Skip to main content
Glama

getecoback-raumklima

brita_microdisc_haertezweck_vs_maxtra_kanne

Read-only

Einen belegten MicroDisc für Kaltgetränke vom beschriebenen Kalkzweck einer MAXTRA PRO Kanne unterscheiden — Match an existing filter to its documented purpose.

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": {
      "filtertyp": "<filtertyp>",
      "bedarf": "<bedarf>",
      "geraetepaar_bestaetigt": "<geraetepaar_bestaetigt>",
      "heissgeraet_angabe_bekannt": "<heissgeraet_angabe_bekannt>"
    },
    "name": "brita_microdisc_haertezweck_vs_maxtra_kanne"
  }
}

Input Schema

NameRequiredDescriptionDefault
bedarfYesEigener Zweck.
filtertypYesTatsächlich identifizierter Filter.
geraetepaar_bestaetigtYesIst die Filter-Aufnahme für das genaue System belegt?
heissgeraet_angabe_bekanntYesIst der separate Wasserhinweis des konkret verwendeten Wasserkochers oder Kaffeeautomaten bekannt?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/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 that the match is based on a documented/proven purpose, but it does not state what the tool returns, how the booleans affect the decision, or any constraints beyond that.

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 definition is a single compact sentence with an English paraphrase; nothing is wasted. It is front-loaded with the distinguishing task.

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?

The tool has four required parameters and no output schema, so the description should explain the decision result and how the inputs combine. Instead it stops at the matching concept, leaving the return behavior and boolean semantics unexplained.

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%, so all four parameters are already documented. The description only loosely echoes filter type and cold-drink purpose; it adds no meaning for geraetepaar_bestaetigt or heissgeraet_angabe_bekannt.

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 operation (unterscheiden/Match) and the two filter resources (MicroDisc, MAXTRA PRO) along with the documented-purpose concept. It does not differentiate this tool from any sibling, so it falls short of a 5.

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 explicit when-to-use or when-not-to-use guidance is given, and no alternative tools are named. The matching purpose is implied but an agent must infer the context.

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