Skip to main content
Glama

BRAINIAC Crypto Tax Computation

Canadian adjusted cost base

crypto-tax_canada-acb
Read-onlyIdempotent

Compute Canadian ACB and capital gains with superficial-loss detection for identical properties on a CAD ledger. Price $0.04 USDC. POST /api/v1/crypto-tax/canada-acb. 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_canada-acb"
  }
}

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
treatmentNotreatment, string. Required.capital
fiatCurrencyNofiatCurrency, string, length 3 to 3. Required.CAD

Output Schema

NameRequiredDescriptionDefault
acbNoacb. Object.
sourcesNosources. Array.
warningsNowarnings. Array.
disposalsNodisposals. Array.
treatmentNotreatment. String.
limitationsNolimitations. Array.

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 cover the safety profile (readOnlyHint=true, idempotentHint=true, destructiveHint=false), and the description adds genuinely new operational context: a $0.04 USDC price, the POST endpoint, and that an unpaid call returns x402 payment terms without executing. It does not disclose computation-level behavior such as rounding, unit assumptions for fiatValue, or determinism, which keeps it just below the top mark.

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?

Four short sentences, front-loaded with the purpose before cost, endpoint, and payment semantics. The price and payment-failure behavior are stated in the fewest words possible; nothing is padding.

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 values need not be described, and the critical non-obvious behavior (paid invocation, x402 flow) is fully covered. What remains thin is domain configuration detail — how feePolicy and treatment affect the result — 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.

Parameters3/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. The description reinforces the CAD currency assumption ('CAD ledger') but adds no meaning for feePolicy, treatment, fiatValue units, or the ledger row types that materially change the ACB math.

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 ('Compute Canadian ACB and capital gains') plus the distinguishing domain detail ('superficial-loss detection for identical properties'), which cleanly separates it from the jurisdiction-specific and lot-selection siblings (australia-cgt-discount, uk-share-pooling, specific-id-select). An agent can recognize this as the Canadian ACB calculator without opening the schema.

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 jurisdictional scope ('Canadian', 'CAD ledger') implies when this tool applies rather than stating it, and there is no explicit when-not or named alternative (e.g. vs crypto-tax_cost-basis-lots or crypto-tax_us-form-8949-rows). The payment/call-flow guidance is clear, but selection guidance is left to inference.

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