Skip to main content
Glama

getecoback-raumklima

strommessung_a_b_messfehler

Read-only

Zwei Messläufe derselben Aufgabe unter Berücksichtigung der Fehlergrenzen vergleichen. — Check whether a measured mode change exceeds the stated measurement uncertainty.

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": {
      "a_kwh": "<a_kwh>",
      "b_kwh": "<b_kwh>",
      "fehler_a_kwh": "<fehler_a_kwh>",
      "fehler_b_kwh": "<fehler_b_kwh>",
      "aufgabe_identisch": "<aufgabe_identisch>"
    },
    "name": "strommessung_a_b_messfehler"
  }
}

Input Schema

NameRequiredDescriptionDefault
a_kwhYesGemessene kWh des ersten Laufs.
b_kwhYesGemessene kWh des zweiten Laufs.
fehler_a_kwhYesAbsolute Fehlergrenze für die erste Messung in kWh.
fehler_b_kwhYesAbsolute Fehlergrenze für die zweite Messung in kWh.
aufgabe_identischYesWurde dieselbe Aufgabe bis zum gleichen Ergebnis unter vergleichbaren Bedingungen erledigt?

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 establish that this is a read-only, closed-world operation, and the description adds that the comparison accounts for stated measurement uncertainty. However, it does not explain how the comparison is performed or what the returned check result looks like, which matters because there is no output schema.

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 description is short and front-loaded, stating the comparison and the uncertainty check immediately. The German and English sentences largely duplicate each other, but the structure remains efficient.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given five fully documented required parameters, read-only annotations, and no output schema, the description provides enough context to invoke the tool correctly. A minor gap is that it does not say what happens when aufgabe_identisch is false or describe the result format.

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 five parameters are already well documented in the input schema. The description reinforces the error-limit concept but adds no extra parameter-level meaning beyond what the schema provides.

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 operation: comparing two measurement runs while accounting for error limits, and checking whether a measured change exceeds uncertainty. It is clear what the tool does, but it does not explicitly differentiate itself from sibling tools such as strommessung_hochrechnen.

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?

The description gives clear usage context: compare two runs of the same task under error limits to determine whether a measured change is significant. It does not state when not to use the tool or name explicit alternatives.

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