Skip to main content
Glama

BRAINIAC Crypto Tax Computation

UK share pooling for cryptoassets

crypto-tax_uk-share-pooling
Read-onlyIdempotent

Apply same-day, 30-day and section 104 share-pooling rules to a GBP ledger and return allowable cost, gains, pool balances and AEA. Price $0.05 USDC. POST /api/v1/crypto-tax/uk-share-pooling. 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>",
      "taxYear": "<taxYear>"
    },
    "name": "crypto-tax_uk-share-pooling"
  }
}

Input Schema

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

Output Schema

NameRequiredDescriptionDefault
poolNopool. Object.
netGainNonetGain. Number.
sourcesNosources. Array.
taxYearNotaxYear. String.
warningsNowarnings. Array.
disposalsNodisposals. Array.
limitationsNolimitations. Array.
taxableAfterAeaNotaxableAfterAea. Number.
annualExemptAmountNoannualExemptAmount. Number.

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 declare read-only, idempotent, open-world, and non-destructive behavior. The description adds important paid-endpoint behavior beyond that: USDC pricing, the POST route, and the fact that an unpaid call returns x402 payment terms without running the calculation.

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 concise sentences front-load the calculation, then give price, endpoint, and payment-gate behavior. Each sentence carries operational information and there is no wasted wording.

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?

Given the output schema, annotations, and fully documented input schema, the description covers the task, key returns, endpoint, price, and unpaid-call behavior. It leaves minor gaps such as not expanding 'AEA', but an agent has enough to select and invoke the tool correctly.

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%, with ledger item fields, taxYear, feePolicy, and fiatCurrency documented in the schema. The description adds only the 'GBP ledger' framing and does not provide extra meaning or constraints for individual parameters.

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 uses a specific verb, 'Apply', together with named UK statutory pooling rules (same-day, 30-day, section 104) and a GBP ledger. This is far more specific than a generic tax tool and distinguishes it from jurisdiction-specific siblings such as Australia CGT or Canada ACB.

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 UK and GBP framing implies the appropriate context, but the description does not explicitly say when to use this versus other cost-basis or jurisdiction tools. There are no stated exclusions, prerequisites, or routing guidance to alternatives.

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