Skip to main content
Glama

BRAINIAC Crypto Tax Computation

Detect missing basis problems

crypto-tax_missing-basis-detect
Read-onlyIdempotent

Replay balances to find disposal-without-acquisition, negative balance, unmatched transfer-in and unpriced events before gains are computed. Price $0.03 USDC. POST /api/v1/crypto-tax/missing-basis-detect. 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>"
    },
    "name": "crypto-tax_missing-basis-detect"
  }
}

Input Schema

NameRequiredDescriptionDefault
ledgerYesledger, array. Required.
pricesNoprices, object. Optional.

Output Schema

NameRequiredDescriptionDefault
okNook. Boolean.
issuesNoissues. Array.
sourcesNosources. Array.
limitationsNolimitations. Array.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds behavior the annotations cannot express: a $0.03 USDC price, the POST endpoint, and the fact that an unpaid call returns x402 payment terms and does not execute. That payment-gate disclosure is exactly the kind of context an agent needs before calling.

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, front-loaded with the core action and defect list, followed by cost and transport details. No filler or restatement of the title.

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, return values need no explanation, and the payment/auth behavior is covered. The only minor gap is that it doesn't clarify whether the optional 'prices' map is needed to avoid false 'unpriced' findings, which matters for a nested two-parameter tool.

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% for both parameters, so the schema already documents the ledger item fields and the prices map. The description only indirectly gestures at the optional 'prices' input via 'unpriced events' and adds no format or semantics beyond the schema, so the 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?

The description names a specific verb ('Replay balances') and enumerates the exact defect classes it detects: disposal-without-acquisition, negative balance, unmatched transfer-in, and unpriced events. That enumeration distinguishes it from siblings like transfer-match or cost-basis-lots without needing to name them.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'before gains are computed' gives a clear sequencing context for when to invoke it, which is the key usage decision for a pre-flight validation tool. It stops short of naming an alternative or stating when-not to use it, so it falls short of a 5.

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