Skip to main content
Glama

getecoback-climate-weather

tineco_saugwischer_pflegecheck

Read-only

Modell und Symptom zum belegten Tineco-Pflegeschritt führen — Find the documented care or escalation step for a Tineco symptom.

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": "<model>",
      "symptom": "<symptom>",
      "care": "<care>"
    },
    "name": "tineco_saugwischer_pflegecheck"
  }
}

Input Schema

NameRequiredDescriptionDefault
careYesAnleitungsgemäße Pflege noch nicht erfolgt, erledigt und vollständig trocken, oder unklar.
modelYesFLOOR ONE S5, S7 FlashDry oder andere Modellvariante.
symptomYesSchwache Leistung, Tankmeldung, Geruch, Abschalten, elektrischer Geruch oder sichtbarer Verschleiß.

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 the safety profile is covered and the low bar applies. The description adds modest context by saying the step is 'documented' (a fixed knowledge lookup) and by hinting that the answer may be an escalation. It says nothing about how the input combination maps to the result or what form the returned guidance takes.

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?

It is short and front-loaded, but the same sentence is rendered twice in German and English with no added information in either version. That duplication is pure padding in an otherwise single-idea description.

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?

For a read-only, closed-world lookup with fully documented enum parameters and no output schema, the essentials are present. What is missing is any statement of the result shape (a single step? a ranked list?) and the role the 'care' precondition plays in selecting that step, which an agent would need to trust 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 description coverage is 100% and all three parameters are enums with per-value explanations, so the schema carries the semantic load. The description only echoes 'Modell und Symptom' and never mentions the 'care' parameter (care not yet done / done and dry / unsure), leaving it to the schema to explain why that precondition changes the answer. Baseline 3 applies.

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 names a specific verb+resource: look up the documented care or escalation step for a Tineco symptom, scoped by model and symptom. It is unambiguous about what the tool returns. It does not distinguish itself from any sibling, though no sibling in the list covers Tineco care lookup, so the cost of that omission is low.

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 only implied: an agent can infer it should call this when a Tineco symptom needs a documented care or escalation step, since 'escalation step' hints at a triage role. There is no explicit when-to-use or when-not-to-use statement and no named alternative for symptom handling.

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