Skip to main content
Glama

getecoback-raumklima

lueftung_lw_raumangebot_belegluecken

Read-only

Ermittelt welche Belege fehlen, wenn ein Angebotswert für den eigenen Aufenthaltsraum verwendet werden soll — Find missing evidence for applying a catalogue sound figure to an occupied room.

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": {
      "dokument": "<dokument>",
      "messort": "<messort>",
      "betriebsfall": "<betriebsfall>"
    },
    "name": "lueftung_lw_raumangebot_belegluecken"
  }
}

Input Schema

NameRequiredDescriptionDefault
messortYesDer betroffene Raum und definierte Aufenthaltsmesspunkt sind im Beleg enthalten.
dokumentYesWert im Angebot.
betriebsfallYesBedarfsvolumenstrom, Anlagenzustand und gewählte Messdauer sind im Beleg benannt.

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 profile is covered structurally. The description adds that the operation is a gap analysis over evidence rather than a data retrieval, but it says nothing about the form or granularity of the result. With annotations carrying the safety burden, 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 core statement is front-loaded and compact. The only waste is the full bilingual duplication, where the English sentence merely restates the German one; it improves accessibility but does not add information.

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 three-parameter, read-only analysis tool with no output schema, the description explains the input situation but not what an agent receives back (e.g. a list of missing evidence items per parameter). That is the main remaining gap given that no output schema exists to compensate.

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 three parameters (messort, dokument with its enum, betriebsfall) are already fully documented in the schema. The description only loosely echoes elements of them ('Angebotswert' ↔ dokument, 'Aufenthaltsraum' ↔ messort) without adding format, allowed-value, or interaction semantics. Baseline 3 applies.

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 names a specific verb and object: it determines which evidence documents ('Belege') are missing when a catalogue/offer sound value is to be applied to one's own occupied room. That is far more specific than a restatement of the name. It does not, however, contrast itself with near siblings such as lueftung_schallanschluss_familienwert_lesart or lueftung_oktavband_daempfungsbeleg_einzelpfad, so an agent must infer the boundary.

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?

A triggering condition is stated ('wenn ein Angebotswert für den eigenen Aufenthaltsraum verwendet werden soll'), which implies when the tool is relevant. There is no guidance on when not to use it, no named alternative for related evidence questions, and no indication of what to do with the result.

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