Skip to main content
Glama

SpotVahti

List an electricity supplier's contracts

get_supplier
Read-onlyIdempotent

Lists all contracts of a Finnish electricity supplier in the SpotVahti comparison, with terms and price check dates. An unknown name returns the list of known suppliers.

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": {
      "supplier": "<supplier>"
    },
    "name": "get_supplier"
  }
}

Input Schema

NameRequiredDescriptionDefault
languageNoLanguage for texts and links: fi (Finnish), sv (Swedish) or en (English). Use the user's language.
supplierYesSupplier name, e.g. "Fortum".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/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, destructiveHint=false, closed-world), so the bar is lower. The description still adds real behavior beyond them: the shape of the payload (terms and price check dates) and the non-obvious fallback that an unknown supplier name yields the list of known suppliers, which prevents an agent from treating a miss as an error.

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?

Two sentences, both load-bearing: the first defines scope and payload, the second handles the edge case. It is front-loaded with the core purpose and contains no filler.

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?

With no output schema, the description carries the burden of describing return values, and it does so at a high level (contracts with terms and price check dates). For a two-parameter read-only lookup this is nearly sufficient; only pagination or result-volume hints are missing, which is minor.

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%, with both parameters documented and the enum spelled out including 'Use the user's language.' The description adds no further meaning about the supplier parameter beyond what the schema example ('Fortum') and required flag already convey, so this sits at the baseline.

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?

The description gives a specific verb and resource ('Lists all contracts of a Finnish electricity supplier') plus the domain context (SpotVahti comparison) and what each entry carries (terms, price check dates). It is clear what the tool does, but it never names how it differs from the singular get_contract sibling, so the agent must infer the distinction from the name alone.

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?

There is no explicit statement of when to use this versus compare_electricity_contracts or get_contract, and no prerequisites are stated. The one genuinely useful usage signal is the fallback hint that an unknown name returns the known suppliers, which effectively tells the agent how to use the tool for supplier discovery.

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.