Skip to main content
Glama

Hlídač spoření

Compare Czech savings accounts

hlidac_compare_savings
Read-onlyIdempotent

Rank Czech savings accounts (spořicí účty) by the effective interest rate (úrok, sazba) for a given deposit, with the net yield after the 15 % tax.

The effective rate is computed for the WHOLE amount: many banks pay their headline rate only up to a limit (e.g. Česká spořitelna 5,20 % only up to 400 000 Kč), so the ranking changes with the amount. Filters drop accounts with card-payment, income or new-money conditions, or keep only accounts without conditions.

Examples:

  • "Kam dát 800 000 Kč na spořicí účet?" -> amount=800000

  • "Nejvyšší úrok bez podmínek pro 1 milion" -> amount=1000000, no_conditions=true Use hlidac_get_product for one account's bands and conditions, hlidac_plan_allocation to split a large sum across banks.

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": {
      "amount": "<amount>"
    },
    "name": "hlidac_compare_savings"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoHow many accounts to return, best first
amountYesDeposit in CZK (vklad v Kč), whole number 1 000–10 000 000, e.g. 800000
no_conditionsNoOnly accounts with no conditions at all (spořicí účet bez podmínek)
without_new_moneyNoExclude offers only for new money moved from another bank (bez nových peněz)
include_investmentNoCount the higher rate some banks pay with a regular investment
without_card_paymentsNoExclude accounts that require card payments (bez placení kartou)
without_income_requirementNoExclude accounts that require a regular income (bez požadavku na příjem)

Output Schema

NameRequiredDescriptionDefault
asOfYesWhen the rates were last updated (ISO 8601)
amountYes
accountsYes
attributionYes
comparison_urlYes
total_matchingYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered. The description adds substantive context beyond that: the effective rate is computed for the whole amount because headline rates are capped per bank (with a concrete Česká spořitelna example), the 15% tax is applied, and the optional filters drop conditioned accounts. It stops short of noting result ordering/output shape, but the output schema covers returns.

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?

Front-loaded with purpose and the key ranking mechanism, then examples, then sibling routing. Every sentence carries information an agent would otherwise have to guess; no filler or restatement of the title.

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 7-parameter read-only ranking tool with a full output schema, the description covers the computation model, tax treatment, filter semantics and sibling routing. Returns need not be described since an output schema exists, so nothing essential is missing.

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?

Schema description coverage is 100%, so all seven parameters are already documented in the schema and the baseline is 3. The description adds modest value by explaining why 'amount' matters (band caps) and by giving example mappings for amount and no_conditions, but it does not elaborate on the other filters beyond what the schema says.

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 and resource ('Rank Czech savings accounts by the effective interest rate for a given deposit') and immediately clarifies the net-of-tax and whole-amount basis. The final paragraph explicitly differentiates it from hlidac_get_product (single account bands/conditions) and hlidac_plan_allocation (splitting a large sum).

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

Usage Guidelines5/5

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

Explicitly names the two relevant alternatives and the condition that selects them, and supplies two worked natural-language examples mapping to concrete parameter values (amount=800000; amount=1000000, no_conditions=true). Nothing about when to reach for this tool versus its siblings is left to inference.

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