Skip to main content
Glama

getecoback-raumklima

brita_maxtra_pro_tropfenquelle_vor_wirkungsannahme

Read-only

Bei stockendem Durchfluss Originalkartusche, Sitz und ersten Vorbereitungsbeleg getrennt prüfen — Triage missing flow documentation before attributing a filter defect.

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": {
      "genaue_kartuschenkanne_belegt": "<genaue_kartuschenkanne_belegt>",
      "beobachtung": "<beobachtung>",
      "originalteil": "<originalteil>",
      "sitz_nach_anleitung": "<sitz_nach_anleitung>",
      "vorbereitet_nach_anleitung": "<vorbereitet_nach_anleitung>"
    },
    "name": "brita_maxtra_pro_tropfenquelle_vor_wirkungsannahme"
  }
}

Input Schema

NameRequiredDescriptionDefault
beobachtungYesEigener beobachteter Durchfluss.
originalteilYesIst die originale MAXTRA PRO Kartusche als tatsächliches Exemplar bestätigt?
sitz_nach_anleitungYesDokumentierter Zustand des Sitzes laut Modellanleitung.
vorbereitet_nach_anleitungYesDokumentierte Vorbereitung nach der passenden Anleitung.
genaue_kartuschenkanne_belegtYesIst es tatsächlich die betrachtete BRITA MAXTRA PRO Kannen-Kombination?

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 safety profile is covered. The description adds the useful behavioral framing that evidence streams must be checked separately and before a defect is attributed, but it never clarifies whether this records documentation state or returns an assessment verdict. With a low-risk read-only tool that is an acceptable but not rich disclosure.

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 compact sentence plus an English gloss, with the precondition placed first and the intent second; nothing is padded. The telegraphic phrasing is dense but every clause carries information.

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 read-only triage tool with five required, fully documented enum/boolean parameters and no output schema, the description supplies the trigger and the sequencing rationale an agent needs. Only the expected result of the triage is left unstated, a minor gap given the annotated safety profile.

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% with four enums carrying their own descriptions, so the schema does the heavy lifting and a 3 is the baseline. The description's only added meaning is the instruction to evaluate the three evidence strands 'getrennt', which gently warns against conflating the cartridge, seat, and preparation inputs.

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 concrete operation (checking original cartridge, seat, and first preparation evidence separately) and frames it as triage that precedes attributing a filter defect. That distinguishes it from a general defect-diagnosis step, but it never names a sibling tool or states what the check produces, so differentiation is inferential rather than explicit.

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?

The trigger condition is explicit and front-loaded: 'Bei stockendem Durchfluss'. The clause 'before attributing a filter defect' also establishes ordering relative to a diagnosis step. It stops short of naming an alternative tool or a when-not condition, which keeps it below a 5.

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