Skip to main content
Glama

getecoback-raumklima

kontaktgrill_programmstrom_leerlauf_ohne_ausgabe

Read-only

Bei einer vollständigen Nutzung unproduktive gemessene Warteaufnahme als eigene Stromposition ausweisen — Report measured grill waiting energy without assuming it is avoidable.

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": {
      "komplett_wh": "<komplett_wh>",
      "warten_leerlauf_wh": "<warten_leerlauf_wh>",
      "ausgegebene_portionen": "<ausgegebene_portionen>",
      "protokoll_vollstaendig": "<protokoll_vollstaendig>"
    },
    "name": "kontaktgrill_programmstrom_leerlauf_ohne_ausgabe"
  }
}

Input Schema

NameRequiredDescriptionDefault
komplett_whYesMesswert der ganzen Sitzung in Wh.
warten_leerlauf_whYesIm Gesamtwert enthaltene und als tatsächliches Warten protokollierte Wh.
ausgegebene_portionenYesZahl der tatsächlich gleichartigen ausgegebenen Portionen.
protokoll_vollstaendigYesSind Messanfang, Messende und Warteabschnitt eindeutig dokumentiert?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/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 the useful interpretive point that waiting energy is reported separately and should not be assumed avoidable, but it does not explain validation behavior when protokoll_vollstaendig is false or what the result contains.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is short, but it is bilingual and repeats the same idea in German and English, producing avoidable redundancy. The core idea is front-loaded enough to be usable.

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 four-parameter read-only calculation/reporting tool with full schema coverage, the description is minimally adequate. It does not explain return behavior, conditional handling of an incomplete protocol, or how portions affect the reported 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 coverage is 100%, so all four parameters are already documented in the schema. The description adds no parameter-specific meaning or constraints beyond that, making the baseline 3 appropriate.

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 states a specific action: reporting measured grill waiting energy as its own electricity line item, without assuming it is avoidable. It is clear enough to identify the resource and output concept, though it does not explicitly differentiate itself from siblings.

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 prerequisites, and no named alternatives. The phrase about not assuming avoidability is a conceptual stance, not usage guidance for an agent.

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