Skip to main content
Glama

getecoback-raumklima

strommessung_quellbeleg_export

Read-only

Strommessung als nachvollziehbaren Beleg für Angebote und Vergleiche vorbereiten — Check whether a meter reading records enough context to cite.

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": {
      "geraet_und_modus": "<geraet_und_modus>",
      "dauer": "<dauer>",
      "kwh": "<kwh>",
      "nutzung_typisch": "<nutzung_typisch>",
      "nebenlasten": "<nebenlasten>"
    },
    "name": "strommessung_quellbeleg_export"
  }
}

Input Schema

NameRequiredDescriptionDefault
kwhYesIst die gemessene Energie dokumentiert?
dauerYesSind die Messdauer und die Einheit dokumentiert?
nebenlastenYesIst bekannt, welche weiteren Lasten am Messpunkt hängen?
nutzung_typischYesWurde notiert, ob der Zeitraum typische Nutzung enthält?
geraet_und_modusYesSind Gerät und Betriebsmodus dokumentiert?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/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 safety is covered. The description adds the crucial framing that this is a sufficiency check rather than an export or computation, but it never says what the check produces (pass/fail, missing-item list) and there is no output schema to fill that gap.

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 short sentence front-loads the purpose and ends with the concrete check. The mixed German/English phrasing is slightly awkward but wastes no space and contains no filler.

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?

All five inputs are self-documenting via the schema, but the tool has no output schema and the description does not say what the agent receives back from the sufficiency check, which is the main open question for a validation tool. Adequate to select the tool, thin for interpreting its result.

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% and each of the five booleans is already explained in German, so the description adds no parameter-level meaning. Baseline 3 applies; nothing is lost, but nothing is contributed either.

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 action (prepare/check a power measurement as a citable record for offers and comparisons), which is more specific than the tool name alone and implies a validation role distinct from the strommessung_* calculation siblings. It does not explicitly name any sibling, so differentiation is only implicit.

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 phrase 'für Angebote und Vergleiche' gives an implied usage context (citation in quotes/comparisons), but there is no explicit when-to-use, when-not-to-use, or pointer to the alternative tool for actually computing or comparing readings. The agent must infer timing from the scenario framing.

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