Skip to main content
Glama

getecoback-raumklima

brita_maxtra_pro_karton_folie_feuchtebeobachtung

Read-only

Sichtbare Feuchte in intakter Schutzfolie von einem unklaren äußeren oder geöffneten Paketbefund unterscheiden — Route observations about a new cartridge without judging suitability.

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": {
      "exakte_pro_originalkartusche": "<exakte_pro_originalkartusche>",
      "folie": "<folie>",
      "feuchteort": "<feuchteort>"
    },
    "name": "brita_maxtra_pro_karton_folie_feuchtebeobachtung"
  }
}

Input Schema

NameRequiredDescriptionDefault
folieYesBeobachteter Zustand der Originalschutzfolie.
feuchteortYesWo befindet sich der sichtbare Befund?
exakte_pro_originalkartuscheYesIst die neue originale MAXTRA PRO Kartusche mit intakter Produkthistorie abgelesen?

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 contributes the meaningful boundary that suitability must not be judged, which is genuine extra context. It does not disclose what the routing result looks like or how ambiguous cases are reported, leaving a gap.

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?

A single compact sentence with the key distinction front-loaded and no filler. The bilingual construction is slightly cryptic but every clause carries content.

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 classification tool with full schema coverage and no output schema, the description covers the purpose and one boundary. It remains thin on what the observation routes to and how conflicting foil/moisture-location readings should be resolved.

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 described enum values for folie and feuchteort, so the schema already carries the semantics. The description's inside-foil vs external distinction loosely mirrors the feuchteort enum but adds no format or interpretation guidance beyond it. Baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description frames the tool as distinguishing visible moisture inside intact foil from external/opened-package findings, which conveys the subject matter precisely. However, the actual operation is only implied by 'Route observations' — it never states plainly that the tool records or classifies an observation, and the name is a noun phrase rather than a verb+resource. An agent can guess the domain but not the concrete action.

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?

'Route observations about a new cartridge without judging suitability' gives an implied scope and one explicit exclusion (do not assess suitability). It never names an alternative sibling or states a when-not condition, so the agent must infer the routing from context rather than from the definition.

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