Skip to main content
Glama

getecoback-climate-weather

philips_backform_erst_seitenfreiraum_belegen

Read-only

Bei einer bereits geometrisch geprüften Form die tatsächlich sichtbaren Seiten getrennt vermerken — Verify that an apparent fit leaves observable space on all four sides.

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": {
      "modell_und_form_bestaetigt": "<modell_und_form_bestaetigt>",
      "vorn": "<vorn>",
      "hinten": "<hinten>",
      "links": "<links>",
      "rechts": "<rechts>"
    },
    "name": "philips_backform_erst_seitenfreiraum_belegen"
  }
}

Input Schema

NameRequiredDescriptionDefault
vornYesPlatz vor der Form am ganzen relevanten Rand sichtbar.
linksYesEntsprechender Platz links.
hintenYesEntsprechender Platz hinter der Form.
rechtsYesEntsprechender Platz rechts.
modell_und_form_bestaetigtYesSind der genaue Korb, seine Formreferenz und dieselbe kalte Aufstellung bekannt?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/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 word 'vermerken' reads as note-taking rather than a real mutation in this evidence-recording tool family, so it is not treated as a contradiction. The description adds useful behavior context: the evidence must be 'tatsächlich sichtbar' (actually observable) and each side is recorded separately, implying a per-side judgement rather than an overall pass. It does not say what the tool returns or how conflicting side states are handled.

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 the precondition is front-loaded, which is good. But it is split across a German clause and an English clause that partly restate the same idea while using different verbs (record vs. verify), so the two halves do not fully earn their combined length.

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-parameter read-only attestation tool with no output schema, the description covers the precondition and the object of the check, which is adequate. It is incomplete on what a successful result looks like (whether a single confirmation or a per-side record is produced) and on how the required boolean 'modell_und_form_bestaetigt' gate behaves if false.

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%, with all five parameters documented including four three-valued enums, so the schema carries most of the semantic load and a baseline of 3 applies. The description adds marginal meaning by emphasizing that the sides are to be noted separately and that the space must be observable, which reinforces the intent of the enum values but does not explain them further.

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 action and object: recording ('vermerken') the actually visible side clearance per side on an already geometrically checked form. The second clause ('Verify that an apparent fit leaves observable space on all four sides') sharpens the intent but also shifts the verb from recording to verifying, leaving a mild ambiguity about whether the tool attests or inspects. Still, an agent can tell this apart from the many sibling 'beleg' tools because the resource (four-sided clearance on a pre-checked form) is explicit.

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?

A real precondition is stated: only apply 'bei einer bereits geometrisch geprüften Form', which tells the agent this comes after a geometry check rather than replacing it. However, no sibling alternative is named and no when-not-to-use condition is given, so the routing guidance is implied rather than explicit. Given the large sibling family of similarly named 'belegen' tools, more differentiation would have helped.

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