Skip to main content
Glama

Verako

Compare Norwegian fixed-term deposits

compare_fixed_term_deposits
Read-onlyIdempotent

Compare Norwegian fixed-term deposits (fastrenteinnskudd) for an amount and a term in months. Ranked by interest earned over the term, with early-withdrawal terms, 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_fixed_term_deposits"
  }
}

Input Schema

NameRequiredDescriptionDefault
amount_nokYesThe amount to deposit, in whole kroner
term_monthsNoTerm in months, 1-120; default 12. The data has: 3, 5, 6, 9, 12, 24, 36, 48, 60
current_rate_pctNoThe user's current rate in per cent, to compare against

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. First observed

TDQS

A4.2/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description adds meaningful behavior beyond that: ranking is by yield only, each offer discloses whether the operator earns a commission, data comes from finansportalen.no refreshed hourly, and every answer carries a last-updated timestamp. These are exactly the trust and freshness traits an agent needs and cannot get from structured fields.

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?

Front-loaded and dense: purpose, ranking basis, return contents, privacy, geography, and data provenance in a handful of short sentences. The telegraphic fragments ("Norway only. Rates change often.") are efficient, though the closing "Users never pay us" is more marketing than operational guidance.

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?

An output schema exists, yet the description still summarizes the return payload (interest earned over term, early-withdrawal terms, deposit guarantee, sources, data date) and discloses data provenance and freshness. For a read-only, three-parameter comparison tool, nothing an agent needs to call it correctly 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 three parameters are already documented, establishing a baseline of 3. The description only restates the amount/term dimension and adds nothing about behavior of the free-range term_months against the discrete rate set the schema lists (3/5/6/9/12/24/36/48/60), nor about how current_rate_pct affects output.

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?

The description opens with a specific verb and resource: "Compare Norwegian fixed-term deposits (fastrenteinnskudd)", and scopes it to "an amount and a term in months". The resource and country qualifier distinguish it cleanly from the sibling comparison tools (savings accounts, electricity contracts) without needing the schemas.

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?

It gives implied context ("Norway only", "Needs no personal data", "Rates change often") that helps an agent decide the tool is appropriate, but it never names an alternative or states when-not to use it — e.g. it doesn't point to compare_savings_accounts for non-fixed-term products. Usage is inferable rather than instructed.

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