Skip to main content
Glama

getecoback-raumklima

oskar_zubehoer_beigabe_anleitungsversion

Read-only

Trenne beim Oskar little die Hygiene-Beigabe in Angebot, Produktseite und EU-Anleitung — Separate Oskar little hygiene accessory listings across documents

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": {
      "typenschild_o060": "<typenschild_o060>",
      "lieferbeigabe": "<lieferbeigabe>",
      "pflegebeleg": "<pflegebeleg>"
    },
    "name": "oskar_zubehoer_beigabe_anleitungsversion"
  }
}

Input Schema

NameRequiredDescriptionDefault
pflegebelegYesWas die zur angebotenen Ausführung mitgelieferte Anleitung nennt
lieferbeigabeYesWas im konkreten Angebot ausdrücklich enthalten ist
typenschild_o060YesWeißes Gerät anhand der Kennung O-060 identifiziert

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 the safety profile is known without the description. Beyond that, the description adds nothing: it does not say what is returned, whether the three documents are compared pairwise, or how conflicts between them are reported. For a read-only analysis tool this leaves real behavioral questions open.

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 description is short and front-loads the resource, which is good, but roughly half its length is a bilingual restatement that adds no new information. The dash-separated English clause is pure duplication rather than elaboration.

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?

Three required parameters, two constrained enums, and no output schema mean the description should explain what the agent gets back and how document conflicts are represented. It does neither, and it does not clarify the role of typenschild_o060 in the separation logic, so an agent cannot predict the result.

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 the two enum parameters (pflegebeleg, lieferbeigabe) already spell out their meanings; the boolean typenschild_o060 is also documented. The description names the three artifacts loosely but adds no mapping between them and the parameters, so it neither helps nor hurts relative to the schema baseline.

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 verb 'Trenne' (separate/disambiguate) plus the object 'Hygiene-Beigabe' and the three target artifacts (Angebot, Produktseite, EU-Anleitung) give a partial picture, but the exact operation remains fuzzy: it is unclear whether the tool splits, reconciles, or merely distinguishes the accessory data. The English half only paraphrases the German, so neither version resolves the ambiguity.

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?

No guidance is given about when to call this tool, what preconditions must hold, or which sibling to use instead (e.g. the document-version or Beleg-related tools). The mention of 'Angebot' implies a context but stops short of stating when the tool should or should not be used.

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