Skip to main content
Glama

German gas storage fill level (GIE AGSI+)

get_gas_storage
Read-only

Free. Fill level of German gas storage from GIE AGSI+ (EU transparency data): percent full, TWh in storage, injection and withdrawal per day, trend as published and a 30-day series. Not a supply forecast and not a statement about security of supply. Returns not_configured or unavailable instead of estimating when the source cannot be read.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the readOnlyHint/openWorldHint annotations, the description discloses cost ('Free'), data provenance (GIE AGSI+), and — most usefully — the failure contract: it returns not_configured or unavailable rather than estimating when the source cannot be read. That is exactly the degradation behavior an agent needs to plan around, and it does not contradict the annotations.

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?

Three tight sentences with the core purpose front-loaded, followed by scope exclusions and then the failure behavior. Fragments like 'Free.' and the field list carry information rather than filler, and nothing is repeated.

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 no input parameters and no output schema, the description carries the return-value burden itself and does so by naming the metrics and the 30-day series. Combined with the explicit unavailable/not_configured path, an agent knows what a successful and a failed call both look like.

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?

The tool takes zero parameters (additionalProperties: false), so there is nothing to disambiguate and the baseline is 4. The description correctly implies a fixed, no-argument call and adds no misleading parameter talk.

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 — fill level of German gas storage from GIE AGSI+ — and enumerates the exact quantities returned (percent full, TWh, injection/withdrawal per day, 30-day series). It also delimits scope with 'not a supply forecast and not a statement about security of supply', so an agent cannot mistake it for an outlook or risk indicator.

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

Usage Guidelines4/5

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

The description supplies clear context for use: it is free, sourced from EU transparency data, and explicitly not a forecast or security-of-supply statement, which tells the agent when not to rely on it. It stops short of naming an alternative tool for supply outlooks, but no sibling in the catalog covers that need.

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.