Skip to main content
Glama

BRAINIAC Crypto Tax Computation

Unrealised holdings snapshot

crypto-tax_unrealized-snapshot
Read-onlyIdempotent

Replay a ledger to a date with a cost-basis method and report holdings, basis, unrealised gain, dust and unpriced assets at caller prices. Price $0.04 USDC. POST /api/v1/crypto-tax/unrealized-snapshot. 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": {
      "ledger": "<ledger>",
      "asOf": "<asOf>",
      "prices": "<prices>"
    },
    "name": "crypto-tax_unrealized-snapshot"
  }
}

Input Schema

NameRequiredDescriptionDefault
asOfYests, string, date-time. Required.
ledgerYesledger, array. Required.
methodNomethod, string, one of FIFO, LIFO, HIFO, AVERAGE. Required.FIFO
pricesYesprices, object. Required.
feePolicyNofeePolicy, string, one of add_to_basis_and_deduct_from_proceeds, ignore. Required.add_to_basis_and_deduct_from_proceeds
fiatCurrencyNofiatCurrency, string, length 3 to 3. Required.USD
dustThresholdFiatNodustThresholdFiat, integer, from 0 to 9007199254740991. Required.

Output Schema

NameRequiredDescriptionDefault
asOfNoasOf. String.
dustNodust. Array.
methodNomethod. String.
sourcesNosources. Array.
holdingsNoholdings. Array.
openLotsNoopenLots. Array.
unpricedNounpriced. Array.
limitationsNolimitations. Array.

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 readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint. The description adds genuinely new behavioral context: the $0.04 USDC price, the POST path, and the fact that an unpaid call returns x402 payment terms without executing — a non-obvious gate an agent must plan for. It stops short of explaining edge behavior such as how unpriced assets are reported or what happens if prices are missing for a held asset.

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 tight sentences: what it does first, then cost, then endpoint, then the payment-failure caveat. Every sentence carries information an agent needs, and the key operation is 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 and parameter documentation is complete, so the description need not explain return values, and it covers the unusual payment gate well. What it omits is a precondition that matters for correctness — that the ledger must contain the full history from inception for cost-basis replay to be valid — which is a notable gap for a 7-parameter tool with a nested transaction array.

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%, so every parameter including the nested ledger fields is already documented, and the baseline is 3. The phrase 'at caller prices' and the mention of dust give mild semantic framing for the prices map and dustThresholdFiat, but the description does not clarify whether price integers are minor units or whole currency units, which is the one ambiguity the schema leaves open.

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 gives a precise verb chain (replay a ledger to a date with a cost-basis method) plus the exact outputs (holdings, basis, unrealised gain, dust, unpriced assets), which is far more specific than the title. It does not explicitly distinguish itself from siblings such as crypto-tax_cost-basis-lots or crypto-tax_specific-id-select, so the agent must infer the difference from the word 'snapshot'.

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 by the output list — this is the tool for a point-in-time unrealised position — but there is no explicit when-to-use versus the sibling lot-level or jurisdiction-specific tools. The only explicit routing guidance is about payment (an unpaid call returns x402 terms and does not run), not about choosing this tool over another.

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