Skip to main content
Glama

getecoback-climate-weather

comfee_mddf20_wf_beleggrenze

Read-only

Für den Comfee MDDF-20DEN7 prüfen, ob eine Herstellerangabe auf die angebotene Variante übertragbar ist — Preserve the documented Comfee dehumidifier suffix and feature scope.

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": {
      "typ": "<typ>",
      "aussage": "<aussage>"
    },
    "name": "comfee_mddf20_wf_beleggrenze"
  }
}

Input Schema

NameRequiredDescriptionDefault
typYesVom Typenschild abgelesene Variante.
aussageYesZu prüfende Ausstattungsbehauptung.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.7/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 agent knows this is a safe, closed-world lookup. The description adds the useful framing that the result is a transferability judgment bounded by documented suffix and feature scope, but says nothing about how a negative or ambiguous verdict is returned. With annotations covering the safety profile, this is adequate but thin.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The German clause is front-loaded and purposeful, but the appended English fragment ('Preserve the documented Comfee dehumidifier suffix and feature scope') partly restates it in a different language without adding operational detail. Mixed-language redundancy costs clarity more than length does.

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?

For a two-parameter verdict tool with no output schema, the description should convey what a result means (transferable / not transferable / indeterminate) and what the caller does with it. Neither is addressed, and the meaning of the 'suffix and feature scope' constraint is left 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 coverage is 100% and both parameters carry their own enum descriptions ('Vom Typenschild abgelesene Variante', 'Zu prüfende Ausstattungsbehauptung'), so the schema does the heavy lifting. The description adds no further meaning about how 'typ' interacts with 'aussage' (for example, what 'unbekannt' yields). 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 does name a specific check (prüfen, ob eine Herstellerangabe übertragbar ist) against a named device (Comfee MDDF-20DEN7), so the verb+resource are identifiable. But it never says what kind of 'Herstellerangabe' is being checked beyond the vague second clause, and the tool name itself ('beleggrenze') is opaque enough that the description has to carry all the meaning. It distinguishes the device scope but not the operation from sibling verification tools.

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?

There is no statement of when to call this versus another check, no prerequisite about where the 'angebotene Variante' comes from, and no exclusions. The agent must infer usage entirely from the enum values in the schema.

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