Skip to main content
Glama

SpotVahti

Get electricity contract details

get_contract
Read-onlyIdempotent

Returns the terms (margin or energy price, monthly fee, intro offer, fixed term, restrictions, price check date) and estimated yearly cost of one Finnish electricity contract, found by contract_id or by supplier and product name.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_contract"
  }
}

Input Schema

NameRequiredDescriptionDefault
productNoProduct name, e.g. "Pörssisähkö".
languageNoLanguage for texts and links: fi (Finnish), sv (Swedish) or en (English). Use the user's language.
supplierNoSupplier name, e.g. "Helen" or "Oomi".
home_typeNoTypical Finnish home type; sets the consumption pattern and default yearly kWh (apartment 2000, terraced_house 5000, detached_house 6000, ground_source_heat_pump 10000, direct_electric_heating 18000).
annual_kwhNo
contract_idNocontract_id from a previous result.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, openWorldHint=false), so the description's value is in disclosing the returned content: margin/energy price, monthly fee, intro offer, fixed term, restrictions, price check date, and an estimated yearly cost. Since no output schema exists, this disclosure is the agent's only view of the result shape. It stops short of stating behavior when no contract matches or how the yearly estimate reacts to missing consumption inputs.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence: verb and scope first, then the lookup keys, with the field enumeration carried compactly in one parenthetical. Every clause earns its place because the enumerated fields substitute for the absent output schema.

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?

For a six-parameter, no-required-parameter read tool with no output schema, the definition covers both what comes back and how to address the contract, which is the bulk of what an agent needs. Remaining gaps are the no-match/error case and the interaction between home_type and annual_kwh for cost estimation.

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 83%, so the baseline is 3; the description adds meaning beyond it by presenting supplier and product as a joint alternative key to contract_id, a combination rule the schema does not state. It does not clarify precedence when both contract_id and supplier/product are supplied, nor how home_type versus annual_kwh resolve which consumption drives the estimate.

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?

States a specific verb ("Returns") and resource ("terms ... and estimated yearly cost of one Finnish electricity contract"), enumerating the exact fields returned. The scope word "one" plus the cost estimate clearly separates it from the sibling compare_electricity_contracts, so an agent can choose without opening the schema.

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 tells the agent the two lookup paths (by contract_id, or by supplier + product name), which is genuine invocation guidance. But there is no explicit when-to-use vs when-not framing and no named alternative for the case where the user wants to shop around rather than inspect a known contract; that is left to inference.

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.