Skip to main content
Glama
Sign In

CryptoPeildatum

by nl.cryptopeildatum
OverviewDiscussionsAdmin

Reference-date price

get_reference_price
Read-onlyIdempotent

Price in EUR of one coin on 1 January 00:00 Dutch time (31 December 23:00 UTC) of the given year, per exchange platform. Omit platform to get all platforms. Includes candleTime and kind ("open" of that hour, or "close" of the last earlier hour) and the URL of the coin page.

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>",
      "year": "<year>"
    },
    "name": "get_reference_price"
  }
}

Input Schema

NameRequiredDescriptionDefault
coinYesCoin ticker, name or slug, case-insensitive, e.g. "BTC", "bitcoin", "eth", "ripple".
yearYesReference year: prices on 1 January of this year (for the tax return over that year). Available: 2014–2026.
platformNoExchange platform where the coins were held.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare a safe, idempotent, closed-world read, so the bar is lower, and the description still adds real value: it names the return fields (candleTime, kind, coin page URL) and explains the non-obvious fallback that 'kind' may be the close of the last earlier hour. It does not cover behavior for years/platforms with no data or result ordering.

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?

Dense but front-loaded: the core definition comes first, followed by the platform-omission rule and the return fields. Every clause carries information; no filler, though the single run-on sentence is slightly hard to scan.

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 no output schema, the description carries the burden of explaining return values and does so (candleTime, kind semantics, coin page URL). Combined with 100% schema coverage on the three inputs and read-only annotations, an agent has what it needs to call this correctly.

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

Parameters4/5

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

Schema coverage is 100%, so a 3 is the baseline, but the description goes beyond it by defining the exact reference instant in two timezones and by stating the effect of omitting platform (return all platforms). That optional-parameter behavior is not spelled out in the schema itself.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a precise verb+resource: the EUR price of one coin at a specific reference instant (1 January 00:00 Dutch time) for a given year, optionally per exchange. The single-instant framing distinguishes it from a range-oriented sibling like price_history without needing to name it.

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?

The only routing guidance is parameter-level ('Omit platform to get all platforms'), which tells how to broaden the query but not when to choose this tool over price_history or compare_platforms. Context that it serves tax-return reference pricing lives in the schema's year description, not the tool description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All CryptoPeildatum toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources