Skip to main content
Glama

getecoback-raumklima

gebrauchtangebot_erstbesichtigung_eigner_terminbeleg

Read-only

Ohne unabhängige Vorführung die Wirkung eines vereinbarten Prüfslots auf offene Kaufpunkte festhalten — Distinguish monitorable acceptance checks from checks disallowed at pickup.

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": {
      "pruefliste_vereinbart": "<pruefliste_vereinbart>",
      "entscheidungspunkte": "<entscheidungspunkte>",
      "beim_termin_gezeigt": "<beim_termin_gezeigt>",
      "aus_unabhaengigem_beleg": "<aus_unabhaengigem_beleg>"
    },
    "name": "gebrauchtangebot_erstbesichtigung_eigner_terminbeleg"
  }
}

Input Schema

NameRequiredDescriptionDefault
beim_termin_gezeigtYesDavon vor einer Zusage beim Termin ausdrücklich möglich.
entscheidungspunkteYesAlle noch offenen Schritte, die für diese Entscheidung nötig sind.
pruefliste_vereinbartYesSind die einzeln vorgesehenen gewöhnlichen Dokumenten- und Sichtprüfungen für den Übergabetermin abgestimmt?
aus_unabhaengigem_belegYesWeitere davon durch unabhängige Unterlagen bereits beantwortete Schritte.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.7/5.0
Behavior3/5

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

The annotations already establish readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds that the tool concerns the effect of an agreed inspection slot on open purchase points and acceptance checks at pickup, which is useful domain context. It still does not clarify whether "festhalten" means producing an internal record or just evaluating counts, nor how the counts interact.

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 short and front-loads the German purpose before the English clarification. However, it mixes languages and uses dense domain jargon, making it cryptic rather than efficiently clear.

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?

This is a tool with four required parameters and no output schema, so the description should clarify how the parameters relate to the acceptance-check decision. Instead it stays abstract and does not explain what the resulting record or evaluation represents. The annotations and parameter schemas provide some support, but the description is too thin for the domain complexity.

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 all four parameters have their own schema descriptions. The tool description adds no parameter-level meaning beyond what the input schema already provides, so the baseline of 3 applies.

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, "festhalten" (record/capture), with the object "Wirkung eines vereinbarten Prüfslots auf offene Kaufpunkte," which gives some purpose. The appended English clause adds a second framing: distinguishing monitorable acceptance checks from checks disallowed at pickup. However, it remains abstract and does not clearly distinguish this tool from any sibling or state exactly what is recorded.

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 phrase "Ohne unabhängige Vorführung" implies a condition under which the tool applies, but it does not explicitly say when to use this tool versus alternatives. There are no when-not guidelines, prerequisites, or named sibling tools to route the agent.

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