Skip to main content
Glama

BRAINIAC Crypto Tax Computation

Apply specific-identification lot selections

crypto-tax_specific-id-select
Read-onlyIdempotent

Apply caller-chosen lot identifications to disposals, validate timing and quantities, and return matched basis or structured selection errors. Price $0.05 USDC. POST /api/v1/crypto-tax/specific-id-select. 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>",
      "selections": "<selections>"
    },
    "name": "crypto-tax_specific-id-select"
  }
}

Input Schema

NameRequiredDescriptionDefault
ledgerYesledger, array. Required.
feePolicyNofeePolicy, string, one of add_to_basis_and_deduct_from_proceeds, ignore. Required.add_to_basis_and_deduct_from_proceeds
selectionsYesselections, array. Required.
fiatCurrencyNofiatCurrency, string, length 3 to 3. Required.USD

Output Schema

NameRequiredDescriptionDefault
errorsNoerrors. Array.
sourcesNosources. Array.
openLotsNoopenLots. Array.
warningsNowarnings. Array.
disposalsNodisposals. Array.
limitationsNolimitations. Array.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent and non-destructive, so the safety profile is covered. The description adds real context beyond that: a $0.05 USDC price, the POST endpoint, and the x402 behavior that an unpaid call returns payment terms and does not execute. Validation of timing and quantities and the 'structured selection errors' outcome are also disclosed. It does not say how errors are shaped or whether partial failure aborts the whole request, which keeps it at 4.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The opening sentence front-loads the action, the outcome and the error mode; pricing, endpoint and payment gating follow in short declarative sentences. No filler or repetition. Slightly dense in the first clause, but every sentence carries new 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?

With an output schema present, the description needn't enumerate return fields, and noting 'matched basis or structured selection errors' is sufficient signposting. Payment gating, idempotency and validation scope cover the operationally important gaps. What remains unstated — jurisdictional applicability of specific-ID and how partial selection errors are reported — is a modest omission rather than a blocker.

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 four parameters (ledger, selections, feePolicy, fiatCurrency) are already documented structurally. The description adds only oblique hints — 'timing and quantities' gesture at ts and qty validation, and 'matched basis' relates to fiatValue — but does not clarify the feePolicy enum trade-off or how disposalId/lotId are expected to correspond. Baseline 3 is appropriate.

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 verb and resource: applying caller-chosen lot identifications to disposals, plus validation of timing and quantities. That is clearly distinguishable from sibling computations like cost-basis-lots or transfer-match, which do the matching for the caller. It stops short of explicitly naming a sibling it is not, so it lands at 4 rather than 5.

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?

The phrase 'caller-chosen lot identifications' implies this tool is used when the user has already decided which lots to pair with which disposals, but it never states that or contrasts with a default/FIFO tool. There is no explicit when-not guidance, no prerequisite note about the ledger needing prior classification. Usage is implied 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