Skip to main content
Glama

The Coin Daily Research

Show video timeline

research_show_videos
Read-onlyIdempotent

Display a focused video timeline widget after evidence from research_ticker_videos is available. Ticker-matched published chapters with exact watch links and dates. 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_videos"
  }
}

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, closed-world, and the description adds real context beyond them: it reuses captured source numbers/selection and that expired evidence requires an explicit new read. It does not contradict annotations. Slightly dense negations rather than describing the rendered output, but the added state/lifetime semantics are valuable.

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-loads purpose and precondition before the restrictions, and every sentence carries routing or lifetime information. The stacked negations ("not a data fetch, calculation, navigation hub...") are informative but slightly heavier than needed.

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 values needn't be explained; the single parameter is fully documented in schema and reinforced in prose. For a read-only display widget, the description covers precondition, purpose, exclusions, and evidence lifetime — nothing an agent needs to call it 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 one required evidence_id with a hex pattern, so baseline is 3. The description adds meaning beyond the schema: the id must reference evidence from this conversation, values/selection are re-read server-side, and evidence can expire requiring a new read.

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 ("Display") and resource ("focused video timeline widget") and explicitly frames it as a presentation layer distinct from research_ticker_videos (data fetch) and from navigation/calculation tools. An agent can tell exactly what this produces versus its siblings.

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 a precondition ("after evidence from research_ticker_videos is available"), a positive condition ("Use only when a visual helps answer the question"), explicit exclusions ("Not a data fetch, calculation, navigation hub or replacement for interpretation"), and the expired-evidence rule requiring a fresh 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