Skip to main content
Glama

getecoback-climate-weather

tuer_bestehender_kontakt_aenderung_zeitpunkt

Read-only

Ordnet eine Bodenberührung danach ein, ob sie schon vor einer bereits genehmigt umgesetzten Maßnahme an der gewöhnlichen Zimmertür dokumentiert war. — Classify whether previously recorded floor contact predated an authorised change to an ordinary room door.

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": {
      "tuerart": "<tuerart>",
      "schutzstatus": "<schutzstatus>",
      "luftweg": "<luftweg>",
      "vorher": "<vorher>",
      "nachher": "<nachher>",
      "gleiche_lage": "<gleiche_lage>"
    },
    "name": "tuer_bestehender_kontakt_aenderung_zeitpunkt"
  }
}

Input Schema

NameRequiredDescriptionDefault
vorherYesBodenberührung vor der Maßnahme dokumentiert?
luftwegYesBeleg zur Funktion des Bodenspalts.
nachherYesBodenberührung nach der Maßnahme dokumentiert?
tuerartYesNutzung der konkreten Tür.
gleiche_lageYesBelag, Ort und Bewegungsphase stimmen zwischen den Aufzeichnungen überein.
schutzstatusYesBeleg zur Schutzfunktion der konkreten Tür.

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?

The annotations already declare readOnlyHint=true and openWorldHint=false, so the safety and scope profile is covered. The description adds that the classification concerns an already authorised and implemented change to an ordinary room door, but it does not explain the classification result, decision rules, or how ambiguous values are handled. With annotations carrying the safety profile, this is adequate but not rich.

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 description is two short sentences, front-loaded with the classification operation and scenario. However, the English sentence is a direct translation of the German sentence rather than new information, so it duplicates content instead of earning its place.

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-required-parameter read-only classifier, the description sets the scenario and the schema fully documents inputs. But there is no output schema, and the description does not explain the return value or how ambiguous values such as 'offen' are resolved, leaving gaps an agent might need to fill.

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 all six parameters have descriptions, including five enums, so the schema already carries parameter meaning. The description restates the floor-contact and authorised-change context but adds no syntax, constraints, or interpretation beyond what the schema provides. Baseline 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 operation: classify whether previously recorded floor contact predated an authorised change to an ordinary room door. This is more than a restatement of the name, but it does not explicitly name or contrast any sibling tool, so differentiation relies on the agent inferring scope from the scenario.

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 description identifies the classification scenario, which implies when the tool is relevant, but it gives no explicit when-to-use guidance, no when-not guidance, and no alternative tool. With many similar door/contact siblings, an agent must infer that this is specifically for the evidentiary timing question rather than other door-related classifications.

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