Skip to main content
Glama

Hlídač spoření

Get one savings account or term deposit

hlidac_get_product
Read-onlyIdempotent

Full detail of one product (spořicí účet or termínovaný vklad): rate bands, conditions, end of a promotion, deposit insurance (pojištění vkladu), early withdrawal, tax, when it was verified, and the facts we do not have (unknown).

product_id comes from hlidac_compare_savings or hlidac_compare_term_deposits, e.g. 'trinity', 'ceska-sporitelna', 'tv-csob'. An unknown id returns the list of valid ids.

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": {
      "product_id": "<product_id>"
    },
    "name": "hlidac_get_product"
  }
}

Input Schema

NameRequiredDescriptionDefault
product_idYesProduct id from a comparison result, e.g. 'trinity' (spořicí účet) or 'tv-csob' (termínovaný vklad)

Output Schema

NameRequiredDescriptionDefault
asOfYesWhen the rates were last updated (ISO 8601)
bankYes
kindYes
staleYes
productYes
savingsNo
unknownYesFacts we do not have for this product; never guess them
bank_urlYes
detail_urlYes
product_idYes
attributionYes
verified_atYes
term_depositNo
deposit_insuranceYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedOutput schema / properties / savings / properties / interest_payout
      Added value: +{
      +  "description": "How interest accrues and when it is credited, verified from the bank terms; null = unknown",
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • changedOutput schema / properties / savings / required
      Previous value: -[
      -  "tier_mode",
      -  "bands",
      -  "investment_bands",
      -  "conditions",
      -  "condition_kinds",
      -  "investment_requirement",
      -  "rate_without_conditions",
      -  "promo_until",
      -  "note",
      -  "examples"
      -]New value: +[
      +  "tier_mode",
      +  "bands",
      +  "investment_bands",
      +  "conditions",
      +  "condition_kinds",
      +  "investment_requirement",
      +  "rate_without_conditions",
      +  "promo_until",
      +  "note",
      +  "interest_payout",
      +  "examples"
      +]
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare read-only, idempotent, and non-destructive behavior, but the description adds concrete context: the response covers rate bands, conditions, promotion end, deposit insurance, early withdrawal, tax, verification, and unknowns. It also discloses that an unknown id returns valid ids, which is useful behavioral information beyond annotations.

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 paragraphs, front-loaded with the purpose; the field list and ID-source note both earn their place. The first sentence is long but remains scannable and does not waste much space.

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 one-parameter lookup with a full output schema and rich annotations, the description supplies what remains: what detail is returned, where product_id comes from, and fallback behavior for unknown ids. Nothing needed to invoke it correctly is missing.

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% and the single product_id parameter already has a pattern and example. The description adds meaning beyond the schema by naming the two source comparison tools and describing the unknown-id behavior, though it does not add syntax details.

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 ('Full detail') and resource ('one product'), scoped to savings accounts and term deposits, and distinguishes from comparison siblings by singular-product focus and by naming where product_id comes from. An agent can identify it as the detail lookup rather than a comparison tool.

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 routes product_id from hlidac_compare_savings or hlidac_compare_term_deposits and gives examples, so the intended sequence is clear. It stops short of an explicit when-not statement or naming hlidac_plan_allocation, so it is not full 5.

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