Skip to main content
Glama
Sign In
e-arveldaja MCP Server

e-arveldaja MCP Server

by iseppo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Check Tax-Free Limits

check_tax_free_limits
Read-onlyIdempotent

Compute cumulative TuMS §49 tax-free limits for representation and donations, and 22/78 income tax on excess, using year-to-date payroll and profit inputs.

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 (rates date-gated). 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.

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": {
      "as_of_date": "<as_of_date>",
      "ytd_social_taxed_payroll": "<ytd_social_taxed_payroll>"
    },
    "name": "check_tax_free_limits"
  }
}

Input 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).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.29.2
    • addedInput schema / additionalProperties
      Added value: +false
  2. Addedv0.25.3
  3. Removedv0.25.2
  4. First observedv0.18.1

TDQS

A4.4/5.0
Behavior4/5

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

Annotations cover the safety profile (readOnly, idempotent, non-destructive). The description adds meaningful context beyond that: it is a pure calculator with no ledger access, and it discloses the date-gated rate behavior. It doesn't spell out return format, but with no output schema present this is a minor gap.

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 sentences that front-load the core computation and then the scope boundary. It is information-rich without padding, though the parenthetical formula list is tight enough to be slightly heavy on first read.

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

Completeness5/5

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

For a pure-calculation tool, the definition covers what it computes, the rate logic, the data source boundary, and the origin of each input. Nothing material is missing for an agent to invoke it correctly.

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 coverage is 100%, so the schema already documents every parameter well, including defaults and omissibility. The description adds cross-tool provenance for two inputs (TSD declaration, compute_profit_and_loss), which is genuine value 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 (compute) and resource (cumulative TuMS § 49 tax-free limits) with the exact formulas and rates involved. It is clearly distinguishable from sibling calculators like compute_profit_and_loss or compute_trial_balance.

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?

Explicitly defines what it is NOT: 'Pure calculator over caller-supplied year-to-date figures ... it does not read the ledger,' and names the sources for inputs (TSD declaration, compute_profit_and_loss). This positions it well, though it doesn't state when passing which optional args matters or when to skip it entirely.

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

Deploy Server

Other Tools