Skip to main content
Glama

finwire.pl - Polish financial data

Regulated electricity and gas prices

get_energy_prices
Read-onlyIdempotent

Use for regulated electricity and gas tariffs in Poland. For prices in the EU, use get_europe_data. Household electricity and gas tariffs approved by URE and in force today: electricity energy price of the default seller and distribution rates per operator for G11, G12 and G12w with cheaper-zone hours and fees; gas fuel price, subscription and PSG distribution rates per tariff area for W-1.1 to W-4. Net amounts, VAT rate given; each with the URE decision and PDF.

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

Input Schema

NameRequiredDescriptionDefault
areaNoFilter by distribution operator or gas tariff area, e.g. "Tauron", "Stoen", "warszawski".
dateNoDay YYYY-MM-DD for which tariffs in force are selected; default today.
carrierNoOmit for both.

Output Schema

NameRequiredDescriptionDefault
urlYes
asOfNo
dataNo
titleYes
sourceYes
docsUrlYes
licenseYes
summaryYes
citationYes
datasetIdYes
sourceUrlNo
truncatedNo
serverDateYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, closed-world, non-destructive behavior, so the safety profile needs no restating. The description adds genuinely useful context beyond them: values are net amounts, the VAT rate is supplied, and each record carries the URE decision reference and a PDF. It does not discuss response size, pagination, or freshness beyond "in force today", which keeps it short of a 5.

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 usage statement and the sibling routing are front-loaded in the first two sentences, before the data-content detail. The third sentence is long and list-heavy but every clause (zones, fees, VAT, URE decision, PDF) conveys distinct scope information, so little is wasted.

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?

An output schema exists and annotations cover the safety profile, so the description only needs to establish domain, scope, and result substance, all of which it does. An agent knows the country, the carriers, the tariff codes, the tax treatment, and the accompanying documents before calling it.

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 parameter mechanics are already documented; the description still adds meaning by clarifying that "area" maps to a distribution operator or gas tariff area and that selection is by the tariff "in force today", which explains the date default. The G11/G12/G12w and W-1.1 to W-4 enumerations give the agent concrete vocabulary for the area and carrier filters rather than bare field names.

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-and-resource pair: regulated electricity and gas tariffs in Poland, and enumerates exactly which figures are covered (default-seller energy price, distribution rates for G11/G12/G12w, gas fuel price, subscription, PSG distribution for W-1.1 to W-4). This is clearly distinguishable from sibling price tools such as get_fuel_prices or get_europe_data.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Opens with explicit when-to-use ("Use for regulated electricity and gas tariffs in Poland") and routes the agent to the correct alternative for non-Polish/EU pricing ("For prices in the EU, use get_europe_data"). The scope boundary is stated directly rather than 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.