Skip to main content
Glama

getecoback-raumklima

heizwaesche_teilfolge_beaufsichtigte_messpunkte

Read-only

Einen bereits erlaubten Trocknungsversuch vor Beginn auf erreichbare manuelle Messpunkte prüfen — Check whether both required observations can be actually taken.

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": {
      "eigenes_fenster_geprueft": "<eigenes_fenster_geprueft>",
      "a_start": "<a_start>",
      "a_ende": "<a_ende>",
      "b_start": "<b_start>",
      "b_ende": "<b_ende>",
      "abstand_noetig": "<abstand_noetig>"
    },
    "name": "heizwaesche_teilfolge_beaufsichtigte_messpunkte"
  }
}

Input Schema

NameRequiredDescriptionDefault
a_endeYesLetzte erreichbare Minute im ersten Messfenster.
b_endeYesLetzte erreichbare Minute im zweiten Messfenster.
a_startYesAnkunft am ersten Messfenster.
b_startYesAnkunft am zweiten Messfenster.
abstand_noetigYesFür den eigenen Beobachtungsplan benötigter Mindestabstand der Ablesungen.
eigenes_fenster_geprueftYesStammen die angegebenen Zeiten aus einem tatsächlich erlaubten und betreuten Aufbau?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The annotations already establish that this is a read-only, non-open-world check, and the description adds the pre-start feasibility context plus the authorization precondition. However, it does not describe the return value, failure behavior, or what happens if the observations cannot actually be taken, which matters because there is no output schema.

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

Conciseness5/5

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

The definition is a single front-loaded sentence with no wasted preamble, and the bilingual phrasing still keeps the purpose and timing constraint immediately visible. Every part contributes to understanding the check.

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 six-parameter required check with no output schema, the description gives enough to understand the purpose and timing, but it does not explain the result semantics or how the feasibility conclusion is expressed. The rich parameter schema and read-only annotations compensate partially, leaving this as minimally adequate rather than complete.

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 six parameters already have documented meanings in the input schema. The description adds no parameter-specific meaning beyond the schema, so the baseline score of 3 is appropriate.

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 (prüfen/check) and a specific resource (erreichbare manuelle Messpunkte for an already permitted drying attempt), plus the timing constraint before the attempt begins. It does not explicitly differentiate this tool from any named sibling, so it falls short of the top score for sibling differentiation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

It clearly indicates when to use the tool: before starting an already permitted supervised drying attempt. It does not name when not to use it or point to alternative sibling tools, so the guidance is clear but incomplete.

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