Skip to main content
Glama

IUSTORIA – průvodci a právní kalkulačky

Úrok z dlužného výživného

urok_z_vyzivneho
Read-onlyIdempotent

Spočítá úrok z prodlení s placením výživného, z každé měsíční dávky zvlášť. U nezletilého dítěte a prodlení od 1. 1. 2026 prvních šest měsíců 2,5 promile denně, potom repo sazba ČNB + 8 procentních bodů ročně; u ostatních oprávněných repo sazba + 8 p. b. po celou dobu. EN: Calculates Czech default interest on unpaid maintenance, month by month.

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": {
      "castka": "<castka>",
      "prvni": "<prvni>",
      "pocet": "<pocet>"
    },
    "name": "urok_z_vyzivneho"
  }
}

Input Schema

NameRequiredDescriptionDefault
komuNoPro koho je výživné: nezletile = Nezletilé dítě (Dítě, které ještě nenabylo plné svéprávnosti.); jine = Zletilé dítě nebo bývalý manžel (Zvýšený úrok se nepoužije.). Bez zadání nezletile. EN: Who receives maintenance.
pocetYesPočet nezaplacených měsíců (1 až 240). EN: Number of unpaid months.
prvniYesSplatnost první nezaplacené dávky, RRRR-MM-DD (den z rozsudku nebo dohody). Další měsíce se počítají se stejným dnem. EN: Due date of the first unpaid instalment.
castkaYesDlužná částka výživného za měsíc v Kč. EN: Monthly amount in CZK.
ke_dniNoDen, ke kterému se úrok počítá (včetně), RRRR-MM-DD. Bez zadání dnešek (Praha). EN: Reference date YYYY-MM-DD; defaults to today (Prague).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare this as a read-only, idempotent, non-destructive calculator, so the safety profile is covered. The description goes beyond them by disclosing the actual computation rule: 2.5 per mille daily for the first six months for minors with delay from 1 Jan 2026, then CNB repo rate + 8 percentage points annually, versus repo + 8 p.p. throughout for other entitled persons. This is substantive behavioral context for verifying results, though it does not mention rounding or output shape.

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 front-loaded sentences: the purpose first, then the rate rules, then a short English gloss. The formula clause is dense but every element is load-bearing; nothing is padded, though the string of rate conditions is harder to parse than a bulleted split would be.

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?

For a five-parameter, read-only calculator with fully documented parameters and no output schema, the description supplies the domain logic needed to call and sanity-check it. The remaining gap is that it never says whether the result is a single total or a per-month breakdown, which matters given the stated month-by-month method.

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 description coverage is 100%, so the baseline would be 3. The description earns more by explaining that the calculation runs month by month per instalment, which clarifies how 'prvni' and 'pocet' combine, and by tying the two rate regimes to the 'komu' enum values, adding meaning the schema alone does not convey.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb and resource ('Spočítá úrok z prodlení s placením výživného') and scopes it to per-instalment calculation, which tells an agent this is a maintenance-arrears interest calculator rather than a general interest tool. It does not explicitly name the related siblings ('urok_z_prodleni', 'uroky'), so the differentiation is inferable rather than stated.

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 domain framing (unpaid maintenance instalments), and the rate rules hint at the scenarios covered. There is no explicit when-to-use / when-not-to-use guidance, nor any pointer to the closely related sibling tools for other interest calculations, so an agent must infer the boundary itself.

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.

Resources