polls.karbach.digital

get_lng_terminals

LNG terminals (GIE ALSI): send-out, tank inventory and utilisation for the EU, each country and every German terminal (Wilhelmshaven, Brunsbüttel, Mukran), versus last year, daily series.

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

Input Schema

Name	Required	Description	Default
`days`	No

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 19, 2026

TDQS

C2.8/5.0

Behavior2/5

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

With no annotations, the description carries the full behavioral burden. It discloses data provenance (GIE ALSI), coverage, and daily granularity, but says nothing about return format, result size, pagination, or how the 'days' window affects output. Operational behavior is essentially undisclosed.

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, front-loaded with the resource and scope, with no filler. The nested parentheticals make it slightly hard to parse but nothing is wasted.

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?

For a tool with no annotations, no output schema, and one undocumented parameter, the description does convey what data is available (metrics, coverage, comparison), which partially substitutes for a missing output schema. However, it leaves the parameter meaning and result characteristics unexplained.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The single parameter 'days' has 0% schema coverage and is never mentioned in the description. 'Daily series' hints at time granularity but does not explain that 'days' sets the lookback window or its default of 90. The description fails to compensate for the schema gap.

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 names a specific resource (LNG terminals via GIE ALSI) and enumerates the metrics returned (send-out, tank inventory, utilisation), scope (EU, country, German terminals), and comparison basis (vs last year). It is clear, but it does not differentiate itself from plausible siblings like get_gas_storage or get_europe_energy_prices.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no mention of alternatives, and no exclusions. The agent gets a content summary but nothing that helps it decide between this tool and get_gas_storage or other energy tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All polls.karbach.digital tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?