Skip to main content
Glama

BRAINIAC Crypto Tax Computation

Match disposals to acquisition lots

crypto-tax_cost-basis-lots
Read-onlyIdempotent

Match disposals to acquisition lots by FIFO, LIFO, HIFO or average cost and compute gains from a caller-supplied ledger and fiat values. No market prices are fetched. Price $0.05 USDC. POST /api/v1/crypto-tax/cost-basis-lots. 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": {
      "fiatCurrency": "<fiatCurrency>",
      "method": "<method>",
      "ledger": "<ledger>"
    },
    "name": "crypto-tax_cost-basis-lots"
  }
}

Input Schema

NameRequiredDescriptionDefault
ledgerYesledger, array. Required.
methodYesmethod, string, one of FIFO, LIFO, HIFO, AVERAGE. Required.
feePolicyNofeePolicy, string, one of add_to_basis_and_deduct_from_proceeds, ignore. Required.add_to_basis_and_deduct_from_proceeds
fiatCurrencyYesfiatCurrency, string, length 3 to 3. Required.

Output Schema

NameRequiredDescriptionDefault
methodNomethod. String.
sourcesNosources. Array.
openLotsNoopenLots. Array.
warningsNowarnings. Array.
disposalsNodisposals. Array.
limitationsNolimitations. Array.
fiatCurrencyNofiatCurrency. String.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so safety is covered. The description adds genuinely non-obvious behavior beyond them: it is a paid POST endpoint at $0.05 USDC, and an unpaid call returns x402 payment terms without running — a failure mode an agent must anticipate. It stops short of rate limits or response shape, though the output schema covers returns.

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, zero padding: capability and method first, then the critical input constraint ('no market prices fetched'), then payment and endpoint details. Nothing is buried or repeated.

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?

With rich annotations and an output schema present, the definition covers what the agent must know: inputs are caller-supplied, methods are enumerated, the call is paid and gated. A note on feePolicy's effect on basis and on how transfer/trade ledger rows are treated would close the remaining gap.

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 the enum values and ledger item fields are already documented inline. The description restates the method choices but adds nothing about feePolicy semantics or how ledger entry types (transfer_in, trade, fee) affect matching — 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 and resource ('Match disposals to acquisition lots') plus the exact methods (FIFO, LIFO, HIFO, average cost) and the output ('compute gains'). That vocabulary cleanly separates it from siblings such as crypto-tax_specific-id-select (specific-lot identification) and crypto-tax_canada-acb (pooled ACB).

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?

Implies usage through 'from a caller-supplied ledger and fiat values. No market prices are fetched', which tells the agent it must supply priced data and that this is not a market-data lookup. It never names a sibling or states when NOT to use this tool, e.g. versus specific-ID selection or jurisdiction-specific pooling tools, so routing must be inferred.

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