Skip to main content
Glama

Coin details

get_coin_details
Read-only

Retrieve the facts, photos and description of one identified coin. fact_status says per field whether it is official (NBU), set by an editor, unconfirmed, disputed or unknown.

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_coin_details"
  }
}

Input Schema

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

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds genuinely non-structured context: that the response includes per-field provenance semantics (official NBU, editor-set, unconfirmed, disputed, unknown), which the agent would not know how to interpret otherwise.

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?

Two sentences, front-loaded with the core action and payload, with the fact_status clarification placed second. No filler; the fact_status clause is dense but warranted.

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 structure need not be spelled out, and the description instead covers the one interpretive signal (fact_status) that matters. With annotations covering safety profile and a fully documented single parameter, the definition is nearly complete.

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 coin_id parameter is fully documented, including its source (search_coins). The description adds only the notion of a single 'identified' coin, not any format, range, or validity detail beyond the schema — baseline 3.

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?

States a specific verb (retrieve) and resource scope (facts, photos, description of one identified coin), which implicitly separates it from siblings like get_coin_links and get_coin_prices that return other slices of the same entity. It stops short of naming any sibling explicitly, so differentiation relies on the agent comparing content scopes.

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

Usage Guidelines3/5

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

Usage is implied: 'one identified coin' signals a lookup keyed by a known coin_id, and the schema notes coin_id comes from search_coins. There is no explicit when-to-use or when-not-to-use statement, and no mention of the alternatives for prices, links, or related coins.

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