Skip to main content
Glama

getecoback-raumklima

tuer_selbstschliessen_persoenlicher_durchgang_zeitbezug

Read-only

Vergleicht einen eigenen dokumentierten Zeitbedarf und die beobachtete Freigabezeit einer selbstschließenden Tür für denselben Durchgang. — Compare a person's documented passage time with the observed time available at the same self-closing doorway.

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": {
      "eigener_bedarf_s": "<eigener_bedarf_s>",
      "beobachtete_zeit_s": "<beobachtete_zeit_s>",
      "vergleichbar": "<vergleichbar>"
    },
    "name": "tuer_selbstschliessen_persoenlicher_durchgang_zeitbezug"
  }
}

Input Schema

NameRequiredDescriptionDefault
vergleichbarYesGleiche Strecke und gleicher Startpunkt in bereits vorhandenen Aufzeichnungen.
eigener_bedarf_sYesDokumentierter persönlicher Zeitbedarf bis zum Bezugsort in s.
beobachtete_zeit_sYesBeobachtete Zeit bis zum selben Bezugsort im normalen Ablauf in s.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/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 and the description need not repeat it. The description adds that the comparison is scoped to the same passage, which is useful behavioral context, but says nothing about what is computed or returned, whether the comparison is symmetric, or how a non-comparable input is treated.

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?

Very short and front-loaded, with the operative verb in the first word. The German sentence is immediately restated in English, which is mild redundancy but arguably serves cross-language agents rather than wasting space.

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?

All three parameters are required and fully documented, and no output schema exists, so the description should say what the comparison yields (a delta, a verdict, a boolean). It does not, leaving the agent unsure of the result shape for a computation-style tool. Otherwise complete for a simple read-only comparison.

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 coverage is 100% and every parameter carries its own description, including units and bounds, so the schema does the heavy lifting. The description's mention of "dokumentierter Zeitbedarf" and "beobachtete Freigabezeit" loosely maps to the two numeric parameters but adds no semantics beyond them, and the meaning of "vergleichbar" is only covered by the schema.

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?

Names a specific verb ("Vergleicht") and two specific resources: a person's documented passage time and the observed time available at the same self-closing doorway. An agent can tell this is a per-passage comparison tool rather than a measurement or logging tool. It does not, however, distinguish itself from the many sibling doorway/passage tools by name or scope.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no prerequisite, and no alternative named. The phrase "für denselben Durchgang" implies the two values must refer to the same passage, but that constraint is left to be inferred and is not framed as a usage rule or exclusion.

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