Skip to main content
Glama

Verako

Compare Norwegian electricity contracts

compare_electricity_contracts
Read-onlyIdempotent

Compare Norwegian electricity contracts (strømavtaler) for a postcode and yearly usage, and check whether the user's current contract is a good deal ('Er strømavtalen min god?'). Returns offers ranked by yearly cost of markup (påslag) and monthly fee, with sources and the data date. Each offer says how long the supplier guarantees its markup and whether it can send one bill with the grid fee (nettleie), with the grid companies that applies to. Ranking is by cost only; each offer states whether we earn a commission. Returns the 20 lowest-cost offers plus the recommended one and the user's current one. Needs no personal data. Norway only.

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": {
      "postcode": "<postcode>",
      "annual_kwh": "<annual_kwh>"
    },
    "name": "compare_electricity_contracts"
  }
}

Input Schema

NameRequiredDescriptionDefault
postcodeYesNorwegian 4-digit postcode (postnummer)
annual_kwhYesYearly electricity use in kWh, from the bill or the grid company's app; a typical house uses 15 000-20 000
price_areaNoPrice area NO1-NO5, only if the postcode lookup is wrong; it is on the electricity bill
current_contractNoName of the current contract, e.g. 'Lyse Spotpris'
current_markup_ore_kwhNoas on the bill, incl. VAT
current_monthly_fee_nokNoas on the bill, incl. VAT

Output Schema

NameRequiredDescriptionDefault
queryYes
answerYes
offersYes
currentYes
sourcesYes
coverageYes
notes_enYes
notes_nbYes
warningsYes
answer_nbYes
disclosureYes
norgesprisYes
not_includedYes
ranking_ruleYes
verdict_kindYes
answer_web_enYes
disclosure_nbYes
answer_amount_nokYes
answer_details_enYes
answer_details_nbYes
disclosure_web_enYes
recommended_offer_idYes
answer_amount_label_enYes
answer_amount_label_nbYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the readOnly/idempotent annotations, the description discloses what the response contains (20 lowest-cost offers plus the recommended one and the user's current one), the ranking criterion, that offers carry sources and a data date, markup guarantee duration, single-bill/nettleie capability, and commission disclosure. That is meaningful behavioral context an agent cannot get from the structured fields alone.

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?

It is front-loaded with the primary purpose and the cost-ranking criterion, and no sentence is filler. It is, however, dense, with a long run of output-detail clauses that partly duplicate the output schema and could be trimmed.

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 six-parameter, read-only comparison tool with full schema coverage and an output schema, the description supplies everything needed: required inputs, optional current-contract inputs, geographic limit, ranking methodology, and disclosure of commercial interest in the ranking. Nothing essential to correct invocation 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%, so the baseline is 3, but the description adds the reason the optional current_* parameters exist: they enable the 'Er strømavtalen min god?' comparison against the user's existing deal. It also frames postcode and annual_kwh as the entry point for the whole comparison, adding intent beyond the field-level text.

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 names a specific verb and resource ('Compare Norwegian electricity contracts') and adds a second, clearly stated function ('check whether the user's current contract is a good deal'). Scope constraints ('Norway only') and the ranking basis ('yearly cost of markup and monthly fee') make it distinguishable at a glance from the sibling comparison tools, which target deposits and savings accounts.

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 gives clear context for use: a postcode plus yearly usage, optionally the user's current contract terms, and explicitly says 'Needs no personal data', which reassures the agent about privacy-sensitive calls. It does not, however, route the agent away from or toward siblings such as explain_electricity_offer or get_signup_link, nor state when-not to use this tool, so it stops short of a 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