Skip to main content
Glama

getecoback-raumklima

steckdosenmessung_mindestdauer

Read-only

Messdauer für einen kleinen, gleichmäßigen Verbraucher aus der Anzeigeauflösung planen. — Estimate how long a steady low-power load needs to register on a plug meter.

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": {
      "last_w": "<last_w>",
      "schritt_kwh": "<schritt_kwh>",
      "ziel_schritte": "<ziel_schritte>"
    },
    "name": "steckdosenmessung_mindestdauer"
  }
}

Input Schema

NameRequiredDescriptionDefault
last_wYesErwartete konstante Wirkleistung in Watt.
schritt_kwhYesKleinste darstellbare Änderung der Energieanzeige in kWh.
ziel_schritteYesZahl der gewünschten Anzeigeschritte.

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?

The annotations already declare readOnlyHint=true and openWorldHint=false, so the agent knows this is a closed, side-effect-free computation. The description adds the modeling assumptions (steady load, display resolution granularity), which is useful beyond the annotations. However, it never says what the result represents or in which unit (seconds, minutes, hours), which is the main thing an agent needs to interpret the output.

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?

It is short and front-loaded, leading with the German statement of the task. The bilingual duplication restates the same sentence in English, which doubles the length without adding information, but the total volume stays small and nothing is buried.

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 three-parameter pure calculator with full schema coverage and read-only annotations, the definition is nearly sufficient. The remaining gap is the return value: with no output schema, the description should say what duration is produced and in what unit, and it does not.

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 the schema already explains all three inputs with bounds. The description only loosely maps concepts: 'Anzeigeauflösung' corresponds to schritt_kwh and 'kleinen, gleichmäßigen Verbraucher' to last_w, but it adds no interpretation of ziel_schritte or of how the three combine. Baseline 3 is appropriate when the schema does the heavy lifting.

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 and object: plan/estimate the measurement duration needed for a small, steady load to register from the meter's display resolution. That is a specific computation, not a restatement of the tool name. It stops short of distinguishing itself from nearby calculation siblings such as geraetetakt_aus_messung or energielabel_messwert_abgleichen.

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?

Usage context is implied rather than stated: 'kleinen, gleichmäßigen Verbraucher' and 'steady low-power load' tell the agent this applies to small constant loads, effectively excluding large or cycling loads. There is no explicit when-not condition, no prerequisite about needing measured display resolution, and no pointer to an alternative tool for non-steady loads.

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