Skip to main content
Glama

getecoback-climate-weather

saugwischer_ersatzwalze_artikelabgleich

Read-only

Ersatzwalze anhand genauer Herstellerliste und Teilenummer prüfen — Compare a replacement roller with official model and part documentation.

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": {
      "model_match": "<model_match>",
      "part_match": "<part_match>",
      "region_match": "<region_match>"
    },
    "name": "saugwischer_ersatzwalze_artikelabgleich"
  }
}

Input Schema

NameRequiredDescriptionDefault
part_matchYesStimmt die Teilenummer mit dieser Herstellerliste überein?
model_matchYesNennt die offizielle Liste die vollständige Modellvariante?
region_matchYesIst die konkrete DE/EU-Ausführung dieselbe?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.5/5.0
Behavior2/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 scope are covered structurally; the description is consistent with them (no write or external-lookup claim). Beyond that it adds almost nothing: no statement of the decision or verdict returned, no note that the three inputs are pre-assessed judgments, no indication of failure handling when a value is 'unknown'.

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 front-loaded, but the German sentence and the English sentence are the same content stated twice, so half the text earns no additional information. No structural cues (result, decision, edge cases) are present.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With three required judgement-style parameters and no output schema, the description must explain what the tool returns and how the three verdicts combine into a compatibility result; it does neither. An agent can fill the parameters but cannot predict the outcome of the call, which is a significant gap for this contract shape.

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% and each of the three enum parameters carries its own German question, so the baseline is 3. The description adds no meaning beyond that and slightly works against the schema by implying the tool derives the model/part match rather than receiving it as an input.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a verb (prüfen / compare) and a resource (Ersatzwalze against official model and part documentation), which is clearer than a bare restatement of the name. However, it does not state what the tool actually produces, and it reads as if the tool performs the comparison itself, while the schema shows the caller must supply the match verdicts. Sibling differentiation is absent.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to use this tool, no prerequisites, and no mention of any alternative among the many saugwischer_* siblings. The agent must infer the use case entirely from the name and description.

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