Skip to main content
Glama

get_tax_estimate

ESTIMATE of capital-gains tax in a country, in that country's currency: the country's cost method (FIFO, average cost, LIFO, UK pooling, annual sum), each trade converted at the ECB rate of its date, the rules of the year of sale, holding period, annual allowance and, where the law allows, losses carried from previous years. Not a tax return. Each country's options are in list_tax_countries (options field).

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": {
      "country": "<country>"
    },
    "name": "get_tax_estimate"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearNoTax year of the sales (optional). In the UK and Australia it is the year the tax year starts (2025 = 2025/26).
countryYesTwo-letter country code (e.g. PT, ES, US). See list_tax_countries.
alternativeNoBR, PT, AR and AT only: the alternative option for where the coins are held (BR foreign exchange; PT broker outside the EU/EEA with no tax treaty; AR sale in pesos; AT Austrian platform).
marginalRateNoOnly where the rate depends on income (DE, GB, US, CA, AU, LU, MX): the person's marginal rate as a fraction (0.35 = 35%). Without it the top rate is used.
marginalRateLongNoUS only: the person's long-term rate as a fraction (0, 0.15 or 0.20, plus 0.038 NIIT if applicable).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observed

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does substantial work: it discloses the exact computation model (country cost method, ECB rate at trade date, year-of-sale rules, holding period, annual allowance, permitted loss carryforward) and that the result is an estimate in local currency, not a filing. It stops short of stating read-only semantics, data prerequisites, or latency, but the computational contract is unusually well exposed.

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?

Front-loaded with the key framing ('ESTIMATE ... in that country's currency') followed by a dense but purposeful enumeration of the factors considered. It is a single run-on sentence with heavy comma splicing, which costs a little readability, but no clause is filler.

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?

For a five-parameter, no-annotation, no-output-schema tool, the description covers what is computed, in what currency, under what rules, and what it is not (a tax return). The main remaining gap is what the response contains (single total vs. per-disposal breakdown) and what input data must pre-exist, which an agent would want before trusting the number.

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; every parameter (year, country, alternative, marginalRate, marginalRateLong) is already documented in-schema with country scoping. The description adds only indirect meaning — that year rules drive the calculation and that country determines the option set — without adding format or edge-case detail beyond the schema.

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 ('ESTIMATE of capital-gains tax in a country') plus the denomination of the result, and the level of detail (cost method, ECB FX conversion, year rules, allowances, loss carryforward) makes it unmistakable against siblings like get_pnl or get_realized_gains. An agent can tell this is a jurisdiction-aware tax projection rather than a raw gains listing 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?

It supplies a prerequisite pointer ('Each country's options are in list_tax_countries (options field)') and a scope caveat ('Not a tax return'), which is genuine guidance. However it never says when to prefer this over get_realized_gains or get_pnl, nor what data must already exist (portfolio/trades) for a meaningful estimate, so usage is only implied.

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