Skip to main content
Glama

Verako

Explain a savings or deposit offer

explain_rate_offer
Read-onlyIdempotent

Explain one savings account or fixed-term deposit from a comparison in plain language (English and Norwegian): the rate, fees and conditions, what it gives or costs for the given amount (or for stated example figures), its source and date, and whether we earn a commission. Savings and deposit data: Data provided by finansportalen.no, checked every hour; every answer says when it was last updated.

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": {
      "offer_id": "<offer_id>"
    },
    "name": "explain_rate_offer"
  }
}

Input Schema

NameRequiredDescriptionDefault
offer_idYesThe offer_id from a comparison
amount_nokNoAmount to save or deposit, in whole kroner

Output Schema

NameRequiredDescriptionDefault
offerYes
sourcesYes
standingYes
data_noteYes
disclosureYes
attributionYes
explanationYes
standing_nbYes
data_note_nbYes
disclosure_nbYes
explanation_nbYes
reference_inputsYes
standing_short_enYes
standing_short_nbYes
rank_at_reference_inputsYes
offers_at_reference_inputsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely new behavior: data provenance (finansportalen.no), hourly refresh, that every answer carries a last-updated timestamp, that commission disclosure is included, and that output is available in English and Norwegian. Only the concrete response shape is left out, which the output schema covers.

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?

The core purpose is front-loaded in the first clause, and the enumerated contents of the explanation are compact and informative. The closing provenance sentence ('Data provided by finansportalen.no, checked every hour...') partly repeats the freshness point already made by 'its source and date', making the sentence denser than necessary, though nothing is off-topic.

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?

The tool is a read-only single-record explainer with an output schema, so return-value structure need not be described. The description covers what is explained, data freshness, provenance and commission disclosure. The one omission is how an offer_id is obtained (presumably from the comparison siblings), which is left implicit.

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 the schema already defines both parameters, giving a baseline of 3. The description adds one piece of meaning the schema does not: when no amount is supplied the explanation falls back to 'stated example figures', clarifying the null default on amount_nok. That is a modest gain, not a full explanation of parameter behavior.

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 opens with a specific verb and resource: 'Explain one savings account or fixed-term deposit from a comparison in plain language'. It also enumerates what the explanation covers (rate, fees, conditions, net cost/benefit, source, date, commission), which distinguishes it from a bulk comparison tool. It stops short of naming the sibling (e.g. compare_savings_accounts) it contrasts with, so the differentiation is implied rather than explicit.

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 'one ... offer from a comparison' and the requirement of an offer_id, suggesting this is the follow-up drill-down after a comparison. There is no explicit when-to-use / when-not-to-use statement and no named alternative for the multi-offer case, which is left for the agent to infer from sibling names.

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