Skip to main content
Glama

get_trades

Transactions recorded by the user (buys, sells and fees), in euros, newest first. Optional filters by asset and year.

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_trades"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearNoCalendar year of the transaction.
assetNoAsset symbol (e.g. BTC).
limitNoMaximum number of transactions to return (default 100).

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

A3.8/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 it does disclose meaningful traits: result ordering (newest first), unit (euros), and the transaction classes included (buys, sells, fees). It does not address authorization requirements, pagination beyond the limit cap, or whether totals/aggregates are returned, leaving some behavioral gaps.

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?

Two sentences, zero filler, with the core identity (what records, what currency, what order) front-loaded before the filtering note. Every clause earns its place.

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?

For a simple, no-auth-annotated read tool with fully documented parameters and no output schema, the description covers what the records are, their unit, and their ordering. A note on default/capped result size or pagination behavior would close the remaining gap given there is no output schema to describe the return shape.

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 each parameter (year, asset, limit) has its own type, bounds, and description, so the schema does the heavy lifting. The description only restates that asset and year are optional filters and ignores the limit parameter entirely, adding no semantics 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 states a specific resource (user's transaction records) with the record types it covers (buys, sells, fees) and the currency, which lets an agent tell it apart from pure analytics tools. It does not explicitly contrast itself with near-siblings like get_realized_gains or get_pnl, which also surface trade-derived data.

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?

"Optional filters by asset and year" implies the usage pattern (retrieve all, optionally narrow), but there is no explicit statement of when to choose this over get_pnl / get_realized_gains / get_tax_estimate, and no preconditions are given. Usage is inferable rather than directed.

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