Skip to main content
Glama
Sign In

CryptoPeildatum

by nl.cryptopeildatum
OverviewDiscussionsAdmin

Value holdings on the reference date

value_portfolio
Read-onlyIdempotent

Value in EUR of a list of holdings on 1 January 00:00 Dutch time of the given year, using each holding's platform price. Returns value per line and the total. Lines without a price are marked missing and not counted. Also returns a link to the calculator. Nothing is stored.

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": {
      "holdings": "<holdings>",
      "year": "<year>"
    },
    "name": "value_portfolio"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearYesReference year: prices on 1 January of this year (for the tax return over that year). Available: 2014–2026.
holdingsYesHoldings, one line per coin and platform. The same coin may appear on several platforms.

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 read-only, idempotent, non-destructive, closed-world behavior, so the bar is lower. The description still contributes real behavioral detail beyond them: lines without a price are marked missing and excluded from the total, per-line and total values are returned, a calculator link is included, and nothing is persisted.

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?

Five short sentences, front-loaded with the valuation semantics before the return shape and edge-case handling. The closing 'Nothing is stored' mildly restates readOnlyHint but is brief enough not to be wasteful.

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?

There is no output schema, yet the description fully specifies the return shape: per-line values, a total, missing-price markers excluded from the count, and a calculator link. Combined with the fully documented two-parameter schema and safety annotations, an agent has everything needed to call it correctly.

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%, so both parameters are already documented, including the year range and the platform enum. The description adds modest meaning by stating that each holding is valued 'using each holding's platform price', clarifying why the platform field matters, but it adds no format or constraint detail beyond 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 opens with a precise verb+resource: it values a list of holdings in EUR on a specific reference date using platform prices. That scope is concrete enough to separate it from single-price or price-history siblings, but it never explicitly names or contrasts those alternatives, so it stops short of full sibling differentiation.

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: the schema notes the year is 'for the tax return over that year', and the description implies batch valuation rather than a single quote. There is no explicit when-to-use or when-not-to-use guidance, and no pointer to get_reference_price for individual prices or compare_platforms for platform comparison.

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