Skip to main content
Glama

getecoback-climate-weather

trockner_programm_trockenmasse

Read-only

Trockene Bezugsmasse mit der Kapazität des konkreten Trocknerprogramms vergleichen — Check a load against the selected dryer programme’s stated capacity.

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": {
      "trockenmasse_kg": "<trockenmasse_kg>",
      "programm_max_kg": "<programm_max_kg>",
      "kapazitaetsbasis": "<kapazitaetsbasis>"
    },
    "name": "trockner_programm_trockenmasse"
  }
}

Input Schema

NameRequiredDescriptionDefault
programm_max_kgYesIn der Anleitung für genau dieses Programm erlaubte Bezugsmasse in kg.
trockenmasse_kgYesVor dem Waschen gewogene Trockenmasse der Ladung in kg.
kapazitaetsbasisYesNutzt die Anleitung für dieses Programm dieselbe Trockenmasse-Basis?

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?

The annotations already declare this as a read-only, closed-world operation, so the description only needs to add context beyond safety. It adds that the comparison uses the programme's stated capacity and depends on whether the manual uses the same dry-mass basis, but it does not explain the comparison outcome, edge cases, or what happens when kapazitaetsbasis is false.

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 compact and front-loads the action, with a concise bilingual restatement. It wastes little space, though the German and English versions largely duplicate each other rather than adding complementary detail.

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 simple three-parameter, read-only check with full schema coverage, the description covers the core intent. However, with no output schema, it does not describe what the comparison returns, and it leaves the behavioral consequence of a false kapazitaetsbasis 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 three parameters are already documented in the schema. The description reinforces that the values relate to a specific dryer programme and its capacity basis, but it adds no new syntax, units, or interpretation beyond the schema.

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 action: comparing the dry mass of a load against the stated capacity of a concrete dryer programme. It is clearly distinguishable from unrelated sibling tools. It does not specify the result format of the comparison, which keeps it 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies the tool is used to check whether a load fits a selected programme's capacity, but it gives no explicit when-to-use versus when-not-to-use guidance and names no alternative approach. The usage context is clear enough for a simple check, but it remains implicit.

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