Skip to main content
Glama

getecoback-raumklima

philips_perfectcare_trageverriegelung_exemplarbeleg

Read-only

Die Trageverriegelung der PSG7140/70 vom tatsächlich beobachteten Zustand am eigenen Exemplar unterscheiden — Separate the stated carry lock feature from an observed lock state.

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": {
      "psg7140_70_belegt": "<psg7140_70_belegt>",
      "einrasten": "<einrasten>",
      "nur_verkaeuferangabe": "<nur_verkaeuferangabe>"
    },
    "name": "philips_perfectcare_trageverriegelung_exemplarbeleg"
  }
}

Input Schema

NameRequiredDescriptionDefault
einrastenYesIst der Zustand des eigenen Verschlusses eindeutig beobachtet?
psg7140_70_belegtYesIst genau PSG7140/70 am Exemplar bestätigt?
nur_verkaeuferangabeYesBeruht der Zustand ausschließlich auf der Aussage des Verkäufers?

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 establish that this is a read-only, closed-world operation, and the description adds the useful context that it concerns the difference between a seller claim and an observed state. However, it does not explain the result, how 'offen' should be interpreted, or what happens when observations conflict.

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?

The definition is a single front-loaded sentence with no filler, and the bilingual phrasing is efficient for a domain-specific tool. Its brevity is appropriate for conciseness, though the German and English clauses essentially restate the same point.

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 schema and annotations cover the parameters and safety profile, but with no output schema the description should do more to explain what the tool returns or how the evidence classification is represented. For a niche evidence-recording tool, the definition is minimally adequate but leaves the result semantics implicit.

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 three required parameters are already documented in the input schema, including the enum values for 'einrasten'. The description reinforces the stated-versus-observed distinction but adds no parameter-specific syntax or interpretation beyond the schema.

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 resource, model (PSG7140/70 carry lock), and scope: separating a stated feature from an observed lock state on the user's own exemplar. It is clear enough to identify the tool's domain, but it does not differentiate it from the many similarly named sibling evidence tools.

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 through the stated versus observed distinction and the 'eigenes Exemplar' scope. There is no explicit when-to-use guidance, no exclusions, and no named alternative among the sibling tools.

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