Skip to main content
Glama

getecoback-raumklima

trockner_wqg241001_programmlimit_statt_nennladung

Read-only

Vergleiche die eigene Trockenladung mit der belegten Grenze des gewählten Programms — Compare the actual load with the documented cycle limit

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": {
      "wqg241001": "<wqg241001>",
      "ladung_kg": "<ladung_kg>",
      "grenze_programm_kg": "<grenze_programm_kg>",
      "gleiche_programmkennung": "<gleiche_programmkennung>"
    },
    "name": "trockner_wqg241001_programmlimit_statt_nennladung"
  }
}

Input Schema

NameRequiredDescriptionDefault
ladung_kgYesTatsächliche Ladung in kg, nach Definition der Programmangabe
wqg241001YesExakte Trocknerreferenz WQG241001 bestätigt
grenze_programm_kgYesZulässige Last im gewählten Programm, 0 wenn nicht belegt
gleiche_programmkennungYesDokumentation nennt bei derselben Variante das vorgesehene Programm ausdrücklich

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/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 clear. The description adds that the comparison is against a documented cycle limit, but it does not describe what the comparison returns, how limits of 0 are treated, or any edge-case behavior, leaving a moderate gap for a read-only tool.

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 with a bilingual translation. It is efficient and wastes little space, though the German/English duplication is slightly redundant.

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?

The tool is a simple read-only comparison with four fully documented required parameters and no output schema. The description covers the purpose adequately but does not explain the return value or result format, which is important given the absence of an output schema.

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 parameters are already fully documented in the schema. The description adds no additional meaning beyond what the schema provides, which is the expected baseline when schema coverage is complete.

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 states a specific verb and resource: comparing the actual dryer load against the documented limit of the selected program. It is clear what the tool does, but it does not differentiate itself from similar-sounding siblings such as trockner_programmdauer_lastvergleich_lesen.

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 guidance on when to use this tool, when not to use it, or which alternatives exist. The description merely states what it does without any usage context or prerequisites.

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