Skip to main content
Glama

BRAINIAC Crypto Tax Computation

Normalize exchange CSV to ledger

crypto-tax_exchange-csv-normalize
Read-onlyIdempotent

Convert a caller CSV export into the shared ledger schema using a caller column mapping, or return a mapping template from headers. Price $0.03 USDC. POST /api/v1/crypto-tax/exchange-csv-normalize. 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": {
      "csv": "<csv>"
    },
    "name": "crypto-tax_exchange-csv-normalize"
  }
}

Input Schema

NameRequiredDescriptionDefault
csvYescsv, string, length 0 to 10485760. Required.
walletNowallet, string, length 1 to 128. Required.exchange
mappingNomapping, object. Optional.
fiatCurrencyNofiatCurrency, string, length 3 to 3. Required.USD

Output Schema

NameRequiredDescriptionDefault
ledgerNoledger. Array.
sourcesNosources. Array.
limitationsNolimitations. Array.
fiatCurrencyNofiatCurrency. String.
rejectedRowsNorejectedRows. Array.
mappingTemplateNomappingTemplate. Null.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/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 the safety profile is covered by structured data. The description adds genuinely new behavioral context: the $0.03 USDC price, the POST endpoint, and the crucial detail that an unpaid call returns x402 payment terms instead of running. It says nothing about partial-parse behavior or error handling for malformed rows.

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 operation and the alternate mode, followed by cost, transport, and the payment-failure behavior. No sentence is redundant and nothing repeats the schema or annotations verbatim.

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, so return shapes need not be described, and all four top-level parameters are documented in the schema. Cost, transport, auth-like payment semantics, and mode selection are all covered. The only shortfall is guidance on the nested column-mapping object for a tool with nested inputs, which the description leaves entirely to the schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is 3, and the description earns an extra point by explaining the semantics of the optional mapping parameter: supplying it drives the conversion, omitting it yields a template derived from headers. It does not clarify the nested per-column options (scale, format, values, timezone) or why the required flags inside the nested mapping differ from the top-level required list.

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: convert a caller CSV export into the shared ledger schema, with a second documented mode that returns a mapping template from headers. That is far more concrete than the title alone. It does not name a sibling, but none of the listed crypto-tax analytics tools overlaps with CSV normalization, so the lack of explicit differentiation is a minor gap.

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?

The two operating modes are spelled out: pass a caller column mapping to normalize, or omit it to get a template built from the file's headers. That gives the agent clear conditions for each mode. It stops short of explicit when-not guidance, such as what to do if headers are unrecognized or if the mapping omits a required column.

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