Skip to main content
Glama
Sign In

papertax

by io.github.AwakeWeb3
OverviewDiscussionsAdmin

Explain default tax treatment

explain_tax_treatment
Read-onlyIdempotent

papertax's default treatment notes for Australia, the US, the UK, Canada, New Zealand, Japan or Spain, optionally for one event type. Not tax advice.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "explain_tax_treatment"
  }
}

Input Schema

NameRequiredDescriptionDefault
event_typeNo
jurisdictionNoUsed when tax_year is not given. AU = 1 Jul–30 Jun; US, CA, JP and ES = calendar year; UK = 6 Apr–5 Apr; NZ = 1 Apr–31 MarAU

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / event_type / enum
      Previous value: -[
-  "loss",
-  "liq",
-  "gain",
-  "queued",
-  "funding",
-  "mint",
-  "stakepay",
-  "spotgain",
-  "spotloss",
-  "vaultgain",
-  "vaultloss",
-  "income",
-  "airdrop",
-  "xfer",
-  "evmswap",
-  "defiin",
-  "defiout",
-  "receive"
-]New value: +[
+  "loss",
+  "liq",
+  "gain",
+  "queued",
+  "funding",
+  "mint",
+  "stakepay",
+  "spotgain",
+  "spotloss",
+  "vaultgain",
+  "vaultloss",
+  "income",
+  "airdrop",
+  "xfer",
+  "evmswap",
+  "defiin",
+  "defiout",
+  "receive",
+  "loan",
+  "unknown"
+]
  2. Changed2 schema fields changed
    • changedInput schema / properties / jurisdiction / description
      Previous value: -"Used when tax_year is not given. AU = 1 Jul–30 Jun; US and CA = calendar year; UK = 6 Apr–5 Apr; NZ = 1 Apr–31 Mar"New value: +"Used when tax_year is not given. AU = 1 Jul–30 Jun; US, CA, JP and ES = calendar year; UK = 6 Apr–5 Apr; NZ = 1 Apr–31 Mar"
    • changedInput schema / properties / jurisdiction / enum
      Previous value: -[
-  "AU",
-  "US",
-  "UK",
-  "CA",
-  "NZ"
-]New value: +[
+  "AU",
+  "US",
+  "UK",
+  "CA",
+  "NZ",
+  "JP",
+  "ES"
+]
  3. Changed2 schema fields changed
    • changedInput schema / properties / jurisdiction / description
      Previous value: -"Used when tax_year is not given. AU = financial year 1 Jul–30 Jun; US = calendar year"New value: +"Used when tax_year is not given. AU = 1 Jul–30 Jun; US and CA = calendar year; UK = 6 Apr–5 Apr; NZ = 1 Apr–31 Mar"
    • changedInput schema / properties / jurisdiction / enum
      Previous value: -[
-  "AU",
-  "US"
-]New value: +[
+  "AU",
+  "US",
+  "UK",
+  "CA",
+  "NZ"
+]
  4. Changed1 schema field changed
    • changedInput schema / properties / event_type / enum
      Previous value: -[
-  "loss",
-  "liq",
-  "gain",
-  "queued",
-  "funding",
-  "mint",
-  "stakepay"
-]New value: +[
+  "loss",
+  "liq",
+  "gain",
+  "queued",
+  "funding",
+  "mint",
+  "stakepay",
+  "spotgain",
+  "spotloss",
+  "vaultgain",
+  "vaultloss",
+  "income",
+  "airdrop",
+  "xfer",
+  "evmswap",
+  "defiin",
+  "defiout",
+  "receive"
+]
  5. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare this as a read-only, idempotent, closed-world lookup, so the safety bar is low. The description adds the meaningful caveat 'Not tax advice,' signalling these are static default notes rather than personalized advice, but it doesn't say what is returned or what happens when event_type is omitted.

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?

A single sentence with no filler; the supported jurisdictions are listed up front and the optional filter is stated last. Every clause carries information.

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?

With only two optional parameters, full annotation coverage and no output schema, the description is close to sufficient: it names the jurisdiction set, the optional filter, and the disclaimer. It would be stronger if it stated the default behavior when no event_type is supplied.

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 coverage is 50%: jurisdiction carries a rich schema description (tax-year boundaries), so the description correctly doesn't repeat it, and 'optionally for one event type' conveys that event_type is an optional filter. However, cryptic enum members such as 'liq', 'stakepay' and 'queued' are explained nowhere, so the description leaves real ambiguity in the parameter it does mention.

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 concrete resource — 'papertax's default treatment notes' — and enumerates the seven supported jurisdictions, so an agent can tell this apart from siblings like get_tax_summary or export_tax_file. The verb is only implicit ('explain' from the name), but the output object is unambiguous.

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 only implied: an agent can infer this is a reference lookup for default treatment, optionally narrowed to one event type. No alternative is named (get_tax_summary is the obvious candidate to compare against) and no conditions for choosing between them are given.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All papertax toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources