Skip to main content
Glama

getecoback-raumklima

venta_rollwagen_belagrichtung_marketing_und_eigenbefund

Read-only

Hält Rollenmaterial, Bodenhinweis und den tatsächlichen eigenen Oberflächenbefund getrennt fest — Separate rubberized caster information and actual floor observations.

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": {
      "belag": "<belag>",
      "bodenhinweis_geprueft": "<bodenhinweis_geprueft>",
      "eigenbefund": "<eigenbefund>"
    },
    "name": "venta_rollwagen_belagrichtung_marketing_und_eigenbefund"
  }
}

Input Schema

NameRequiredDescriptionDefault
belagYesEigener auf der vorgesehenen Strecke bestätigter Belag.
eigenbefundYesEigener bereits vorliegender Sichtbefund für den belegten Aufbau.
bodenhinweis_geprueftYesGenau passende Belag- oder Pflegevorgabe für diese Oberfläche geprüft.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.8/5.0
Behavior3/5

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

The annotations already establish that this is a read-only, non-open-world operation, so the description does not need to restate safety. It adds the useful behavioral distinction that three kinds of information are kept separate, but it does not explain what the tool returns or how the separation is represented.

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

Conciseness3/5

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

The description is a single front-loaded sentence, which is efficient, but it duplicates the same idea in German and English rather than adding detail. The bilingual restatement is not harmful, yet it uses space without materially improving understanding.

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?

The tool has three required parameters, complete schema descriptions, and read-only annotations, so the structured data carries much of the burden. The description still leaves out what a caller gets back and how the separated information is surfaced, but no output schema exists and the core recording scope is at least indicated.

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 schema itself defines the enums and the meaning of each required field. The description reinforces the distinction between floor guidance and actual observation, but it adds little syntax or interpretation beyond the schema and does not map its terms cleanly to all three parameters.

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 uses a specific verb phrase ('Hält ... getrennt fest') and names three things it separates: caster material, floor note, and actual surface observation. However, the wording is broad and the English gloss introduces 'rubberized caster information,' which is not clearly reflected in the schema parameters, making it only moderately clear what the tool actually records.

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?

The description implies a use case by emphasizing separation of advisory floor information from the actual observation, but it gives no explicit guidance on when to use this tool rather than a sibling, nor does it name any alternatives or exclusions.

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