Skip to main content
Glama

getecoback-raumklima

kochtopf_deckelprobe_verdunstung_energie

Read-only

Eigene Deckelproben bei identischer Aufgabe nach Wasserverlust und Strom getrennt beurteilen — Separate evaporation and power differences in matched lidded pot trials.

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": {
      "mit_deckel_wasserverlust_g": "<mit_deckel_wasserverlust_g>",
      "ohne_deckel_wasserverlust_g": "<ohne_deckel_wasserverlust_g>",
      "mit_deckel_wh": "<mit_deckel_wh>",
      "ohne_deckel_wh": "<ohne_deckel_wh>",
      "gleiche_bedingungen": "<gleiche_bedingungen>"
    },
    "name": "kochtopf_deckelprobe_verdunstung_energie"
  }
}

Input Schema

NameRequiredDescriptionDefault
mit_deckel_whYesGemessener elektrischer Energiebedarf mit Deckel.
ohne_deckel_whYesGemessener elektrischer Energiebedarf ohne Deckel.
gleiche_bedingungenYesWasserstartmenge, Topf, Küchenaufgabe und Messgrenze waren vergleichbar.
mit_deckel_wasserverlust_gYesGemessener Wasserverlust mit passendem zugelassenem Deckel.
ohne_deckel_wasserverlust_gYesGemessener Wasserverlust im zulässigen Vergleich ohne Deckel.

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 the safety profile is covered and the bar is lower. Beyond that the description only reveals that the two effect types are judged separately; it says nothing about what is returned or how a failed 'gleiche_bedingungen' check is reflected.

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?

Extremely short and front-loaded, with the two-axis separation stated immediately. The German sentence is simply repeated in English, which is mild redundancy rather than bloat given the total length.

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 five-parameter read-only computation tool with fully documented parameters, the inputs are adequately framed. However, with no output schema present, the description never indicates what the evaluation returns, leaving a real gap for an agent deciding whether to call it.

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 every parameter carries a German description plus numeric bounds, so the schema does the heavy lifting and baseline 3 applies. The description echoes the two measurement axes and the matched-conditions gate but adds no format, unit, or tolerance detail 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?

Names a concrete analysis subject (eigene Deckelproben) and the two axes it separates (Wasserverlust vs. Strom) under a matched-task constraint, so the agent knows this compares paired lidded-pot trials. It stops short of distinguishing itself from sibling measurement tools by name.

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 'bei identischer Aufgabe' implies the prerequisite of comparable trials, which is genuine usage context. There is no explicit when-to-use vs. when-not, no mention of what to do when conditions were not matched, and no alternative tool named.

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