Skip to main content
Glama

The Coin Daily Research

Show market shortlist

research_show_markets
Read-onlyIdempotent

Display a focused market shortlist widget after evidence from research_markets is available. Ranked assets and their current reported prices; Signal Book rank measures analytical attention, not expected returns. 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_markets"
  }
}

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

A3.8/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely new behavior: it reuses captured source numbers and selection, and expired evidence requires an explicit new read, which tells the agent about failure/reuse semantics not present in the structured fields.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core purpose is front-loaded and the prerequisite framing is efficient, but the four-item negative list ("not a data fetch, calculation, navigation hub or replacement for the assistant's interpretation") is a laundry list that could be compressed. For a single-parameter display widget the description is somewhat long-winded.

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?

An output schema exists, so return values need no explanation, and the description covers the prerequisite evidence read, the reuse/expiry behavior, and the interpretation caveat about Signal Book rank. The main residual gap is error behavior for an invalid or mismatched evidence_id.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the single evidence_id parameter already documents the exact-id requirement, the 64-hex pattern, and the instruction not to supply chart numbers. The description's note about reusing captured values largely restates the schema, so baseline 3 applies.

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 verb and resource ("Display a focused market shortlist widget") and adds what the widget contains (ranked assets with current reported prices). It distinguishes itself from the data-fetch sibling research_markets, but does not differentiate itself from other show_* siblings such as research_show_price or research_show_positioning.

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

Usage Guidelines4/5

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

It gives a clear usage condition ("Use only when a visual helps answer the question") and explicit exclusions ("Not a data fetch, calculation, navigation hub or replacement for the assistant's interpretation"), plus the prerequisite that evidence from research_markets must exist. It stops short of naming which sibling to call instead when a visual is not warranted.

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