Skip to main content
Glama

getecoback-climate-weather

roboter_tuerfreigabe_nachholrunde

Read-only

Bei einem normalen Türwechsel prüfen, welche gesperrten Räume der Roboter später selbst nachholt. — Check which previously closed rooms are recovered without a second start.

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": {
      "wieder_geoeffnet": "<wieder_geoeffnet>",
      "selbst_nachgeholt": "<selbst_nachgeholt>",
      "mit_neustart_nachgeholt": "<mit_neustart_nachgeholt>"
    },
    "name": "roboter_tuerfreigabe_nachholrunde"
  }
}

Input Schema

NameRequiredDescriptionDefault
wieder_geoeffnetYesGeplante Räume, deren Türen erst im laufenden Durchgang wieder geöffnet wurden.
selbst_nachgeholtYesDavon im selben Durchgang ohne neuen Auftrag gereinigte Räume.
mit_neustart_nachgeholtYesWeitere dieser Räume, die erst ein späterer Auftrag erreicht hat.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.7/5.0
Behavior2/5

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

readOnlyHint=true and openWorldHint=false already tell the agent this is a safe, closed-world read, so the description need not restate safety. Beyond that, it discloses no behavior: it does not say whether the three counts are validated against each other, what is derived or returned, or how partial/overlapping figures are handled.

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

Conciseness3/5

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

The intent is stated up front and is short, but the sentence is duplicated as a German–English pair with no added information in the second half, which is pure redundancy. The German clause 'Bei einem normalen Türwechsel prüfen' is also grammatically elliptical and slightly ambiguous.

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?

For a three-required-number computation tool with no output schema, the definition never explains what result the agent will receive or how to interpret it, which is the key missing piece. The annotations and fully documented schema cover inputs and safety, but the output side of this compute tool is entirely 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% and every parameter carries a precise German definition, so the schema does the semantic work. The description adds no additional meaning about the parameters or their numeric constraints, which matches the baseline-3 expectation when coverage is complete.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a domain-specific action (prüfen, which locked rooms the robot recovers on its own) and the scenario (a normal door change), so the general intent is graspable. But it never states what the tool actually produces from the three counts, and it offers no distinction from near-identical siblings such as roboter_wiederaufnahme_doppelpass or roboter_nacharbeit_ersatzroute.

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 'Bei einem normalen Türwechsel' implies the context in which to use it, which is more than nothing. However, there is no explicit when-not guidance, no prerequisite statement, and no named alternative for the adjacent recovery/route tools.

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