Skip to main content
Glama

getecoback-climate-weather

brita_deckelanzeige_zeit_oder_zeit_und_menge

Read-only

Den eigenen Bedarf an einem Mengensignal gegen die dokumentierten BRITA Deckelanzeigen prüfen — Compare a time reminder against time-plus-volume indication.

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": {
      "deckel": "<deckel>",
      "genaue_anleitung_gelesen": "<genaue_anleitung_gelesen>",
      "menge_als_erinnerung_gewuenscht": "<menge_als_erinnerung_gewuenscht>"
    },
    "name": "brita_deckelanzeige_zeit_oder_zeit_und_menge"
  }
}

Input Schema

NameRequiredDescriptionDefault
deckelYesTatsächlicher Anzeigetyp am eindeutig zugeordneten BRITA Deckel.
genaue_anleitung_gelesenYesIst der Typ in der eigenen genauen Anleitung bestätigt?
menge_als_erinnerung_gewuenschtYesSoll die Anzeige für die eigene Routine auch einen mengenbezogenen Hinweis liefern?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/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 domain scope about documented lid displays and personal routine needs, but it does not describe the result format, decision logic, or any limitations.

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 description is a single front-loaded sentence plus an English gloss, with no unnecessary filler. The bilingual dash is slightly redundant but still aids clarity.

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, three-parameter advisory tool with complete schema descriptions and no output schema, less explanation is required. Still, the description does not explain what the check returns or how an agent should interpret the comparison, leaving a gap for a decision-support tool.

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 coverage is 100%, with descriptions for deckel, genaue_anleitung_gelesen, and menge_als_erinnerung_gewuenscht, so the baseline is 3. The description echoes the time-versus-volume concept but does not add meaning beyond the schema for the enum values or how the booleans affect the comparison.

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?

States that it checks one's own need for a volume signal against documented BRITA lid indicators and frames a comparison of time reminder versus time-plus-volume indication. The verb and resource are specific enough to distinguish it from generic BRITA status tools, though the exact decision output is not made explicit.

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?

The comparison framing implies use when deciding whether a time-only reminder is sufficient versus needing a volume-based reminder. However, it gives no explicit when-not-to-use guidance, prerequisites, or named alternatives among the many BRITA sibling tools.

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