Skip to main content
Glama
iseppo

e-arveldaja MCP Server

by iseppo

Check Tax-Free Limits

check_tax_free_limits
Read-onlyIdempotent

Calculate cumulative tax-free limits for representation costs (€50/month + 2% of payroll) and donations (3% of payroll or 10% of prior-year profit), then compute 22/78 income tax on any excess. Uses year-to-date payroll and profit figures.

Instructions

Compute cumulative TuMS § 49 tax-free limits (representation 50 €/month + 2% of payroll; donations 3% of payroll or 10% of prior-year profit) and the 22/78 income tax on any excess. Pure calculator over caller-supplied year-to-date figures (payroll from the TSD declaration, prior-year profit from compute_profit_and_loss); it does not read the ledger.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
as_of_dateYesDate the cumulative figures are taken as of (YYYY-MM-DD). Sets the 22/78 rate and the default months elapsed.
ytd_donationsNoYear-to-date gifts/donations to listed associations. Omit to skip the donation limit.
donation_basisNoWhich donation limit to apply: 3% payroll, 10% prior-year profit, or the more favourable (default max).
months_elapsedNoCalendar months elapsed for the representation 50 €/month accrual. Defaults to the month of as_of_date.
prior_year_profitNoPrior financial year's profit (for the donation 10% alternative). Defaults to 0.
ytd_representation_costsNoYear-to-date representation/entertainment costs booked. Omit to skip the representation limit.
ytd_social_taxed_payrollYesYear-to-date payments subject to social tax (the 2%/3% base).
Behavior4/5

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

Annotations indicate readOnly, idempotent, non-destructive. The description adds that it is a pure calculator that does not read the ledger, reinforcing its safe and stateless nature. No contradictions.

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?

Two sentences, each delivering critical information: first the core function with specific rules, second clarifying it is a calculator without ledger access. Efficient, front-loaded, no redundancy.

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?

Given 7 parameters, no output schema, the description explains the calculation and input sources. It could mention the return format, but overall it provides sufficient context for a calculator tool.

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

Parameters4/5

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

Schema has 100% coverage with individual parameter descriptions. The tool description adds value by explaining the calculation formulas and the source of inputs, providing context 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?

The description clearly states the tool computes cumulative tax-free limits under TuMS § 49 and the income tax on excess, with specific formulas. It distinguishes itself from siblings as a pure calculator that does not read the ledger, making its purpose unambiguous.

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?

The description explains it is a pure calculator over caller-supplied figures, specifying where inputs like payroll and prior-year profit come from. While it does not explicitly list exclusions, it provides clear context on when to use this tool versus alternative data sources.

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/iseppo/e-arveldaja-mcp'

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