Skip to main content
Glama

getecoback-climate-weather

philips_dualkorb_ungeteilte_form_kaltes_musterstueck

Read-only

Ein ungeteiltes langes Musterstück nur auf tatsächlich vorhandene zusammenhängende Korbfläche prüfen — Preserve shape evidence for a one-piece footprint without adding basket areas.

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": {
      "ein_stueck_dokumentiert": "<ein_stueck_dokumentiert>",
      "benoetigte_freie_laenge_mm": "<benoetigte_freie_laenge_mm>",
      "gross_frei_mm": "<gross_frei_mm>",
      "klein_frei_mm": "<klein_frei_mm>",
      "linie_allein_ausreichend": "<linie_allein_ausreichend>"
    },
    "name": "philips_dualkorb_ungeteilte_form_kaltes_musterstueck"
  }
}

Input Schema

NameRequiredDescriptionDefault
gross_frei_mmYesDurchgängige, tatsächlich gemessene freie Länge auf dieser Linie im großen Korb.
klein_frei_mmYesEntsprechende separat gemessene Linie im kleinen Korb.
ein_stueck_dokumentiertYesBezieht sich dieselbe kalte Probe auf ein zusammenhängendes Musterstück, seine geprüfte Orientierung und beide echten Körbe?
linie_allein_ausreichendYesWurden Breite, Höhe, Seitenraum und Zweck zusätzlich unabhängig für die jeweilige Konfiguration bestätigt?
benoetigte_freie_laenge_mmYesGemessene Länge des starren Musters entlang der vorgesehenen belegten Linie.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

readOnlyHint=true and openWorldHint=false already establish that this is a safe, closed-domain read, and the description is consistent with that (prüfen, preserve evidence, do not add areas). It adds one genuine behavioral constraint: the check must not invent basket area. It says nothing about permissions, failure conditions, or what the response represents, which is a real gap given the absence of an 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 definition is short and front-loads the core condition, but it splits into a German sentence and an English sentence that largely restate each other, which is redundant for a bilingual agent. The mixed-language phrasing harms scannability without adding information. Structure is acceptable but not tight.

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 read-only tool with no output schema, the description covers what is being checked and the key constraint about not assuming basket area. It does not explain what a successful result looks like, how the gross and small basket measurements combine, or how this differs from sibling Philips shape checks, which an agent would need in order to call it correctly and interpret it.

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 documented in the schema, which sets the baseline at 3. The description adds only marginal meaning, notably reinforcing that the contiguous basket area must be actually measured rather than assumed, which loosely maps to linie_allein_ausreichend and ein_stueck_dokumentiert. No units, ranges, or interaction between the two basket values are added beyond what the schema states.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the resource (ungeteiltes langes Musterstück) and the action (prüfen auf vorhandene zusammenhängende Korbfläche), so the general purpose is inferable. But 'prüfen' is not a concrete verb with a stated outcome, and no sibling tool is named or contrasted, leaving it ambiguous among the many Philips basket/shape checks. Nothing tells the agent what the check actually returns.

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?

The clause 'nur auf tatsächlich vorhandene zusammenhängende Korbfläche' works as an implicit when-to-use constraint and a when-not-to-act rule (do not assume or add basket areas). However, there is no explicit routing to an alternative sibling tool and no stated prerequisites beyond the parameters themselves. Usage is implied rather than spelled out.

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