Skip to main content
Glama

BRAINIAC Crypto Tax Computation

Australian CGT discount

crypto-tax_australia-cgt-discount
Read-onlyIdempotent

Apply the Australian 12-month CGT discount by entity type after losses, from caller event proceeds and cost base. Price $0.03 USDC. POST /api/v1/crypto-tax/australia-cgt-discount. 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": {
      "entity": "<entity>",
      "resident": "<resident>",
      "events": "<events>"
    },
    "name": "crypto-tax_australia-cgt-discount"
  }
}

Input Schema

NameRequiredDescriptionDefault
entityYesentity, string, one of individual, trust, super_fund, company. Required.
eventsYesevents, array. Required.
residentYesresident, boolean. Required.
carriedForwardLossesNocarriedForwardLosses, integer, from 0 to 9007199254740991. Required.

Output Schema

NameRequiredDescriptionDefault
eventsNoevents. Array.
sourcesNosources. Array.
grossGainsNogrossGains. Number.
limitationsNolimitations. Array.
discountRateNodiscountRate. Number.
lossesAppliedNolossesApplied. Number.
netCapitalGainNonetCapitalGain. Number.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent and non-destructive, so the safety bar is met; the description goes further with behavior the annotations cannot convey: a $0.03 USDC price, the concrete POST endpoint, and the crucial fact that an unpaid invocation returns x402 payment terms instead of executing. It also discloses the computation ordering ('after losses'), which changes the result materially. It stops short of stating how carried-forward losses or non-resident status alter the output.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three tightly packed sentences, front-loaded with the operation and followed by commercial/transport details, with no filler. The endpoint and pricing sentences are utilitarian rather than descriptive of the tool's domain behavior, but they earn their place by preventing a failed unpaid call.

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-value explanation is not required, and the payment/transport mechanics are fully covered for typical agent use. What is missing is domain-level: the discount rate per entity type, the treatment of non-residents, and how existing losses interact with the 12-month threshold, any of which an agent might otherwise assume.

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 already documents all four parameters and the nested event fields; baseline 3 applies. The description adds some semantic value by indicating proceeds/cost base come from the caller's events and that losses are applied before the discount (clarifying the role of carriedForwardLosses), but it never mentions the required `resident` flag or its effect.

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') on a specific resource ('Australian 12-month CGT discount') and adds the qualifying scope ('by entity type after losses, from caller event proceeds and cost base'). The Australian jurisdiction plus the discount/after-losses framing clearly separates it from siblings such as crypto-tax_canada-acb or crypto-tax_germany-holding-period without needing to open any 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?

Usage is implied rather than stated: the agent can infer this is the tool for Australian CGT discount computation once events and a cost base exist, and the payment sentence gives one real precondition (unpaid calls return x402 terms and do not run). However, it names no alternative tool and gives no explicit exclusion or prerequisite ordering relative to siblings like crypto-tax_cost-basis-lots.

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