Skip to main content
Glama

getecoback-raumklima

heissluft_teilauslastung_messwert_mehrportion

Read-only

Aus zwei gewogenen Auslastungen den zusätzlichen Strombedarf der zusätzlich erhaltenen gleichartigen Portionen ablesen — Attribute incremental measured electricity to extra servings at a documented load.

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": {
      "kleinstlauf_kwh": "<kleinstlauf_kwh>",
      "groesser_kwh": "<groesser_kwh>",
      "kleine_portionen": "<kleine_portionen>",
      "grosse_portionen": "<grosse_portionen>"
    },
    "name": "heissluft_teilauslastung_messwert_mehrportion"
  }
}

Input Schema

NameRequiredDescriptionDefault
groesser_kwhYesVollständiger Messwert der größeren erlaubten Ausgabe.
kleinstlauf_kwhYesEigener vollständiger Messwert für die kleinere erlaubte Ausgabe.
grosse_portionenYesZahl gleichartiger Portionen aus dem größeren Lauf.
kleine_portionenYesZahl gleichartiger Portionen aus dem kleinen Lauf.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

The read-only nature is already covered by annotations, and the description usefully clarifies that the result is incremental electricity attributable to extra servings. However, it does not state assumptions such as equal portion types, measurement comparability, units, or what exactly is returned. With annotations covering safety, this is adequate but incomplete.

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?

The definition is compact and front-loads the German statement of purpose. The English restatement is somewhat duplicative but still concise enough not to obscure the core meaning.

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 simple four-parameter calculation tool with annotations and fully described schema fields, the definition supplies the essential purpose. It remains incomplete regarding the returned value, units, and any assumptions about comparability between the two measured loads.

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%, so all four parameters are already well documented. The description reinforces the notion of two measured loads and extra portions but adds no additional syntax, constraints, or interpretation beyond the schema.

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 computation: deriving incremental electricity demand for additional equal-sized portions from two measured loads. It is clear enough to distinguish this as an incremental-energy calculation, though it does not explicitly contrast itself with sibling measurement tools.

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?

The description gives no explicit when-to-use guidance, prerequisites, or alternatives. The context of 'two weighed loads' implies the scenario, but an agent is not told when this tool is preferred over related measurement tools.

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