Skip to main content
Glama

get_realized_gains

The user's realised capital gains using FIFO, in euros, with fees and gas deducted: total, per asset and per year. Not a tax return.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_realized_gains"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearNoCalendar year of the sales (optional; without it everything is returned).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the accounting method (FIFO), currency normalization, cost deductions, and output aggregation levels, plus a scope disclaimer. It omits auth/wallet prerequisites and whether results are computed live or cached.

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 with a compact colon-delimited enumeration of output levels and a short disclaimer. No filler, every clause adds 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?

No output schema or annotations exist, yet the description specifies return contents (total, per asset, per year), currency, and cost method. It could still say more about required wallet connectivity or the time range covered, but it is largely sufficient for a one-optional-param read tool.

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 optional 'year' parameter is fully documented there, including the default-all behavior. The description adds only the notion that results appear 'per year', so the schema does the heavy lifting; baseline 3 applies.

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 specific verb (realised capital gains) and resource, plus method (FIFO), currency (euros) and deductions (fees, gas). The closing 'Not a tax return' distinguishes it from the sibling get_tax_estimate without needing the schema.

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?

'Not a tax return' signals that tax computations belong to get_tax_estimate rather than this tool, and the description implies use for actual realized-gain reporting. It gives clear context but never explicitly names the alternative or states when-not to call it beyond that caveat.

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