Skip to main content
Glama

Verako

Explain an electricity offer

explain_electricity_offer
Read-onlyIdempotent

Explain one electricity contract from a comparison in plain language: what a spot contract is, the markup and fee for the user, the yearly supplier cost at the given usage, the data source and date, and whether we earn a commission.

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_electricity_offer"
  }
}

Input Schema

NameRequiredDescriptionDefault
offer_idYesThe offer_id from a comparison, e.g. 'lyse-energi-as/10215'
postcodeNoNorwegian postcode, used only for VAT
annual_kwhNoYearly use in kWh; 16 000 is about an average home
price_areaNoPrice area NO1-NO5, optional

Output Schema

NameRequiredDescriptionDefault
offerYes
sourcesYes
disclosureYes
explanationYes
disclosure_nbYes
available_in_areasYes

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 readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely non-structured behavior: it discloses that the response includes the data source and its date and whether a commission is earned, which is the kind of trust/provenance context an agent cannot get from annotations. It stops short of stating what happens with an unknown offer_id or whether results are cached.

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?

A single front-loaded sentence with the verb and object first, followed by a compact list of what is explained. The list is dense but each item maps to real output content; only minor tightening would be possible.

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?

An output schema exists, so return values need not be spelled out, yet the description still signals the key outputs, and with 100% schema coverage the parameters are self-documenting. The only real gap is the absence of any routing cue toward or away from explain_rate_offer and compare_electricity_contracts.

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 offer_id, postcode (VAT only), annual_kwh (default 16 000) and price_area are already documented in the schema. The description's phrase 'yearly supplier cost at the given usage' reinforces that annual_kwh drives the calculation, but adds no format or edge-case detail beyond the schema, so the baseline 3 applies.

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?

States a specific verb and resource: 'Explain one electricity contract from a comparison in plain language', and the enumerated payload (spot contract, markup/fee, yearly supplier cost, data source/date, commission) makes the scope concrete. It does not name or contrast with the close sibling explain_rate_offer, so differentiation is left to the agent's inference.

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?

'from a comparison' implies the tool is used downstream of compare_electricity_contracts, but that sibling is never named and no explicit when/when-not is given. Nothing tells the agent to prefer this over explain_rate_offer for a given offer, nor what preconditions exist.

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