Skip to main content
Glama

Related coins

get_related_coins
Read-only

Find a few coins related to one coin (same series, otherwise same year) and say how they are related.

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": {
      "coin_id": "<coin_id>"
    },
    "name": "get_related_coins"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoHow many related coins to return.
coin_idYescoin_id from search_coins.

Output Schema

NameRequiredDescriptionDefault
dataYes
as_ofYes
warningsYes
request_idYes
schema_versionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, destructiveHint=false, openWorldHint=false), so the description's contribution is the matching algorithm itself — same series with a same-year fallback — plus the fact that the result explains the relationship. That is genuine behavioral disclosure not present in the annotations or schema. The word 'otherwise' is ambiguous (fallback when series is absent, or when series yields too few results), which keeps it from 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.

Conciseness5/5

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

A single sentence with zero filler: the action and resource come first, the matching rule follows, and the output note closes it. Nothing could be removed without losing information.

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?

For a simple read-only lookup with a full output schema and complete annotations, the description supplies what structured fields cannot: the relationship criteria. The only real gap is behavior when no related coin exists, which the description never addresses.

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 schema already documents both coin_id (sourced from search_coins) and limit (1-6). The description adds only the loose phrase 'a few coins', which does not clarify the limit semantics or what happens at the maximum of 6. Baseline 3 is appropriate when the schema carries the parameter burden.

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 gives a specific verb ('Find') and resource ('coins related to one coin') and states the matching criteria (same series, otherwise same year), which is concrete enough to separate it from search_coins and compare_coins. It stops short of naming any sibling as an alternative, so an agent must infer the boundary itself.

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

Usage Guidelines2/5

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

There is no explicit statement of when to use this tool versus compare_coins (also multi-coin) or search_coins (also discovery). The parenthetical explains the matching heuristic, which is selection logic internal to the tool, not guidance about when an agent should call it. Usage is only faintly implied by the word 'related'.

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