Skip to main content
Glama

The Coin Daily Research

Show funding chart

research_show_funding
Read-onlyIdempotent

Display a focused funding chart widget after evidence from research_read_series is available. Funding history in its supplied units. Positive rates mean longs pay shorts; negative rates reverse that payment. Use only when a visual helps answer the question. Not a data fetch, calculation, navigation hub or replacement for the assistant's interpretation. Reuses captured source numbers and selection; expired evidence requires an explicit new read.

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": {
      "evidence_id": "<evidence_id>"
    },
    "name": "research_show_funding"
  }
}

Input Schema

NameRequiredDescriptionDefault
evidence_idYesExact evidence.id from the matching data tool in this authenticated conversation. The server retrieves original values and selection; do not supply chart numbers.

Output Schema

NameRequiredDescriptionDefault
factsNo
statusYes
messageNo
surfaceYes
evidenceNo
selectionYes
research_urlYes
schema_versionNotcd.mcp-research/v2
retry_after_secondsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, closed-world), yet the description still adds real behavior: it reuses captured source numbers and selection, reports history in the supplied units, and defines the sign convention for funding rates. The staleness rule (expired evidence needs a fresh read) is genuinely useful operational detail beyond the annotations.

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 action and the prerequisite, and the sign-convention sentence earns its place by preventing misreading of returns. Slightly padded by the four-item negation clause ("data fetch, calculation, navigation hub..."), which could be tightened.

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?

With an output schema present, the return values need no explanation, and annotations carry the safety profile. The description still supplies the prerequisite, staleness handling, unit and sign semantics, and the anti-use cases — nothing an agent needs to call this correctly is missing.

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?

Schema coverage is 100% and the evidence_id description already covers the pattern and sourcing, so baseline is 3. The description adds the specific originating tool (research_read_series) and restates that source numbers/selection are reused rather than supplied, which sharpens how to obtain the ID.

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?

States a specific verb and resource ("Display a focused funding chart widget") plus the prerequisite evidence source (research_read_series), and explicitly negates adjacent roles ("Not a data fetch, calculation, navigation hub"). An agent can separate it from research_read_series and the other research_show_* siblings without opening a schema.

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

Usage Guidelines5/5

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

Gives an explicit gate ("Use only when a visual helps answer the question") and an explicit exclusion list ("Not a data fetch, calculation, navigation hub or replacement for the assistant's interpretation"). It also names the required prior step (evidence from research_read_series) and the recovery path when evidence expires ("requires an explicit new read").

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