Skip to main content
Glama

getecoback-raumklima

philips_backset_gebrauchsspuren_originalform_vergleichen

Read-only

Einen gebrauchten Formkörper und überstehende Griffe technisch getrennt als Sichtbefund einordnen — Check whether observed rim changes invalidate an older exterior measurement.

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": {
      "messungen_am_gleichen_teil": "<messungen_am_gleichen_teil>",
      "alter_rahmen_mm": "<alter_rahmen_mm>",
      "neuer_rahmen_mm": "<neuer_rahmen_mm>",
      "messspanne_mm": "<messspanne_mm>",
      "rand_auffaellig": "<rand_auffaellig>"
    },
    "name": "philips_backset_gebrauchsspuren_originalform_vergleichen"
  }
}

Input Schema

NameRequiredDescriptionDefault
messspanne_mmYesKombinierte Unsicherheit dieser Breiten.
alter_rahmen_mmYesÄltere größte gemessene Außenbreite einschließlich Griffen.
neuer_rahmen_mmYesAktuell beobachtete größte Außenbreite einschließlich Griffen.
rand_auffaelligYesIst am Rand oder Griffbereich eine tatsächliche äußerliche Auffälligkeit dokumentiert?
messungen_am_gleichen_teilYesSind ältere Außenmessung und heutige kalte Beobachtung sicher genau derselben Form zugeordnet?

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?

The readOnlyHint=true and openWorldHint=false annotations already establish that this is a safe, closed-world read operation, and the description is consistent with that by framing the tool as a visual check. It does not disclose how the check is decided, what result is returned, or any thresholds, so it adds only modest behavioral context.

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?

It is a single sentence and not padded, but the structure is weakened by switching between German and English and by leading with an abstract classification clause before the concrete check. The core action is not front-loaded.

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?

With five required parameters fully documented and read-only annotations, the description covers the broad purpose. However, it never states what the tool returns or how the invalidation judgment is expressed, which matters because there is no output schema.

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?

All five parameters are already described at 100% schema coverage, including the distinction between old/new frame widths and the uncertainty span. The description does not add syntax, units, or interpretation rules beyond the schema, so the baseline of 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 English clause states a concrete check: whether observed rim changes invalidate an older exterior measurement, giving a specific verb and resource. However, the opening German clause is abstract ('technisch getrennt als Sichtbefund einordnen') and the description does not distinguish this from sibling comparison tools, so it falls short of a 5.

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 description implies the use case of validating an older exterior measurement against current rim observations, but it gives no explicit when-to-use, when-not-to-use, or alternative-tool guidance. The implied context is enough for a 3, not for a 4.

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