Skip to main content
Glama

getecoback-raumklima

wohnmobil_polster_vorne_hinten_seitenwechsel_befund

Read-only

Erkenne nach Wenden eines Polsters, ob die feuchte Beobachtung der Textilseite oder der Einbaulage folgte — Track a damp observation after turning a camper cushion

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": {
      "zuerst": "<zuerst>",
      "spaeter": "<spaeter>",
      "seiten_markiert": "<seiten_markiert>",
      "umgebung_aehnlich": "<umgebung_aehnlich>"
    },
    "name": "wohnmobil_polster_vorne_hinten_seitenwechsel_befund"
  }
}

Input Schema

NameRequiredDescriptionDefault
zuerstYesFeuchte Beobachtung vor dem Wenden
spaeterYesFeuchte Beobachtung nach dem Wenden
seiten_markiertYesDasselbe Polster wurde eindeutig gewendet und Vorder-/Hinterlage in beiden Notizen gleich bezeichnet
umgebung_aehnlichYesÄhnliche Bedingungen und gleiche Beobachtungsmethode nach dem Umlagern

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/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 locality are covered. The description adds the inferential purpose (attributing dampness to textile side vs installation orientation), which is real behavioral value. It does not disclose what the conclusion looks like or how ambiguity is reported, leaving the diagnostic output opaque.

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?

The core determination is front-loaded in a single German clause with the English gloss trailing. It is compact with no filler. Minor waste from the bilingual duplication, and the English half is too generic to earn its space fully.

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?

With four fully documented required parameters, read-only annotations, and no output schema, the definition covers enough for correct invocation. The only gap is the nature of the returned conclusion, which is a modest omission for a diagnostic tool rather than a blocking one.

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 both enum parameters carry their own descriptions, so the baseline is 3. The description supplies the conceptual frame ('Textilseite oder Einbaulage') that gives the zuerst/spaeter comparison meaning, but it adds no syntax, constraints, 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?

The description names a specific determination task: after a cushion is turned, decide whether the damp observation followed the textile side or the installation position. That is a concrete verb-plus-resource ('Erkenne ... ob ...') rather than a restatement of the name, and the side-vs-installation distinction differentiates it from cushion-handling siblings. The English half ('Track a damp observation after turning a camper cushion') is vaguer and does not reinforce the discrimination logic.

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 precondition 'nach Wenden eines Polsters' — the agent understands it applies to before/after turning observations. However, no explicit when-to-use/when-not framing appears, and no alternative sibling (e.g. re-measurement or repeat-run tools) is named for cases where the sides were not clearly marked.

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