Skip to main content
Glama

PerpMetric perpetuals data

Data status per venue

get_status
Read-onlyIdempotent

Freshness and coverage of PerpMetric data for each venue. Call this first when timing matters, or when another tool reports 'degraded'/'stale' data. Cheap.

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_status"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is fully covered. The description adds two useful behavioral cues beyond that: a cost signal ("Cheap") and the fact that the tool can surface 'degraded'/'stale' states that other tools may echo. It does not describe the shape of the status payload, which matters since no output schema exists.

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?

Three short sentences, front-loaded with what the tool returns, then the routing rule, then a cost cue. "Cheap." is a fragment but is deliberate and high-value for an agent deciding whether to spend a call.

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?

For a zero-parameter, read-only status tool this covers purpose, timing and cost adequately. The remaining gap is the return shape: with no output schema, the description never says what per-venue fields come back (stale flag, timestamps, coverage percentage), leaving the agent to infer from the words 'degraded'/'stale'.

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?

Zero parameters, so there is no parameter semantics to explain and the baseline of 4 applies. Nothing in the description misleads about inputs.

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 resource pair — freshness and coverage of PerpMetric data — scoped per venue. That is clearly distinguishable from siblings that return market lists, breadth metrics, or venue comparisons; an agent knows this is a health/quality check, not a data pull.

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?

"Call this first when timing matters, or when another tool reports 'degraded'/'stale' data" gives an explicit trigger condition and a reactive trigger tied to other tools' output. It stops short of stating when NOT to call it (e.g. no need on every request), so it is strong but not exhaustive.

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