Skip to main content
Glama

The Coin Daily Research

Show group comparison

research_show_cohorts
Read-onlyIdempotent

Display a focused group comparison widget after evidence from research_prepare_cohorts / research_compare_cohorts is available. One pinned comparison: performance, benchmark-relative performance, member contributions, relationships or qualified correlation. A ready preparation is a valid source too; preserve named groups and selection. 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_cohorts"
  }
}

Input Schema

NameRequiredDescriptionDefault
viewNoThe specific analytical chart answering the user's question; not always price performance.performance
x_metricNoFor relationships, an exact returned metric ID for the horizontal axis; otherwise omit.
y_metricNoFor relationships, an exact returned metric ID for the vertical axis; otherwise omit.
evidence_idYesExact evidence.id from the requested pinned cohort comparison.

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.3/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), so the bar is lower; the description nonetheless adds real behavior: one pinned comparison at a time, reuse of captured source numbers and selection, and that expired evidence forces a fresh read. It does not state what happens to a previously pinned comparison when re-invoked, which keeps it at 4.

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 its precondition, then the scoping and exclusion rules. A few clauses are dense, stacked negatives ("not a data fetch, calculation, navigation hub or replacement..."), but each sentence carries a distinct constraint rather than padding.

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?

With an output schema present, return values need no explanation, and the description covers the critical preconditions, expiry behavior, and non-purposes for a 4-param widget tool. The only thin spot is behavior on repeat invocation with a different view for the same 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 description coverage is 100%, so the enum values and x_metric/y_metric semantics are already documented in the schema; the description's view enumeration largely restates the enum. The one added nuance is that groups and selection are preserved from the source rather than re-specified, which is worth noting but doesn't exceed the baseline by much.

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+resource ("Display a focused group comparison widget") and immediately scopes it to a single pinned comparison with enumerated views. Explicitly separates itself from data-fetch/calculation/navigation siblings, so an agent can distinguish it from research_compare_cohorts or research_read_evidence 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 both sides of the decision: preconditions (evidence from research_prepare_cohorts / research_compare_cohorts, or a ready preparation), an affirmative test ("Use only when a visual helps answer the question"), and explicit exclusions (not a data fetch, calculation, navigation hub, or replacement for interpretation). The expiry rule ("expired evidence requires an explicit new read") names the fallback action.

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