Skip to main content
Glama

getecoback-raumklima

schutztuer_fachliche_anfrage_systembezug_unterlagen

Read-only

Zeigt fehlende Angaben für eine fachliche Anfrage zum konkreten Feuer- oder Rauchschutz-Türsystem. — Identify missing details for a professional enquiry about the exact fire or smoke door assembly.

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": {
      "tuer_identifiziert": "<tuer_identifiziert>",
      "systemunterlage": "<systemunterlage>",
      "vorhaben_dokumentiert": "<vorhaben_dokumentiert>",
      "ansprechstelle_bekannt": "<ansprechstelle_bekannt>"
    },
    "name": "schutztuer_fachliche_anfrage_systembezug_unterlagen"
  }
}

Input Schema

NameRequiredDescriptionDefault
systemunterlageYesEine Systemunterlage zum eingebauten Abschluss liegt vor.
tuer_identifiziertYesDie eingebaute Tür ist in den Unterlagen zugeordnet.
vorhaben_dokumentiertYesDie gewünschte Änderung ist für die Anfrage konkret beschrieben.
ansprechstelle_bekanntYesZuständige Stelle für die Prüfung ist bekannt.

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 and the description need only add context. It does add that the result is a list of *missing* items judged against the exact installed system, which tells the agent the output is a gap assessment rather than a pass/fail. It does not say what form that output takes or how the four booleans combine into the verdict.

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?

Two short sentences with the core action front-loaded and no filler. The German/English duplication costs a few words but arguably aids matching across query languages, so it is a minor rather than disqualifying inefficiency.

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 read-only, four-boolean checklist tool, the definition covers what is evaluated and that the answer concerns missing items. Because there is no output schema, the description should have said what the response looks like (e.g., a list of unmet criteria), and it omits any note on how the required booleans are consumed. Adequate but with a real gap.

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 each of the four booleans carries its own description, so the schema already does the semantic work. The description adds only the framing that these checks concern the exact door system; it contributes no per-parameter meaning beyond what is structured, which is the correct baseline of 3.

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 pairs a concrete verb with a concrete resource: it reports missing details ("fehlende Angaben") for a professional enquiry tied to a specific fire/smoke door assembly. A bilingual restatement plus the qualifier "zum konkreten ... Türsystem" makes the scope unambiguous. It does not, however, contrast itself with any named alternative, so it stops short of a 5.

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 wording implies a pre-submission readiness check on a specific assembly, which is a usable usage cue, but there is no explicit when-to-use, when-not-to-use, or prerequisite statement. No alternative tool is named, so an agent must infer that this is a gate before sending an enquiry rather than a general lookup.

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