Skip to main content
Glama

Take-home pay

net_pay
Read-onlyIdempotent

Take-home pay for a gross yearly salary in a country (and region or city, for regional and municipal taxes), with every tax line, the model's caveats and its official sources. Takes age, children, a pension share, a newcomer regime, and a partner (joint filing for a married couple where the country has it).

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": {
      "gross": "<gross>"
    },
    "name": "net_pay"
  }
}

Input Schema

NameRequiredDescriptionDefault
ageNoAge in years, where the tax uses it
cityNoCity id or name; sets country, region and municipal taxes
grossYesGross yearly salary
tweakNo
regimeNoA newcomer regime id for this country (list_metrics_and_sources kind "regimes")
regionNoISO 3166-2 subdivision, e.g. US-CA, GB-SCT, IT-21
countryNoISO alpha-2 or name; optional when city is given
partnerNoA second earner in the same household
pensionNoPension share of gross, 0.05 = 5%
childrenNoChildren's ages, for child credits and allowances
currencyNoCurrency of gross; default the country's
displayCurrencyNo

Output Schema

NameRequiredDescriptionDefault
netYes
grossYes
linesYes
caveatsYes
countryYes
sourcesYes
currencyYes
effectiveRateYes
reportVersionYesThe report's shape version (now 2.0)

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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 read-only, idempotent, closed-world behavior, so the safety profile is covered. The description adds real value by disclosing that the result includes tax lines, the model's caveats and official sources, hinting at estimation uncertainty. It still doesn't say what tax year or dataset vintage the model uses, or how it behaves for unsupported country/city combinations.

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?

Two dense, front-loaded sentences: the primary output and scope come first, the optional levers second. Some of the second sentence reads as a parameter recital that largely duplicates the schema, but no sentence is padded or vague.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is complex (12 parameters, nested partner/tweak objects), but it has an output schema so return shape needn't be explained. What's missing is guidance on parameter interplay – e.g. that city supersedes country, that region expects ISO 3166-2 codes, that regime ids come from list_metrics_and_sources – which the description leaves to the schema.

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 83%, so the schema already documents nearly every parameter, including pension share, children's ages, and the tweak object. The description adds only a packaged summary ('age, children, a pension share, a newcomer regime, and a partner') and clarifies that partner enables joint filing for a married couple, which the schema only partly conveys.

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 names the specific computation ('Take-home pay for a gross yearly salary') and its geographic scoping (country, plus region or city where local taxes apply), and the returned content (every tax line, caveats, sources). It is clearly distinct from siblings like get_city or compare_cities, which read city data rather than compute a payroll result.

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 by the description's feature list – you call it when you want a full take-home breakdown for a salary. However, it never states when NOT to use it or points to a specific alternative (e.g. compare_cities for multi-city comparison, list_metrics_and_sources for regime ids), leaving the agent to infer routing.

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.