Skip to main content
Glama

PerpMetric perpetuals data

Market breadth and regime

get_breadth
Read-onlyIdempotent

Participation across the whole venue: share of markets up/down, positioning and regime context. Use to judge whether a move is broad or idiosyncratic.

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": {
      "venue": "<venue>"
    },
    "name": "get_breadth"
  }
}

Input Schema

NameRequiredDescriptionDefault
venueYesExchange. hyperliquid = Hyperliquid (Core + HIP-3), aster = Aster, lighter = Lighter.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world, so the safety profile is covered. The description adds real value by enumerating the content of the payload (up/down share, positioning, regime), but it says nothing about whether breadth is a point-in-time snapshot or over a window, and no freshness or rate-limit context.

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 short sentences, zero filler, with the scope stated first and the decision use case second. Every clause carries information.

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 does list the three return components an agent can expect, which is the main burden here. The remaining gap is temporal semantics — breadth over what period or as of when — which an agent would need to interpret the numbers correctly.

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 a single required parameter with 100% schema description coverage and an enumerated value set fully documented in the schema. The description only echoes the concept of 'venue' without adding meaning such as what a venue scope excludes, so the schema carries the load and the baseline of 3 applies.

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 specific resource and scope: 'participation across the whole venue' with 'share of markets up/down, positioning and regime context', which is clearly an aggregate breadth read rather than a per-market lookup. That distinguishes it from siblings like get_markets or explain_market, though it never names an alternative explicitly.

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?

It gives one concrete decision context: 'use to judge whether a move is broad or idiosyncratic'. That is implied usage rather than explicit when/when-not guidance, and it does not say when to prefer explain_market, compare_venues, or get_status instead.

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