Skip to main content
Glama

BRAINIAC Crypto Tax Computation

Build IRS Form 8949 rows

crypto-tax_us-form-8949-rows
Read-onlyIdempotent

Produce Form 8949 rows and Schedule D box totals from caller disposals using 2025 short/long-term and 1099-B / 1099-DA box rules. Price $0.04 USDC. POST /api/v1/crypto-tax/us-form-8949-rows. 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": {
      "taxYear": "<taxYear>",
      "disposals": "<disposals>"
    },
    "name": "crypto-tax_us-form-8949-rows"
  }
}

Input Schema

NameRequiredDescriptionDefault
taxYearYestaxYear, integer, from -9007199254740991 to 9007199254740991. Required.
disposalsYesdisposals, array. Required.
roundToDollarsNoroundToDollars, boolean. Required.

Output Schema

NameRequiredDescriptionDefault
rowsNorows. Array.
sourcesNosources. Array.
taxYearNotaxYear. Number.
limitationsNolimitations. Array.
totalsByBoxNototalsByBox. Object.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior5/5

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

Beyond the annotations (readOnly, idempotent, openWorld), the description discloses the $0.04 USDC price, the POST transport, and the crucial failure mode: an unpaid call returns x402 payment terms and does not run. That is exactly the payment/auth behavior an agent needs before committing a call.

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: purpose first, then price and transport, then the unpaid-call caveat. Nothing is redundant and the most decision-relevant constraint 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?

With an output schema present, the description needn't explain return values, and the payment gate is fully covered. It is slightly thin on input expectations such as whether disposals must already be normalized or how missing basis is handled, which matters for a computation 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 coverage is 100% and nested fields carry their own descriptions, so the schema does the heavy lifting. The description adds modest meaning by tying reportedOn/basisReported to 1099-B / 1099-DA box classification and by framing taxYear as the 2025 rule set, but it does not explain roundToDollars or adjustmentCode behavior.

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 opens with a specific verb+resource pair: producing Form 8949 rows and Schedule D box totals from caller-supplied disposals. That names a distinct artifact (IRS Form 8949) relative to the many non-US sibling tools, though it never explicitly contrasts with adjacent tools like cost-basis-lots or specific-id-select that could feed it.

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

Usage Guidelines2/5

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

It signals the applicable regime (2025 short/long-term, 1099-B / 1099-DA box rules) but gives no explicit when-to-use, when-not-to-use, or alternative-selection guidance. An agent must infer that this is the US filing path rather than, say, the Canada ACB or UK pooling sibling.

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