Skip to main content
Glama

getecoback-raumklima

pac_n90_ean_abgleichen

Read-only

EAN und Modellangabe des PAC N90 ECO Silent gegen deutsche Unterlagen prüfen — Check the advertised model and GTIN for the documented German PAC N90 ECO Silent.

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": {
      "ean": "<ean>",
      "modell": "<modell>"
    },
    "name": "pac_n90_ean_abgleichen"
  }
}

Input Schema

NameRequiredDescriptionDefault
eanYesAls Zahl geschriebene EAN vom Angebot oder Typenschild.
modellYesZusätzliche Modellbezeichnung.

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 safety and closed-corpus behavior are covered structurally; the description usefully confirms the check runs against German documentation. It does not disclose what a verification yields (match/mismatch, tolerance, discrepancies), which matters because 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.

Conciseness3/5

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

The content is short and front-loaded, but the same sentence is essentially delivered twice, once in German and once in English, without the second version adding information. Defensible for a German-language server, yet redundant by the strict conciseness bar.

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 two required, fully documented parameters and annotations present, the input side is complete. The gap is the result side: no output schema exists and the description never indicates whether the agent receives a boolean, a verdict, or a list of deviations, which an agent needs to plan the call.

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 coverage is 100% with both parameters documented and an enum constraining 'modell' to three values, so the schema carries the semantics. The description only repeats the parameter names and adds no format, range, or interpretation guidance 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?

States a concrete verb (prüfen/check) and concrete resources (EAN and Modellangabe) scoped to one specific appliance, PAC N90 ECO Silent. The device specificity itself separates it from the other *_abgleichen siblings, though it never names an alternative tool outright.

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 narrow device scope: you call it when verifying an offer or nameplate for this particular unit. There is no explicit when-to-use statement, no exclusion (e.g. what to do for a different model), and no mention of prerequisites such as where 'deutsche Unterlagen' come from.

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