Skip to main content
Glama

DeFi Capital Flow-Price Gap

What is measured today (free)

get_coverage
Read-onlyIdempotent

Free. What is measured today: chains, protocols, tokens and data sets, generated from the data itself. Same JSON as GET /coverage.json.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

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 cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description carries a lighter burden. It adds two useful facts beyond the structured data — that the catalog is generated from the data itself (so it reflects live state rather than a static list) and that the payload is identical to GET /coverage.json, which lets an agent cross-reference known REST semantics. It stops short of any indication of size, shape, or refresh cadence.

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?

Two short sentences, front-loaded with cost ('Free') and then the content enumeration, with the endpoint equivalence last. Minor waste: 'What is measured today' duplicates the title verbatim, and the subject list ('chains, protocols, tokens and data sets') verges on enumerating what the fast-changing response would already show.

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?

This is a simple, zero-parameter read with no nested objects and no output schema, so the description need not document return values. Naming the covered entity types plus pointing at the equivalent REST endpoint gives an agent enough to invoke it confidently and interpret the result.

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 no parameters and the schema is 100% covered, so there is nothing for the description to compensate for. Baseline 4 applies for a zero-argument call.

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 states a specific resource — the catalog of what is measured (chains, protocols, tokens, data sets) — which tells an agent exactly what comes back. It differentiates itself from siblings only via the 'Free' marker, which other free tools (get_free_signal, list_free_days) also carry, so it is clear but not sharply distinct from alternatives.

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?

Usage is only implied: an agent can infer this is a discovery/metadata call for figuring out what data exists, and that it should be called before queries against unlisted entities. There is no explicit when-to-use statement, no mention of when it is unnecessary, and no named alternative.

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