Skip to main content
Glama

getecoback-climate-weather

spueler_frontgewicht_inklusive_griff_messband

Read-only

Bestätigten Frontgewichtsbereich mit Front, Griff und allen zusätzlich gesondert gewogenen Teilen vergleichen — Check the documented panel-weight band against the complete panel assembly mass.

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": {
      "front_g": "<front_g>",
      "griff_g": "<griff_g>",
      "weitere_g": "<weitere_g>",
      "untergrenze_g": "<untergrenze_g>",
      "obergrenze_g": "<obergrenze_g>",
      "grenze_und_wiegeumfang_gleich": "<grenze_und_wiegeumfang_gleich>"
    },
    "name": "spueler_frontgewicht_inklusive_griff_messband"
  }
}

Input Schema

NameRequiredDescriptionDefault
front_gYesGewogene Front ohne die getrennt erfassten Teile.
griff_gYesGewogener Griff, soweit nicht bereits enthalten.
weitere_gYesSeparat gewogene zusätzliche Teile, die laut exakter Unterlage zum Frontgewicht zählen.
obergrenze_gYesHersteller-Obergrenze derselben Frontvariante.
untergrenze_gYesVom Hersteller eindeutig dieser Frontvariante zugeordneter kleinster Wert.
grenze_und_wiegeumfang_gleichYesDoppelte Gewichte ausgeschlossen sowie richtige Variante und vollständiger Wiegeumfang bestätigt?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/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 safety is covered. The description adds that this is a comparison against a manufacturer-confirmed band, but it never says what happens when the assembly falls outside the band, nor what the result looks like — a real gap given 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.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The content is short and front-loaded, but it is the same sentence duplicated in German and English without any added information in the second rendering. Nothing is padded beyond that duplication, yet the repetition earns no extra value.

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?

Six required parameters are all described by the schema, and the annotations cover read-only semantics. With no output schema, the description should say what a successful or failing comparison yields; it does not, leaving the agent unable to predict the result shape of this check tool.

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 each of the six parameters is already fully documented in German with bounds. The description only restates the front/handle/extra-parts grouping and adds no meaning about the two boundary values or the boolean confirmation flag, so baseline 3 applies.

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 concrete verb and resource: compare ('vergleichen' / 'check') the confirmed front-weight band against a complete assembly mass built from front, handle and separately weighed parts. An agent can infer it is a validation tool for dishwasher panel weights. However, it does not distinguish itself from the many sibling 'spueler_*' front/weight tools, so 4 rather than 5.

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

Usage Guidelines2/5

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

There is no explicit when-to-use statement, no prerequisites, and no naming of an alternative tool. The only implicit guidance is that a documented upper/lower band must already exist, which the agent derives from the parameter names rather than from the text.

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