Skip to main content
Glama

BRAINIAC Crypto Tax Computation

Value staking and income events

crypto-tax_income-events-value
Read-onlyIdempotent

Value staking, mining, airdrop and interest receipts in fiat using caller-supplied prices within a max lag window. Price $0.03 USDC. POST /api/v1/crypto-tax/income-events-value. An unpaid call returns the x402 payment terms and does not run.

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": {
      "events": "<events>",
      "prices": "<prices>",
      "maxPriceLagHours": "<maxPriceLagHours>",
      "fiatCurrency": "<fiatCurrency>"
    },
    "name": "crypto-tax_income-events-value"
  }
}

Input Schema

NameRequiredDescriptionDefault
eventsYesevents, array. Required.
pricesYesprices, array. Required.
fiatCurrencyYesfiatCurrency, string, length 3 to 3. Required.
maxPriceLagHoursYesmaxPriceLagHours, number, from any to 8760. Required.

Output Schema

NameRequiredDescriptionDefault
eventsNoevents. Array.
sourcesNosources. Array.
limitationsNolimitations. Array.
fiatCurrencyNofiatCurrency. String.
totalsByKindNototalsByKind. Object.
missingPricesNomissingPrices. Array.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, and non-destructive traits, yet the description still adds real context beyond them: the $0.03 USDC price, the POST endpoint, and crucially the x402 payment-gate behavior where an unpaid call returns terms and does not run. It stops short of stating error behavior for prices that fall outside the max lag window.

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?

Three short sentences: purpose first, then cost, then endpoint, then failure mode. No filler, and the most decision-relevant facts (what it does and what it costs) are front-loaded.

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?

An output schema exists, so return-value description is correctly omitted, and the pricing/payment behavior is disclosed. For a tool with a nested array-of-objects input, the description could say more about matching events to prices, but it is adequate to call the tool 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 description coverage is 100%, so the baseline would be 3, but the description adds relational meaning the schema does not: prices are caller-supplied and are constrained by the max lag window, which explains the interaction between the 'prices' and 'maxPriceLagHours' parameters. It adds no detail on the 'kind' enum values or the expected price units.

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?

States a specific verb ('Value') and a well-scoped resource (staking, mining, airdrop and interest receipts) with the output unit (fiat) and the input method (caller-supplied prices). It is clearly distinct from basis-lot, transfer-match, or CGT-discount siblings, though it does not explicitly name an alternative.

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 implied rather than stated: an agent can infer this is the tool for pricing income-type receipts, and the payment note signals when the call will not execute. There is no explicit 'use this instead of X when Y' routing guidance and no stated prerequisites about which assets/currencies are supported.

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