Skip to main content
Glama

getecoback-raumklima

keller_messnotiz_zugang_und_abholung_termine

Read-only

Eine freiwillige Messrunde nur mit bestätigtem Raumzugang und rechtzeitiger Abholung planen — Check a two-person measurement role split without assuming self-access.

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": {
      "raum_frei_ab_min": "<raum_frei_ab_min>",
      "raum_frei_bis_min": "<raum_frei_bis_min>",
      "abholung_ab_min": "<abholung_ab_min>",
      "messzeit_min": "<messzeit_min>"
    },
    "name": "keller_messnotiz_zugang_und_abholung_termine"
  }
}

Input Schema

NameRequiredDescriptionDefault
messzeit_minYesFür diese eigene Beobachtung geplante Dauer ab bestätigtem Beginn.
abholung_ab_minYesAb dieser Minute ist die übernehmende Person tatsächlich vor Ort.
raum_frei_ab_minYesBestätigter Zugang zum Messort ab dieser Minute.
raum_frei_bis_minYesBestätigtes Ende desselben Zeitfensters.

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 establish that this is a read-only, non-open-world operation. The description adds useful preconditions around confirmed access, pickup timing, and the two-person split, but it does not explain what the tool returns or how it behaves if constraints are not met.

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 concise statement with no extraneous detail, and the key constraint is front-loaded. The bilingual phrasing adds slight redundancy, but it remains easy to parse.

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?

The tool has four required parameters and no output schema, so the description should clarify what the call produces. It gives the operational constraints well but leaves the return behavior and validation semantics underspecified.

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 all four time-related parameters are already documented in the input schema. The description reinforces the access and pickup concepts but does not add syntax, units, or interpretation beyond what the schema provides.

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 identifies a specific verb and resource: planning a voluntary measurement round with confirmed room access and timely pickup. It also clarifies the two-person role split and explicitly says not to assume self-access, though it remains slightly ambiguous whether the tool plans, validates, or records the round.

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 states a clear usage condition: only use it with confirmed room access and timely pickup, and do not assume self-access. However, it does not compare this tool to any sibling or explain when an alternative would be more appropriate.

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