Skip to main content
Glama

getecoback-climate-weather

philips_na35x_backform_rahmenmasse_korbwahl

Read-only

Gemessene Außenkanten einer Rechteckform gegen die dokumentierte NA350/351/352 Korbgrenze prüfen — Match an actual measured rectangular dish to the selected family basket.

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": {
      "geraet": "<geraet>",
      "korb": "<korb>",
      "aussenmasse_belegt": "<aussenmasse_belegt>",
      "seite_a_mm": "<seite_a_mm>",
      "seite_b_mm": "<seite_b_mm>",
      "hoehe_mm": "<hoehe_mm>",
      "gedrehte_lage_belegt": "<gedrehte_lage_belegt>"
    },
    "name": "philips_na35x_backform_rahmenmasse_korbwahl"
  }
}

Input Schema

NameRequiredDescriptionDefault
korbYesBestätigt betrachteter Korb.
geraetYesGenau am Gerät bestätigte Modellfamilie.
hoehe_mmYesGrößte Außenhöhe der Form.
seite_a_mmYesErste Außenkante in eingeplanter Orientierung.
seite_b_mmYesQuer dazu liegende zweite Außenkante.
aussenmasse_belegtYesWurden alle tatsächlichen Außenkanten inklusive Griffen und Höhe derselben Form gemessen?
gedrehte_lage_belegtYesIst eine Drehung um 90 Grad im tatsächlich bestätigten Aufbau anderweitig geometrisch möglich?

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 by structured data. The description adds that this is a comparison/match operation against a documented limit, but it does not say what a negative result looks like, how the 'offen' enum values affect the verdict, or whether it fails versus reports a mismatch.

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 parallel clauses in German and English with no filler, and the core operation is front-loaded. The bilingual duplication costs a little space but aids disambiguation rather than padding.

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?

The input side is fully covered by the schema, but with no output schema the description should indicate what a check yields (pass/fail, slack in mm, or a refusal when dimensions are unconfirmed), and it does not. For a read-only validation tool with seven required inputs, that leaves a meaningful gap for an agent that must interpret the 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%, so every parameter is already documented in the schema, including the enum meanings for korb and geraet and the mm bounds. The description only restates that the edges are measured and the basket is the selected one, adding no syntax or interpretation beyond the schema; 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 pair: it checks measured outer edges of a rectangular dish against the documented NA350/351/352 basket limit, and phrases the outcome as matching a dish to the selected family basket. That distinguishes it reasonably well from the round-form sibling, though it never names a sibling explicitly.

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 only implied: an agent can infer it applies when real measured outer dimensions of a rectangular dish exist and must be compared to a basket limit. There is no explicit when-not guidance, no statement about what to do when measurements are unconfirmed, and no named alternative for round forms or other geometry.

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