Skip to main content
Glama

Coin

get_coin
Read-only

Free, Standard and Pro: one coin in one call: its quote, rank and window changes, the technicals verdict, the latest stories that mention it and the mean sentiment of those stories over 4 and 24 hours (not the market reading). Use get_technicals or get_candles for more detail.

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": {
      "symbol": "<symbol>"
    },
    "name": "get_coin"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
symbolYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds genuine context beyond that: availability across Free/Standard/Pro tiers and the crucial disclaimer that the sentiment figure is derived from stories rather than the market. It says nothing about failure modes, symbol resolution, or how many stories the limit governs.

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 plan availability and the one-call summary, then the payload list, then the routing hint — a sensible order with no filler. The colon-chained clauses are dense but each carries 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?

With no output schema, the description usefully substitutes by enumerating what comes back, so an agent knows what it will receive. The read-only annotations cover the safety side; the only material omission is the meaning of 'limit', which slightly undercuts an otherwise complete picture.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description carries the burden. It never mentions the 'limit' parameter (default 8, max 20), leaving unclear whether it caps stories or other list items; only 'symbol' is inferable from 'one coin in one call'. With two parameters and no schema docs, this is a real gap.

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?

Concretely enumerates the returned payload — quote, rank, window changes, technicals verdict, latest stories, and mean story sentiment over 4/24 hours — for exactly one coin, which distinguishes it from aggregate siblings. The verb is implicit ('one coin in one call' rather than 'get'), but the resource and scope are unambiguous.

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

Usage Guidelines4/5

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

Explicitly routes detail-seekers to get_technicals or get_candles, and the parenthetical '(not the market reading)' steers agents away from the market-wide sentiment tools. It stops short of saying when this bundle is preferable to the narrower siblings, but the context is clear.

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.