Skip to main content
Glama

getecoback-climate-weather

trocknerversuch_abkuehlphase_check

Read-only

Versuchsläufe mit fehlender Abkühlphase vor dem Vergleich aussortieren — Identify early-cut dryer-cycle recordings before comparing full loads.

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": {
      "laeufe": "<laeufe>",
      "vollstaendig": "<vollstaendig>",
      "vorher_abgebrochen": "<vorher_abgebrochen>"
    },
    "name": "trocknerversuch_abkuehlphase_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
laeufeYesZahl nach Plan begonnener Läufe mit derselben Aufgabenstellung.
vollstaendigYesLäufe mit vollständigem Ende einschließlich Abkühlphase.
vorher_abgebrochenYesLäufe, bei denen sicher ein früheres Ablesen oder Abbruch dokumentiert wurde.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/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 safety and scope are covered. The description adds the comparison-gating intent, but it never explains what the tool computes or returns from the three aggregate counts, nor how it decides that a recording is 'early-cut'. With annotations carrying the safety profile, this is adequate but shallow.

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?

It is front-loaded and only two clauses long, with the operational purpose stated before the English clarification. The bilingual duplication is mildly redundant but efficient overall; no sentence is wasted.

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?

There is no output schema, and the description does not explain what the tool returns or how aggregate counts yield an identification of early-cut recordings. For a check tool whose entire value is a classification decision, this leaves a substantial gap between the stated 'aussortieren' purpose and the count-only inputs.

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 the three German parameters (laeufe, vollstaendig, vorher_abgebrochen) are already well documented in the schema. The description adds no parameter-level meaning and does not resolve the tension between 'runs to sort out' and count-based inputs; baseline 3 applies when the schema does the heavy lifting.

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 check — filtering out trial runs that lack a cooling phase before comparison — and names the domain object (dryer-cycle recordings). It is distinguishable from the many other check siblings because it is explicitly about early-cut/Abkühlphase completeness, though the phrasing 'aussortieren' is slightly abstract for a tool that only receives counts.

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 phrase 'vor dem Vergleich' establishes the moment to use it (before comparing full loads), which is genuine usage context. However, it gives no explicit exclusions, prerequisites, or alternative tools, so the agent must infer the boundary.

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