Skip to main content
Glama

Coin prices

get_coin_prices
Read-only

Return the current reference prices of one coin and its bounded observed market price history.

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

Input Schema

NameRequiredDescriptionDefault
periodNoHistory window; current returns no history.90d
coin_idYescoin_id from search_coins.
max_pointsNoUpper bound of history points; a longer series is thinned evenly.

Output Schema

NameRequiredDescriptionDefault
dataYes
as_ofYes
warningsYes
request_idYes
schema_versionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds real value with the distinction between "reference prices" and "observed market price history" and the note that the history is bounded, but it says nothing about freshness, throttling, or what happens for coins with sparse history.

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?

A single front-loaded sentence with no filler; the core resource and scope appear immediately. It is dense but every clause carries information, with only slight redundancy between the verb and the title.

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?

With full schema descriptions, an output schema, and complete annotations, the definition only needs to state the resource and scope accurately, which it does. Nothing essential to correct invocation is missing given how much the structured fields already provide.

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%, including descriptions and an enum for period, so the schema carries the parameter documentation burden. The description only corroborates this by signaling a single coin (coin_id) and a bounded history (max_points), adding little beyond the structured fields; 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 names a specific verb ("Return") and precise resources ("current reference prices", "bounded observed market price history") scoped to "one coin", which separates it from siblings like get_coin_details or get_related_coins. It stops short of naming an explicit alternative, but the resource-level distinction is clear.

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 when-to-use guidance: nothing says whether to prefer this over get_coin_details, or when the history window is worth requesting. At best the split between "current" reference prices and history implies the tool handles both a snapshot and a series use case, but the agent must infer that.

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