Skip to main content
Glama

DeFi Capital Flow-Price Gap

Freshness, quality gate and proof status (free)

get_status
Read-onlyIdempotent

Free. Today's data day and its age, the quality gate, whether paid tools are open (paid_routes_open), the Bitcoin proof status of today's fingerprint, the token list (token_symbols) and each tier's track-record verdict. Same JSON as GET /v1/status. Informational, not investment advice.

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

B3.4/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 the safety profile is covered. The description adds useful context beyond that: the payload mirrors a known REST endpoint, that paid tool availability is exposed, and a disclaimer that this is informational. It does not say whether the values fluctuate, how often, or what the quality gate verdict actually looks like.

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 cost signal, then a compact field inventory, then the endpoint equivalence and disclaimer. The field list is dense but every clause names a distinct returned datum; the only waste is the boilerplate disclaimer.

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-argument status tool with no output schema, the description carries the return-value burden itself and does so by naming each payload section. Minor gaps remain: no indication of freshness thresholds, what values the quality gate can take, or how the track-record verdict is expressed.

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?

The tool takes zero parameters, so there is no parameter semantics to explain and the baseline of 4 applies. The description does not introduce confusing pseudo-parameters such as paid_routes_open or token_symbols as inputs, they read as returned fields.

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 enumerates the concrete payload of a status endpoint (data day and age, quality gate, paid_routes_open, Bitcoin proof status, token_symbols, per-tier track-record verdict) and anchors it with 'Same JSON as GET /v1/status'. It is clear what the tool returns, but it never contrasts itself with overlapping siblings such as get_proof, get_coverage or get_track_record.

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

Usage Guidelines2/5

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

The only usage signal is the leading 'Free.' and 'Informational, not investment advice.' There is no statement of when to call this versus get_proof or get_track_record, nor any prerequisite such as 'call this first to check freshness before requesting signals'.

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