# pair_briefing

Everything the radar knows about one perpetual pair in a single answer: funding rate and receiving side, time to next settlement, mark price, 24h volume, open interest with deviation from the 7-day norm, orderbook walls with break-through history, how the price usually moves around settlement, and the same coin on other exchanges. Accepts an exact symbol (BTCUSDT) or just the coin (BTC).

Agent View of the PolicyLayer registry record for `pair_briefing`. HTML page: https://policylayer.com/tools/com-funding-radar-radar/pair-briefing

## Facts

- Tool: `pair_briefing`
- Server: Radar (`https://funding-radar.com/mcp`) — https://policylayer.com/tools/com-funding-radar-radar.md
- Homepage: https://github.com/https://funding-radar.com/mcp
- Risk category: Read (Low risk)
- Registry record: grade C, identity unverified
- Server auth posture: open
- Server rate-limited: no
- Parameters: 3 (2 required)
- Recommended policy verdict: Allowed

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `lang` | string | no | Language of the summary and links: 'en' (default) or 'ru' |
| `symbol` | string | yes | Native pair symbol (BTCUSDT, BTC-USDT-SWAP) or base coin (BTC) |
| `exchange` | string | yes | Exchange id |

Parameters from the server's own tool schema.

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "pair_briefing",
    "arguments": {
      "symbol": "<symbol>",
      "exchange": "<exchange>"
    }
  }
}
```

## Why pair_briefing is rated Low

Even though pair_briefing only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

## Use case

AI agents call pair_briefing to retrieve information from Radar without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Radar:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "pair_briefing": {}
  }
}
```

## Other tools on Radar (5)

- `funding_events` — Read — https://policylayer.com/tools/com-funding-radar-radar/funding-events.md
- `funding_history` — Read — https://policylayer.com/tools/com-funding-radar-radar/funding-history.md
- `radar_about` — Read — https://policylayer.com/tools/com-funding-radar-radar/radar-about.md
- `settlement_calendar` — Read — https://policylayer.com/tools/com-funding-radar-radar/settlement-calendar.md
- `spread_pairs` — Read — https://policylayer.com/tools/com-funding-radar-radar/spread-pairs.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=com-funding-radar-radar · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/com-funding-radar-radar