Skip to main content
Glama

BRAINIAC Crypto Tax Computation

German §23 holding-period screen

crypto-tax_germany-holding-period
Read-onlyIdempotent

Classify crypto private sales under §23 EStG with FIFO (or caller method), one-year holding and the €1,000 Freigrenze. Price $0.04 USDC. POST /api/v1/crypto-tax/germany-holding-period. 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>",
      "calendarYear": "<calendarYear>"
    },
    "name": "crypto-tax_germany-holding-period"
  }
}

Input Schema

NameRequiredDescriptionDefault
ledgerYesledger, array. Required.
methodNomethod, string, one of FIFO, LIFO, HIFO, AVERAGE. Required.FIFO
feePolicyNofeePolicy, string, one of add_to_basis_and_deduct_from_proceeds, ignore. Required.add_to_basis_and_deduct_from_proceeds
calendarYearYescalendarYear, integer, from -9007199254740991 to 9007199254740991. Required.
fiatCurrencyNofiatCurrency, string, length 3 to 3. Required.EUR

Output Schema

NameRequiredDescriptionDefault
exemptNoexempt. Boolean.
methodNomethod. String.
reasonNoreason. String.
sourcesNosources. Array.
disposalsNodisposals. Array.
limitationsNolimitations. Array.
calendarYearNocalendarYear. Number.
taxableGainTotalNotaxableGainTotal. 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?

Goes beyond the annotations by disclosing the price ($0.04 USDC), the x402 payment gate, and the crucial fact that an unpaid call returns payment terms without running the computation — behavior the readOnly/idempotent hints cannot convey. It stops short of describing output semantics or any rate/limit behavior.

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, front-loaded with purpose and followed by price, endpoint, and the payment-gate caveat. Nothing is padded and nothing essential is buried.

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 no explanation, and the payment/auth behavior is well covered. Minor gaps remain around how calendarYear bounds the analysis and what the classification result signifies, but the definition is sufficient to invoke 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%, so the schema carries the parameter documentation and the baseline of 3 applies. The description only hints at the method override ("FIFO (or caller method)") and the year scope; it adds no detail on ledger item fields, feePolicy, or fiatCurrency.

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 ("Classify crypto private sales") and pins the legal regime (§23 EStG, one-year holding, €1,000 Freigrenze), which cleanly separates it from the other jurisdictional siblings like australia-cgt-discount or us-form-8949-rows.

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 German-jurisdiction framing implies when to use it, but there is no explicit when-to-use/when-not statement and no routing advice against the sibling country-specific tools. An agent must infer the alternative from the tax regime named.

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