Skip to main content
Glama

CryptoPeildatum

Price history on all reference dates

price_history
Read-onlyIdempotent

Every reference-date price (1 January 00:00 Dutch time) of one coin since the first year with data, per platform, with the percentage change versus the previous year on the same platform.

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": "<coin>"
    },
    "name": "price_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
coinYesCoin ticker, name or slug, case-insensitive, e.g. "BTC", "bitcoin", "eth", "ripple".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare this a safe, idempotent, closed-world read, so the description's job is to add domain behavior — and it does: exactly which dates are sampled (1 January 00:00 Dutch time), that results are broken out per platform, that a percentage change versus the previous year on the same platform is attached, and that history starts at the first year with data. Remaining gaps (ordering, absence of data for early years, size of the series) are minor against that annotation coverage.

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?

One densely packed sentence with no filler, front-loaded on the returned resource. The nested parentheticals make it slightly harder to parse on first read, but every clause (reference date definition, per-platform split, year-over-year change, history start) carries information.

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 one well-documented parameter, full annotation coverage, and no output schema, the description succeeds in conveying what the response contains: per-platform prices on fixed annual reference dates plus percentage change. Nothing an agent needs in order to call this correctly is missing.

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 coin parameter already documents accepted forms (ticker, name, slug, case-insensitivity) with examples. The description only adds the constraint that a single coin is queried, which is worth having but does not meaningfully extend the schema.

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 resource (every reference-date price of one coin, per platform, since the first year with data) rather than restating the title. An agent can distinguish it from a single-point price lookup, but it never names the sibling get_reference_price or states the boundary explicitly.

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 only implied by scope: the 'every reference-date price ... since the first year with data' phrasing suggests this is the full-history call, as opposed to a snapshot. There is no explicit when-to-use, when-not-to-use, or named alternative, so the agent must infer the choice from coverage wording.

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