Skip to main content
Glama

list_deductions

Retrieve the deduction sheet ESTV derives for a household, showing each line item and marking editable fields for custom tax input.

Instructions

Show the deduction/budget sheet ESTV derives for a household.

Returns every line item with the value ESTV assumes by default. Lines marked editable can be overridden through the deductions argument of calculate_tax (keyed by id), e.g. PRAEMIEN3A for pillar 3a contributions or SCHULDZINSEN for mortgage interest. Non-editable lines (gross salary, AHV/ALV/BVG contributions) are computed by the model.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
age1No
age2No
wealthNoNet wealth at year end, CHF.
income1YesAnnual income of person 1, CHF.
income2NoAnnual income of the spouse, CHF.
languageNode
locationYesTax location id, postal code or municipality name.
tax_yearNo
confession1Nonone
confession2No
income_type1Noemployed
income_type2Noemployed
relationshipNosingle
children_agesNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

With no annotations, the description carries the full burden. It discloses that the tool returns every line item with default values and distinguishes editable vs non-editable lines. It does not mention side effects, but the read-only nature is implied. It provides useful behavioral context beyond what a bare schema would give.

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?

The description is three sentences long, well-structured, and front-loads the purpose. Every sentence adds value: purpose, output format, and relation to sibling tool. No wasted words.

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?

Despite having an output schema, the description omits any link between input parameters and the output deductions. With 14 parameters and low schema coverage, the description should provide more context on how parameters influence results. It explains the output well but is incomplete for a complex tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 29%, meaning most parameters lack descriptions in the schema. The tool description does not explain any parameters or how they affect the output. Given this gap, the description should have compensated but did not, leaving agents uninformed about input semantics.

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 clearly states 'Show the deduction/budget sheet ESTV derives for a household', specifying both the verb ('show') and the resource (deduction sheet). It distinguishes from sibling tools by mentioning how editable lines can be overridden in `calculate_tax`, providing context on how this tool fits into the workflow.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Although the description does not explicitly state when to use or not use this tool, it strongly implies that it is a read-only preview for default deductions before using `calculate_tax` for overrides. This provides clear context but lacks explicit alternative scenarios or when-not-to-use instructions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/noaahh/estv-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server