Skip to main content
Glama

Get sector or mandate radar

get_sector_radar
Read-onlyIdempotent

Shareable radar for a standing mandate or a symbol list (api:read). Pass mandate_id to read YOUR saved Gambit (its name, monitor interval, and symbol whitelist) or preset=ai_memory_compute (or a comma-separated symbols list such as xyz:SKHX,xyz:SKHY,MU) for the memory, optical, and AI-compute watch. Returns live 24/7 quote and perp metrics (mark, index, basis_bps, funding_rate, change_24h_pct, volume_24h), cross-DEX and sibling spreads (xyz:SNDK vs io:SNDK, xyz:SKHX vs xyz:SKHY), your open Gambits on those symbols, and compute prices. Without signed Ornn rights (the usual case): gpu_hours from Gambit's stored GPU-hour composite (USD per GPU-hour per GPU family, with 7-day change) and token_prices from OpenRouter token-price medians. With signed Ornn rights configured, GPU prices come from Ornn's OCPI and token_prices is null; without them token_index.otpi is null and compute_reference.otpi says rights_required (Tesseract clearing is omitted unless TESSERACT_REFERENCE_FEED_ENABLED is on). A dex-prefixed symbol is that dex's market only: one with no open market comes back available=false with an unavailable_reason and null figures, and a pair with such a leg has available=false and null spreads. This read does not trade.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_sector_radar"
  }
}

Input Schema

NameRequiredDescriptionDefault
presetNoai_memory_compute when symbols and mandate_id are omitted
symbolsNocomma-separated symbols, e.g. xyz:SNDK,io:SNDK
mandate_idNostanding mandate id; reads YOUR radar

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already establish a safe, idempotent read, and the description still adds substantial behavior: which data source feeds gpu_hours and token_prices depending on signed Ornn rights, that token_index.otpi becomes null without rights, that Tesseract clearing is conditional on a feature flag, and that dex-prefixed symbols with no open market return available=false with an unavailable_reason. It closes with 'This read does not trade,' reinforcing the read-only profile. This is exactly the kind of context annotations cannot convey.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Everything is packed into a single dense paragraph with nested parentheticals, so the key mode-selection instruction competes with edge-case detail about OCPI/otpi nulls and a feature-flag note. The information is mostly load-bearing given there is no output schema, but it is not front-loaded or segmented, which slows scanning.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description carries the return-value burden and does so: field names, spread pairs, degraded/rights-gated states, and unavailable handling are all covered for a three-parameter read tool. Gaps are minor, such as what 'shareable' implies and error behavior for an invalid mandate_id.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning: mandate_id reads your own saved Gambit with its name, monitor interval, and symbol whitelist; preset=ai_memory_compute scopes to the memory/optical/AI-compute watch; and dex-prefixed symbols are constrained to that dex's market with defined unavailable behavior. Only the exact format of a pair comparison is left to the schema example.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a concrete resource ('radar') and its two input modes — a standing mandate ('read YOUR saved Gambit') or a symbol list/preset — and enumerates what comes back (quote and perp metrics, spreads, open Gambits, compute prices). An agent can tell what it produces without opening the schema. It never names a sibling tool it is distinct from, so differentiation from tools like get_live_snapshot or get_gambit rests on inference.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Mode selection is spelled out well: mandate_id reads your saved Gambit, preset=ai_memory_compute or a symbols list gives the market watch. However, there is no when-not-to-use guidance and no alternative tool is named for overlapping needs such as raw quotes or single-symbol data, so usage is implied rather than directed.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources