Skip to main content
Glama

getecoback-climate-weather

philips_na352_kit_einsatzzweck_statt_shoptitel

Read-only

Ein vorhandenes oder angebotenes Philips Kit nach seiner dokumentierten Aufgabe statt nach dem Shop-Sammelbegriff auswählen — Distinguish HD9945/01 bakeware and HD9920/00 rack-and-skewer evidence.

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": {
      "na352_00_belegt": "<na352_00_belegt>",
      "tatsaechlicher_artikel": "<tatsaechlicher_artikel>",
      "gewuenschter_zweck": "<gewuenschter_zweck>",
      "passendes_bereits_vorhanden": "<passendes_bereits_vorhanden>"
    },
    "name": "philips_na352_kit_einsatzzweck_statt_shoptitel"
  }
}

Input Schema

NameRequiredDescriptionDefault
na352_00_belegtYesIst das deutsche NA352/00 am eigenen Gerät genau identifiziert?
gewuenschter_zweckYesEigener beabsichtigter Zubehörzweck.
tatsaechlicher_artikelYesEindeutig abgelesenes Originalteil-Set.
passendes_bereits_vorhandenYesIst passendes Zubehör für diesen Zweck bereits unabhängig bestätigt und vorhanden?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/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 and scope profile is covered. The description adds that the decision must rest on documented evidence rather than marketing naming, but it never says what the call actually produces (a verdict, a matched article, a rejection) — notable given there is no 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two compact clauses with the core principle (purpose over shop title) front-loaded and the concrete discriminators appended. The German/English mix is slightly awkward but costs no extra 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?

With four required parameters, two enums, and no output schema, the description should say what the result looks like and how conflicting evidence is resolved. It supplies the discriminating rule but leaves the outcome and the role of the two boolean prerequisites to the schema, so it is adequate rather than complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description genuinely adds meaning by mapping the opaque enum values to real articles: hd9945_01 equals bakeware, hd9920_00 equals rack-and-skewer. It does not interpret the two boolean gates (na352_00_belegt, passendes_bereits_vorhanden), which the schema carries alone.

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 specific discriminating operation: pick a Philips kit by documented purpose rather than by the shop's collective term, and it names the two concrete article variants (HD9945/01 bakeware, HD9920/00 rack-and-skewer) that the classification hinges on. It is clearly not the sync/status siblings, but the exact operation type (a decision/verdict vs. a lookup) is only implied.

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 implied by the framing 'statt dem Shop-Sammelbegriff' — use it when a shop title is ambiguous and the actual task must drive the selection. There is no explicit when-not guidance and no sibling is named as the alternative for the adjacent cases (e.g., the other philips_hd9945/philips_na35x evidence 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