Skip to main content
Glama

getecoback-climate-weather

steckdosenmessgeraet_einsatzgrenze

Read-only

Vor einer Steckdosenmessung prüfen, ob eine bestätigte Gerätegrenze zur beobachteten Last passt. — Check documented plug-meter capacity and load-type approval before measuring.

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>",
      "limit_w": "<limit_w>",
      "lastart_freigabe": "<lastart_freigabe>"
    },
    "name": "steckdosenmessgeraet_einsatzgrenze"
  }
}

Input Schema

NameRequiredDescriptionDefault
last_wYesHöchste dokumentierte normale Wirkleistung des Geräts in W.
limit_wYesVom Messgerätehersteller für die Lastart erlaubte Wirkleistung in W.
lastart_freigabeYesMessgeräteanleitung bestätigt diese Lastart samt Einsatzbedingungen und Einschaltlast.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/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 agent knows this is a safe, local check. The description adds that a *confirmed* device limit is required before measuring, which is useful workflow context, but it says nothing about what the verdict looks like or what the agent should do when the check fails.

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?

Two short, front-loaded sentences with the trigger condition first and the purpose second. The German/English duplication is slightly redundant but aids clarity rather than adding noise.

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 read-only, closed-world check with fully documented parameters, the definition covers inputs and timing adequately. However, with no output schema, the agent is left guessing what the tool returns (a boolean verdict, a threshold comparison, a recommendation) and how to act on a negative 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 parameter has bounds and a precise definition, so the schema does the heavy lifting. The description frames the three inputs as a comparison between documented device limit and observed load, which adds conceptual value, but no format or edge-case guidance 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 verb and resource: check ('prüfen') a documented plug-meter ('Steckdosenmessgerät') capacity/load-type limit against the observed load. It is unambiguous what the tool evaluates, though it does not explicitly distinguish itself from the many sibling tools by naming an alternative.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives a clear temporal trigger — 'Vor einer Steckdosenmessung' / 'before measuring' — which tells the agent exactly when this pre-check applies. It does not state when-not to use it or name an alternative tool, so it falls short of a 5.

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