Skip to main content
Glama

getecoback-raumklima

saugroboter_buerste_geraeusch

Read-only

Ungewohntes Bürstengeräusch am vorhandenen Roboter sicher eingrenzen — Triage a new brush sound without running an unsafe or partly assembled robot.

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": {
      "symptom": "<symptom>",
      "visible_entanglement": "<visible_entanglement>",
      "after_care": "<after_care>"
    },
    "name": "saugroboter_buerste_geraeusch"
  }
}

Input Schema

NameRequiredDescriptionDefault
symptomYesBeobachtung aus einem normalen Lauf.
after_careYesModellgerechte Pflege bereits durchgeführt und beide Teile korrekt eingesetzt?
visible_entanglementYesHaare oder Schnur am von außen zugänglichen Bürstenbereich sichtbar?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/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 safe-read profile is covered structurally. The description adds genuine context beyond that: the tool is a pure triage step that must not require operating the robot in an unsafe or partially assembled state. It stops short of saying what the output/recommendation looks like or whether it bounds the triage to a single brushing area.

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?

One front-loaded sentence stating purpose and the key safety restriction, with no filler. The German/English duplication adds a few redundant words but also serves clarity for a bilingual catalogue.

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

Completeness4/5

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

For a small three-parameter triage tool with full schema coverage, no output schema and read-only annotations, the definition supplies enough to call it correctly and to know not to run the robot. A slightly fuller statement of the decision outcomes would push it higher, but nothing essential is absent.

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 required fields carries its own description plus an enum for the symptom, so the schema does the heavy lifting. The description adds no semantics beyond that (e.g. how 'unclear' is handled or what after_care=true unlocks), which is the expected baseline-3 case.

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?

Names a concrete verb+resource pair: triaging an unusual brush sound ("Ungewohntes Bürstengeräusch ... sicher eingrenzen"). The scope ('am vorhandenen Roboter') and safety framing differentiate it from the diagnostic siblings such as sensor-care or carpet-mode tools, though it does not name a specific alternative. It is specific enough to select without opening the schema.

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

Usage Guidelines4/5

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

Implicitly states the trigger condition (a new/unfamiliar brush noise) and adds a clear constraint: do not run the robot when it is unsafe or partly assembled. What is missing is an explicit 'if X instead, use sibling Y' routing or a statement of what to do when the symptom is electrical/stopped.

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