Skip to main content
Glama

PerpMetric perpetuals data

Explain one market

explain_market
Read-onlyIdempotent

One-call briefing for an asset: price, 1h/24h change, funding, open interest and basis on every venue, the funding spread, a plain reading of price vs open interest, and (with a key) the market's active unusual-activity signals plus what historically followed similar signals. Start here for 'what is going on with X?'.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "symbol": "<symbol>"
    },
    "name": "explain_market"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolYesBase asset, e.g. BTC, ETH, HYPE, or a HIP-3 id like xyz:TSLA.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive, closed-world behavior, so the description doesn't need to repeat that. It adds genuinely useful context beyond them: the response aggregates across every venue, and the unusual-activity signal section requires an API key ('with a key'), which is an auth prerequisite an agent must know before relying on the output. No mention of rate limits or latency.

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

Conciseness4/5

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

Front-loaded with the core promise ('One-call briefing for an asset'), then a dense enumeration of contents, then a short usage pointer. The enumeration is long but each item is a distinct returned data category, so little is wasted; the run-on structure is the main weakness.

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 one fully described parameter, a rich set of annotations, and no output schema, the description covers what an agent needs: scope, contents, auth caveat, and entry-point role. It stops short of describing any depth or pagination limits on the historical 'what followed' comparison, which is the one remaining ambiguity.

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

Parameters3/5

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

Schema coverage is 100% and the schema description already explains the single symbol parameter including HIP-3 ids. The description adds only the implicit point that the symbol scopes every venue in the aggregate; it adds no syntax or format detail beyond the schema, so baseline 3 applies.

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

Purpose5/5

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

States a specific verb+resource ('one-call briefing for an asset') and then enumerates the exact contents: price, 1h/24h change, funding, open interest, basis across venues, funding spread, price-vs-OI reading, and unusual-activity signals. The multi-venue scope distinguishes it from single-metric siblings like find_funding_spreads or compare_venues without needing their schemas.

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

Usage Guidelines4/5

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

Gives a clear entry-point rule: 'Start here for what is going on with X?'. It implies this is the default first call before drilling into narrower tools, but it does not explicitly name an alternative or state when not to use it (e.g. multiple assets at once).

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