Skip to main content
Glama

tax-engine

by cz.freelax

Paušální daň year-end settlement

calc_flat_tax_settlement
Read-only

Given the paušální daň band you paid and the actual annual income, computes whether you owe a doplatek (top-up), get a vratka (refund), or must exit the flat-tax regime (income above 2,000,000 CZK).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
currentBandYesBand actually paid during the year
isProjectionNoTrue for a mid-year projection instead of a final settlement
monthsInRegimeNo
flatRatePercentNoFlat-rate expense percentage as a decimal: 0.4 (other business), 0.6 (most freelancers / živnost volná), 0.8 (craft trades)
actualAnnualIncomeYes

TDQS

A3.9/5.0
Behavior4/5

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

The readOnlyHint annotation already covers safety, and the description adds useful behavioral context: the 2,000,000 CZK exit threshold and the three possible outcomes. It does not contradict the annotation and provides additional edge-case information.

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 a single, well-structured sentence that front-loads the core purpose and includes a key threshold. No unnecessary words or repetition.

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?

Without an output schema, the description should clarify the return structure; it only states the tool 'computes whether' without detailing how results are formatted. The optional parameters and projection mode are not mentioned, which is a notable gap for a tool with this complexity.

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?

The description clarifies currentBand and actualAnnualIncome, which are the two required parameters, but it does not explain isProjection, monthsInRegime, or flatRatePercent. With 60% schema coverage, it partially compensates but leaves a gap.

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 uses a specific verb ('computes') and resource ('paušální daň settlement') and clarifies the outcome types (doplatek, vratka, exit). It distinguishes itself from sibling tools by focusing on the settlement decision rather than eligibility or thresholds.

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?

The context of a year-end settlement is implied, but there is no explicit guidance on when to use this tool over siblings like check_flat_tax_eligibility or compare_regimes. No alternatives or exclusions are mentioned.

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

All tax-engine toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.8/5.0
Disambiguation4/5

Most tools have clear distinct purposes, but calc_set_aside overlaps with compute_year (both compute safe-to-spend) and the flat-tax tools (check_flat_tax_eligibility, get_flat_tax_band, calc_flat_tax_settlement) could be confused without careful reading. Overall, descriptions are detailed enough to resolve ambiguity.

Naming Consistency4/5

Nearly all tools follow a verb_noun pattern, but 'czech_working_days' is a noun phrase and the verbs vary (calc, compute, check, compare, convert, estimate, get). The use of both 'calc' and 'compute' for calculations is a minor inconsistency, but the pattern is still readable and predictable.

Tool Count5/5

14 tools is well within the ideal range for a complex tax domain. Each tool addresses a distinct aspect (calculations, eligibility, deadlines, penalties, rules, currency, working days) and none seems redundant, making the count appropriate.

Completeness4/5

The tool surface covers the main OSVČ tax lifecycle: income tax, social/health insurance, flat tax, VAT thresholds, deadlines, penalties, and working days. A notable gap is the absence of a dedicated advance-payment (zálohy) calculation tool, though compute_year and get_rule_source can partially address this.

Resources