Skip to main content
Glama

Compare coins

compare_coins
Read-only

Compare two to four identified coins by the same facts and the same price basis.

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_ids": "<coin_ids>"
    },
    "name": "compare_coins"
  }
}

Input Schema

NameRequiredDescriptionDefault
coin_idsYesTwo to four different coin_id values 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 cover the safety profile (readOnly, non-destructive, closed world), so the description's added contribution is the normalization guarantee: all coins are compared on the same facts and the same price basis. That is meaningful behavioral context an agent could not infer from the annotations or schema, though nothing is said about limits on how many comparisons can be requested or how results are ordered.

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 front-loaded sentence that states the operation and its constraints with no filler. Every clause earns its place, and the cardinality limit appears before the softer comparison-basis detail.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter read-only tool with full schema coverage, a complete output schema, and clear annotations, the description covers the essentials. It is thin on routing guidance, however, leaving the agent to guess whether a comparison is worth one call versus several get_coin_details calls.

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% and the single parameter is documented in the schema itself, including the 'different coin_id values from search_coins' provenance. The description restates the two-to-four cardinality but adds no new semantics such as ordering behavior or what happens with duplicate IDs.

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 definition names a specific verb (compare) and resource (two to four coins) and even states the comparison dimensions ('same facts and the same price basis'). It is clear what the tool does, though it never explicitly distinguishes itself from looking up each coin individually via get_coin_details or get_coin_prices.

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?

'Identified coins' and the two-to-four bound imply the precondition that coin IDs must already be known (the schema points at search_coins), but there is no explicit when-to-use versus when-not, and no named alternative for one-coin lookups or multi-coin price browsing.

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