Skip to main content
Glama

getecoback-raumklima

klimageraet_bedienperson_versetzte_kurzauftraege

Read-only

Zwei versetzte manuelle Kontrollen mit der nötigen Wegezeit einer verfügbaren Person prüfen — Compare one-operator and separate-operator coverage for two fixed AC checks.

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": {
      "erstes_ende_min": "<erstes_ende_min>",
      "zweiter_beginn_min": "<zweiter_beginn_min>",
      "weg_min": "<weg_min>",
      "zweite_person_bestaetigt": "<zweite_person_bestaetigt>"
    },
    "name": "klimageraet_bedienperson_versetzte_kurzauftraege"
  }
}

Input Schema

NameRequiredDescriptionDefault
weg_minYesGemessene Dauer des vorgesehenen Wegs ohne Umstellen des Geräts.
erstes_ende_minYesEnde der ersten vorgesehenen Kontrolle.
zweiter_beginn_minYesFester Beginn der nächsten Kontrolle an einem anderen passenden Standort auf derselben Zeitachse.
zweite_person_bestaetigtYesEine andere Person hat die zweite Aufgabe unabhängig angenommen.

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?

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety and scope are covered and the description need not repeat them. It adds a useful framing detail (it compares two coverage scenarios, and the travel time is the measured path without repositioning the device), but it never says what the comparison yields or how ties/edge cases are handled. For a read-only computed check that is a modest but real gap, not a serious one.

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?

Two clauses, one German and one English, front-loading the operation before the comparative framing; it is short and easy to scan. The bilingual duplication is somewhat redundant but each half adds a slightly different nuance (the travel-time condition vs. the comparison framing), so it earns most of its length.

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?

With four fully documented required parameters and read-only annotations, the inputs are well covered, but there is no output schema and the description does not describe the return shape — the agent cannot tell whether it receives a boolean, a two-scenario breakdown, or a recommended staffing choice. For a comparison tool whose entire value is its result, that leaves the definition one step short of 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 each of the four parameters is already documented in the schema, and the description's contribution is contextual rather than definitional — it explains that the two ends/beginnings sit on the same time axis and that the comparison hinges on the travel duration. That is a mild semantic boost over the schema, but no units, boundary behavior, or interpretation of the boolean confirmation is added beyond what the schema already states.

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 names a specific operation (compare one-operator vs. separate-operator coverage) on a specific resource (two fixed, staggered AC checks plus travel time), so the agent knows this is a feasibility/coverage comparison rather than a measurement or mutation. It does not name a sibling alternative, which keeps it short of a 5, but the verb+resource pairing is unambiguous.

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?

Usage is only implied: the agent can infer this applies when it must decide whether a single available person can cover two staggered checks given travel time, versus needing a second person. There is no explicit statement of when to prefer a sibling such as the split-rest-window or condensation-check tools, and no stated preconditions beyond the required inputs.

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