Skip to main content
Glama

The Coin Daily Research

Show price chart

research_show_price
Read-onlyIdempotent

Display a focused price chart widget after evidence from research_open_ticker is available. Candlestick history with local 3× replay and A/B selection. Ask the assistant to investigate the selected move. 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_price"
  }
}

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 declare readOnly/idempotent/non-destructive, so the safety profile is covered. The description adds genuinely non-obvious behavior: it reuses captured source numbers and the prior selection rather than re-fetching, and expired evidence forces an explicit new read. It does not explain failure behavior for a malformed or unknown evidence_id, which keeps it below a 5.

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 primary action and precondition, then constraints. Dense but nearly every clause carries information; the 'Not a data fetch, calculation, navigation hub' enumeration is slightly listy and the '3× replay / A/B selection' terms arrive without definition.

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?

Output schema exists, so return shape needn't be described; annotations cover safety. For a single-parameter rendering tool, the description covers prerequisite, lifetime, reuse semantics, and appropriateness criterion — everything an agent needs to decide and invoke correctly.

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 property description already specifies the 64-hex evidence.id format and 'do not supply chart numbers'. The description nonetheless reinforces the semantics — the ID carries the original values and selection, and stale IDs expire — which is meaning the schema alone does not convey.

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 artifact ('Display a focused price chart widget') and immediately scopes it against siblings by declaring it is 'Not a data fetch, calculation, navigation hub' — a direct contrast with research_read_series, research_interpret_range, and the show_* family. It also names the prerequisite tool research_open_ticker, so an agent can place it precisely in a workflow.

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?

Explicit when-to-use ('Use only when a visual helps answer the question'), explicit when-not (not a data fetch, calculation, navigation hub, or replacement for the assistant's interpretation), and a stated precondition (evidence from research_open_ticker must exist). The expired-evidence rule tells the agent what to do when the guard fails.

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