Skip to main content
Glama

Verako

Compare Norwegian savings accounts

compare_savings_accounts
Read-onlyIdempotent

Compare Norwegian savings accounts (sparekonto, høyrentekonto) for an amount, and check whether the user's savings rate is good ('Er sparerenten min god?'). Ranked by interest earned in a year after fees, with conditions, withdrawal rules, deposit guarantee, sources and the data date. Ranking is by yield only; each offer states whether we earn a commission. Needs no personal data. Norway only. Rates change often. Data provided by finansportalen.no, checked every hour; every answer says when it was last updated. Users never pay us.

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_nok": "<amount_nok>"
    },
    "name": "compare_savings_accounts"
  }
}

Input Schema

NameRequiredDescriptionDefault
amount_nokYesThe amount to save, in whole kroner
max_notice_daysNoLongest notice before a withdrawal the user accepts, in days, 0-365; default 0 (instant access). The data has: 0, 30, 31, 32, 60, 90, 180, 360
current_rate_pctNoThe user's current savings rate in per cent, e.g. 3.5
withdrawals_per_yearNoExpected withdrawals a year; default 4

Output Schema

NameRequiredDescriptionDefault
queryYes
answerYes
offersYes
currentYes
sourcesYes
verdictYes
coverageYes
warningsYes
answer_nbYes
disclosureYes
attributionYes
warnings_nbYes
not_includedYes
product_typeYes
ranking_ruleYes
disclosure_nbYes
answer_detailsYes
not_included_nbYes
ranking_rule_nbYes
answer_details_nbYes
disclosure_web_enYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / required
      Previous value: -[
      -  "product_type",
      -  "verdict",
      -  "answer",
      -  "answer_nb",
      -  "answer_details",
      -  "answer_details_nb",
      -  "current",
      -  "coverage",
      -  "ranking_rule",
      -  "ranking_rule_nb",
      -  "disclosure",
      -  "disclosure_nb",
      -  "disclosure_web_en",
      -  "not_included",
      -  "not_included_nb",
      -  "warnings",
      -  "warnings_nb",
      -  "sources",
      -  "attribution",
      -  "query",
      -  "offers"
      -]New value: +[
      +  "product_type",
      +  "verdict",
      +  "answer",
      +  "answer_nb",
      +  "answer_details",
      +  "answer_details_nb",
      +  "coverage",
      +  "ranking_rule",
      +  "ranking_rule_nb",
      +  "disclosure",
      +  "disclosure_nb",
      +  "disclosure_web_en",
      +  "not_included",
      +  "not_included_nb",
      +  "warnings",
      +  "warnings_nb",
      +  "sources",
      +  "attribution",
      +  "current",
      +  "query",
      +  "offers"
      +]
  2. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Beyond the read-only, idempotent, non-destructive annotations, it explains yield-after-fee ranking, commission disclosure, included conditions and withdrawal rules, deposit guarantee, data source finansportalen.no, hourly refresh, and update timestamps. This is rich behavioral context and does not contradict the 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?

The description is front-loaded with purpose and use case, and most sentences add material transparency. It is somewhat long and the freshness/payment-model points could be tightened, but it is not bloated.

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?

Given the output schema and read-only annotations, the description covers the key selection and invocation context: scope, ranking basis, included offer details, data freshness, commission model, and privacy. No material gap remains for an agent to use it correctly.

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?

With 100% schema coverage, amount_nok, max_notice_days, current_rate_pct, and withdrawals_per_year are already fully documented in the schema. The description reinforces 'for an amount' and the rate-check use case, but adds little parameter-specific detail beyond that.

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 gives a specific verb ('Compare') and resource ('Norwegian savings accounts'), including local terms and a secondary use case of checking the user's rate. It is clearly scoped, but it does not explicitly distinguish itself from related siblings such as fixed-term deposits or rate explanation.

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?

It supplies clear usage context: compare for a stated amount, optionally check the user's current rate, Norway only, and no personal data required. It does not explicitly state when to use this instead of compare_fixed_term_deposits or explain_rate_offer, so alternative selection remains implicit.

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