Skip to main content
Glama

getecoback-climate-weather

wohnmessung_nachprobe_raeume_ereignisfenster

Read-only

Zwei zeitlich begrenzte Nachmessungen mit nur einem verfügbaren Gerät priorisieren — Select a feasible order for two timed room follow-ups with one meter.

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": {
      "start": "<start>",
      "a_spaetestens": "<a_spaetestens>",
      "a_dauer": "<a_dauer>",
      "b_spaetestens": "<b_spaetestens>",
      "b_dauer": "<b_dauer>",
      "wechsel": "<wechsel>"
    },
    "name": "wohnmessung_nachprobe_raeume_ereignisfenster"
  }
}

Input Schema

NameRequiredDescriptionDefault
startYesFrühester Start mit dem verfügbaren Messgerät.
a_dauerYesBenötigte Dauer der Nachmessung A.
b_dauerYesBenötigte Dauer in B.
wechselYesWegzeit und Eingewöhnung vor der zweiten Nachmessung.
a_spaetestensYesLetzte Minute für das Ende der Nachmessung A.
b_spaetestensYesLetzte Minute für Ende B.

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 the safety profile is covered by structured data. The description adds only the constraint 'one meter', which explains that the two appointments compete for a single device, but says nothing about what happens when no feasible order exists or what form the result takes. With annotations carrying the safety burden the lower bar applies, but the added behavioral value is thin.

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 definition is a single front-loaded sentence given in German and English, with no filler. The bilingual duplication is slightly redundant for an agent but adds no real bloat. Structure is clean and immediately conveys the task.

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 six required parameters, no output schema, and a combinatorial feasibility decision underneath, the definition is adequate but incomplete. Because no output schema exists, the description should at least hint at the return value (an ordering such as A-then-B / B-then-A, or a no-feasible-order signal). It does not, leaving the agent to infer the result shape.

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%, with each of the six required fields documented in German (earliest start, durations, latest end times, travel/settling time). The description adds no interpretation of how these interact — for example that 'wechsel' is inserted between the two measurements. Baseline 3 is appropriate when the schema does the documentation work.

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 task with verb and object: 'Select a feasible order for two timed room follow-ups with one meter,' in German and English. An agent can tell it is a two-appointment sequencing/feasibility computation rather than a data lookup or mutation. It stops short of differentiating itself from the many sibling room-scheduling tools, none of which are named.

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 'two timed room follow-ups with one meter' implies the scenario (two constrained appointments competing for a single device), which is a usable usage cue. However, there is no explicit when-to-use, when-not, or reference to any alternative sibling tool for related scheduling problems. Guidance is implied rather than stated.

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