Skip to main content
Glama

getecoback-raumklima

haushaltswaage_nullpunkt_driftspanne

Read-only

Gewichtsmessung mit Nullanzeige vor und nach dem Wiegen samt Restunsicherheit einordnen — Bound tare drift using verified zero readings at both ends.

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": {
      "anzeige_g": "<anzeige_g>",
      "null_vor_g": "<null_vor_g>",
      "null_nach_g": "<null_nach_g>",
      "restspielraum_g": "<restspielraum_g>",
      "zwischenwerte_begrenzt": "<zwischenwerte_begrenzt>"
    },
    "name": "haushaltswaage_nullpunkt_driftspanne"
  }
}

Input Schema

NameRequiredDescriptionDefault
anzeige_gYesAngezeigte Bruttomasse in Gramm.
null_vor_gYesAnzeige der leeren Wiegefläche vor dem Versuch, Gramm.
null_nach_gYesAnzeige der leeren Wiegefläche nach dem Versuch, Gramm.
restspielraum_gYesZusätzlicher begründeter absoluter Spielraum in Gramm, ohne erneut eingerechnete Nullpunktdrift.
zwischenwerte_begrenztYesDarf der Nullpunkt im betrachteten Fenster auf den Bereich der beiden Kontrollwerte begrenzt werden?

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. The description adds genuine behavioral context beyond that: the computation is bounded by control readings at both ends, and restspielraum is explicitly not re-including zero drift. However it never says what the result looks like (a single span in grams, a verdict, both), and with no output schema that omission matters.

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?

A single compact sentence with the operative idea front-loaded, followed by a short English restatement. The bilingual duplication is mildly redundant but the whole definition is short and wastes little space.

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-required-parameter computation with no output schema, the description should at minimum indicate what is returned (a drift span in grams, a bound, or a pass/fail assessment). It establishes inputs and intent but leaves the return value entirely to inference, which is the main completeness gap.

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 already carry definitions and ranges; baseline is 3. The description reinforces the roles of the two zero readings and the residual-uncertainty term, but adds nothing about the semantics of zwischenwerte_begrenzt (whether clamping to the control-value interval is permissible) beyond what the schema already says.

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 specific operation on a specific object: bounding tare (zero-point) drift for a weighing using zero readings taken before and after the weighing, plus residual uncertainty. That is far more than the compound name alone conveys. It does not differentiate itself from any of the many sibling weighing/measurement tools, which keeps it out of 5 territory.

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 is implied rather than stated: the phrase 'using verified zero readings at both ends' tells the agent this applies only when control readings exist before and after a weighing. There is no explicit when-not guidance, no mention of an alternative tool for single-reading or drift-free cases, and no prerequisites such as calibration state.

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