Skip to main content
Glama

getecoback-climate-weather

modellhandbuch_fertigungslos_geltungsgrenze

Read-only

Prüfe, ob eine Änderung der Bedienungsanleitung das dokumentierte Fertigungslos umfasst — Check whether a manual revision applies to the documented production batch

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": {
      "modell_exakt": "<modell_exakt>",
      "los_position": "<los_position>",
      "ab_los_position": "<ab_los_position>",
      "bis_los_position": "<bis_los_position>",
      "losfolge_belegt": "<losfolge_belegt>"
    },
    "name": "modellhandbuch_fertigungslos_geltungsgrenze"
  }
}

Input Schema

NameRequiredDescriptionDefault
los_positionYesNumerischer Losstand laut Hersteller innerhalb derselben geordneten Kennung
modell_exaktYesGenaue Gerätevariante stimmt in Handbuch und Unterlagen überein
ab_los_positionYesUntergrenze der Änderung innerhalb derselben Kennungsfolge
losfolge_belegtYesHersteller verwendet eine gemeinsame numerische Loskennungsfolge und nennt beide Grenzen ausdrücklich
bis_los_positionYesObergrenze aus der ausdrücklich angegebenen Geltung

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/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 nothing further. It does not say what verdict is produced, nor what happens when losfolge_belegt is false (does the check return false, or fail?), which is the key behavioral branch for a gating check.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single sentence, front-loaded with the verb, mirrored in English for disambiguation, with zero filler. Nothing is repeated and nothing dilutes the core statement.

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 five required parameters and no output schema, the description should at minimum state what the check returns and how the boundary values are compared. It leaves the return semantics entirely unspecified, so an agent knows what to send but not what to expect back.

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 coverage is 100% and every parameter carries a substantive German description (Losstand, untere/obere Grenze, gemeinsame Kennungsfolge), so the schema does the heavy lifting. The description itself contributes no parameter meaning, which is the expected baseline of 3 when coverage is complete.

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 specific verb ("Prüfe") with a specific resource (whether a manual revision covers the documented production batch), given in both German and English. It is immediately understandable, but it offers no differentiation from nearby tools such as anleitung_nachtrag_kapitel_uebernahme or bedienunterlagen_geraeteanzeige_verschiedene_zustaende, so an agent cannot tell from the text alone which check applies.

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 when-to-use guidance, no preconditions, and no named alternative. The agent must infer from the name alone that this is the tool for batch-coverage questions rather than for chapter carry-over or document-version questions.

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