Skip to main content
Glama

SpotVahti

Finnish grid transmission fees

get_network_fees
Read-onlyIdempotent

Electricity transmission (siirtohinta) price lists of Finnish distribution network companies, incl. VAT: basic fee per month, transmission price per kWh (general, time-of-day or seasonal), power fees, upcoming price lists and the estimated yearly transmission cost incl. electricity tax per home type. Omit network_company to list all covered companies.

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

Input Schema

NameRequiredDescriptionDefault
languageNoLanguage for texts and links: fi (Finnish), sv (Swedish) or en (English). Use the user's language.
network_companyNoNetwork company name, e.g. "Caruna", "Elenia", "Helen Sähköverkko".

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 declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so safety is covered. The description adds meaningful behavioral context beyond that: prices include VAT, electricity tax is included in yearly cost estimates, and both current and upcoming price lists are returned. It does not discuss auth or rate limits, but those are minor for a read-only lookup.

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 definition is compact: one dense sentence enumerating the fee components followed by a short parameter hint. It is front-loaded with the resource and scope, though the long enumeration makes it slightly list-heavy. Every clause contributes information about what is returned.

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?

With only two optional parameters and no output schema, the description carries the burden of explaining return content and does so thoroughly: fee types, VAT, tax, upcoming lists, and estimated yearly costs. Combined with annotations covering the read-only safety profile, an agent has everything needed to call it correctly.

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 both parameters are already documented. The description still adds value by explaining that omitting network_company returns all covered companies, which is behavioral meaning not present in the schema's brief name example. The language parameter is left to the schema, which is acceptable given full coverage.

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 resource (Finnish distribution network transmission price lists) and enumerates its components: monthly basic fee, per-kWh transmission price by tariff type, power fees, upcoming lists, and estimated yearly cost. This clearly distinguishes it from sibling tools dealing with supply contracts, spot prices, and suppliers.

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?

The only explicit usage guidance is 'Omit network_company to list all covered companies,' which explains a parameter behavior rather than when to choose this tool over siblings like get_contract or compare_electricity_contracts. The tool's purpose implies its use case, but no when-not or alternative routing is stated.

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.