Skip to main content
Glama

Gexiro DACH Pulse & Alexa Voice Suite MCP

get_heating_oil_and_pellet_price

Get live German/Austrian heating oil (Heizöl EL per 100L) and ENplus A1 wood pellet prices (€/t) with Brent Crude 7-day buy/wait recommendation.

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

Input Schema

NameRequiredDescriptionDefault
litersNoOrder volume in liters (default 2000)
bundeslandNoGerman state name (e.g. Bayern, Nordrhein-Westfalen)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the whole burden; it does disclose useful behavior — live data, German/Austrian scope, quoting units, and that a buy/wait recommendation is derived from Brent Crude's 7-day trend. It does not say how the recommendation is computed, how often data refreshes, or whether the recommendation depends on the order volume.

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 dense sentence with the core resource and value proposition front-loaded and zero filler. The parenthetical unit/product qualifiers are compact and functional, though the packed phrasing takes a moment to parse.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, and the description names the returned measures (€/100L, €/t, Brent-based buy/wait) but not their shape or how optional inputs alter the response. For a two-optional-parameter read tool this is adequate but leaves gaps about the recommendation logic and Austrian vs. German handling.

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 both parameters (liters, bundesland) are already documented in structured form; the description adds no parameter-level detail. It gestures at volume pricing via 'per 100L' but never explains how liters changes the result or how Austrian coverage interacts with a German state parameter.

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 (Get) and two concrete resources with units and product grades — heating oil (Heizöl EL per 100L) and ENplus A1 wood pellets (€/t) — plus a Brent-Crude-derived 7-day buy/wait recommendation. This is clearly distinguishable from siblings like get_fuel_station_prices_de or get_epex_electricity_price.

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 intended use (checking live fuel/pellet prices plus a buy/wait signal) is implied by the wording, but there is no explicit statement of when to prefer this over price-adjacent siblings such as get_fuel_station_prices_de, and no exclusions or prerequisites are given.

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