Skip to main content
Glama

getecoback-climate-weather

strompreis_zeitreihe_vollstaendigkeit_beleg

Read-only

Für eine veröffentlichte Statistik über Börsenpreisstunden die fehlenden Werte getrennt ausweisen — Report observed coverage before quoting a negative-price share.

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": {
      "erwartete_stunden": "<erwartete_stunden>",
      "vorhandene_stunden": "<vorhandene_stunden>",
      "negative_stunden": "<negative_stunden>"
    },
    "name": "strompreis_zeitreihe_vollstaendigkeit_beleg"
  }
}

Input Schema

NameRequiredDescriptionDefault
negative_stundenYesZahl negativer Preise unter den vorhandenen Stundenwerten.
erwartete_stundenYesZahl erwarteter Stundenwerte im definierten Bezugszeitraum inklusive Zeitumstellung.
vorhandene_stundenYesZahl tatsächlich vorliegender, eindeutiger Stundenwerte.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds a real behavioral point beyond that: missing values are reported separately rather than silently folded in, which tells the agent the tool is conservative about coverage. It says nothing about what happens on inconsistent inputs (e.g. present hours exceeding expected) or what the response contains.

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?

A single front-loaded sentence stating the purpose followed by an em-dash clause stating the usage trigger. Nothing is redundant and the operational instruction is placed where an agent will read it first.

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?

With three fully documented numeric parameters and read-only annotations, the definition is callable as written. However, there is no output schema, and the description never indicates what is returned (coverage ratio, missing count, a verdict), leaving the agent to infer the result shape for a tool whose entire value is its computed output.

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 coverage is 100%: all three parameters carry German descriptions explaining expected hours (including DST), actually present unique hour values, and negative-price count. The description adds no format or constraint detail beyond the schema, so the baseline 3 applies — the schema does the work here.

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 concrete operation on a concrete resource: report observed coverage (missing values separately) for a published statistic over exchange-price hours. That is a specific verb-plus-resource, and 'beleg'/'Vollstaendigkeit' in the name is backed by real content rather than restated. It stops short of differentiating itself from any sibling tool, so it lands at 4 rather than 5.

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?

It gives one clear trigger — call this before quoting a negative-price share — which is genuine when-to-use guidance. It offers no when-not-to-use condition, no prerequisites, and no named alternative for related checks, so the guidance is implied rather than complete.

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