Skip to main content
Glama

getecoback-raumklima

tuer_schutzkennzeichnung_bauunterlage_belegstatus

Read-only

Trennt Systemunterlagen zur genau betrachteten Tür von sichtbaren Einzelmerkmalen wie Türschließer und unlesbarem Schild. — Distinguish records for the exact door assembly from clues such as a closer or an unreadable label.

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": {
      "fund": "<fund>",
      "identitaet_bestaetigt": "<identitaet_bestaetigt>"
    },
    "name": "tuer_schutzkennzeichnung_bauunterlage_belegstatus"
  }
}

Input Schema

NameRequiredDescriptionDefault
fundYesVerfügbarer Beleg.
identitaet_bestaetigtYesUnterlage gehört zur eingebauten Tür.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.6/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds only a conceptual distinction and says nothing about what the classification returns, how ambiguities are handled, or what happens when identity is not confirmed — meaningful gaps given the read-only annotation carries the rest.

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 parallel sentences, front-loaded with the core distinction and free of padding. The bilingual duplication is costly for a short definition but each half is tight and unambiguous on its own.

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?

With only two parameters but no output schema, the description must explain what a 'Belegstatus' result looks like and how it relates to the enum input — it does not. The agent knows the conceptual distinction but not the outcome of calling the tool, which is the central unknown here.

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 the enum values are self-describing, so the schema already does the parameter work. The description's wording echoes the enum semantics (closer, unreadable label, assigned document) but adds no format, precedence, or interpretation rules beyond it.

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 specific operation (separating/trennen) on a specific resource (Systemunterlagen for a door), and its two-clause contrast loosely maps onto the enum cases. However, it never states what the tool actually produces (a 'Belegstatus' verdict), so the purpose stays abstract and the sibling differentiation is absent.

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 explicit when-to-use or when-not-to-use guidance and no named alternative. The closest thing is the semantic contrast between a record tied to the exact door and mere visible clues, which implies a usage context but leaves it to inference.

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