Skip to main content
Glama

getecoback-raumklima

anleitung_nachtrag_kapitel_uebernahme

Read-only

Entscheide, ob ein Nachtrag eine konkrete Anleitungsstelle ersetzt oder nur ergänzt — Decide whether a manual amendment supersedes a particular instruction

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": {
      "variante_im_nachtrag": "<variante_im_nachtrag>",
      "sachstelle": "<sachstelle>",
      "anleitung_am_geraet_belegt": "<anleitung_am_geraet_belegt>"
    },
    "name": "anleitung_nachtrag_kapitel_uebernahme"
  }
}

Input Schema

NameRequiredDescriptionDefault
sachstelleYesIm Nachtrag erkennbare Beziehung zum gesuchten Kapitel
variante_im_nachtragYesNachtrag nennt die gelieferte Variante einschließlich nötiger Modellendung
anleitung_am_geraet_belegtYesUrsprüngliche Anleitung ist eindeutig der gelieferten Variante zugeordnet

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 stays consistent with it as a pure judgement/classification tool. Beyond that it adds no behavioral detail — nothing on how ambiguous cases are handled, whether the result is a single verdict, or what confidence semantics apply, even though the schema enums ('unklar', 'offen') hint that ambiguity is a first-class outcome.

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 decision question is front-loaded in a single sentence, which is efficient and easy to scan. The full English restatement adds little for a German-domain tool and is mild redundancy, but it does not obscure the core statement.

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?

With three fully documented required parameters and a read-only classification profile, the core call is adequately described. However, there is no output schema and the description does not state what the tool returns or the rule by which 'ersetzt/ergaenzt/ungenannt/unklar' is decided, leaving a real gap for a decision tool.

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 both enums carry their own explanatory text, so the schema already does the semantic work and the baseline of 3 applies. The description contributes nothing about how the three inputs combine into the decision, which is the one thing the schema cannot express.

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 concrete decision ('Entscheide, ob ein Nachtrag eine konkrete Anleitungsstelle ersetzt oder nur ergänzt'), which is a specific verb plus resource and is clearly distinct from the domain-lookup siblings listed. It stops short of naming any sibling it should be preferred over, so it is clear but not differentiating.

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?

Usage is only implied: the agent can infer it should call this when comparing an amendment against a specific instruction section, since the decision criterion (replace vs. supplement) is stated. There is no explicit when-not guidance, no prerequisites, and no mention of when a related tool would be the better choice.

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