Skip to main content
Glama

PerpMetric perpetuals data

Compare one asset across venues

compare_venues
Read-onlyIdempotent

Side-by-side price, funding (normalized to hourly % and APR %), open interest, volume and basis for one asset on Hyperliquid, Aster and Lighter, plus the funding spread between venues. Use for cross-venue funding or basis analysis.

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": "compare_venues"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolYesBase asset, e.g. BTC, ETH, SOL, HYPE.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety and repeatability are covered. The description adds genuinely useful output detail — that funding is normalized to hourly % and APR % so venues are comparable, and that a funding spread is included. It does not state freshness/snapshot timing or how venues with missing markets are handled.

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

Conciseness5/5

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

Two tight sentences with the payload (metrics and venues) front-loaded and the usage cue trailing. No redundant restatement of the title and no filler.

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

Completeness5/5

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

For a single-parameter read tool with no output schema, enumerating the returned fields in the description is exactly the missing piece, and the normalization convention is spelled out. Nothing an agent needs to call it correctly appears to be absent.

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?

There is only one parameter and the schema documents it at 100% coverage, including example base assets, so the description need not do more. The phrase "one asset" mildly reinforces that a single symbol is compared across all venues rather than a list being accepted, but adds little beyond the schema.

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?

Names a specific verb (compare) and resource (one asset across Hyperliquid, Aster and Lighter), then enumerates the exact metrics returned: price, funding normalized to hourly % and APR %, open interest, volume, basis, and the funding spread. This is clearly differentiated from siblings such as find_funding_spreads, which the fixed venue/asset scope implies is a different kind of lookup.

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?

"Use for cross-venue funding or basis analysis" gives explicit when-to-use context, which is more than most read tools offer. It stops short of naming when not to use it or pointing to an alternative (e.g. a market-wide spread scanner), so there is no exclusion guidance.

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