Skip to main content
Glama

getecoback-climate-weather

altgeraete_abholhinweis_vertragsmoment_beleg

Read-only

Bei einer geplanten Haushaltslieferung Informationen und tatsächliche Nachfrage zur Altgeräteabgabe beim Vertragsschluss getrennt belegen — Audit which checkout disclosures were actually observed without turning them into a booking.

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": {
      "haushaltslieferung_bestaetigt": "<haushaltslieferung_bestaetigt>",
      "hinweis_rueckgabe": "<hinweis_rueckgabe>",
      "hinweis_abholung": "<hinweis_abholung>",
      "absicht_erfragt": "<absicht_erfragt>",
      "ausschnitt_vollstaendig": "<ausschnitt_vollstaendig>"
    },
    "name": "altgeraete_abholhinweis_vertragsmoment_beleg"
  }
}

Input Schema

NameRequiredDescriptionDefault
absicht_erfragtYesWurde im gesicherten Vertragsschritt eine konkrete Rückgabeabsicht erfragt?
hinweis_abholungYesWurde dort auch über die unentgeltliche Abholung informiert?
hinweis_rueckgabeYesEnthält der gesicherte Vertragsschritt einen Hinweis auf die unentgeltliche Rückgabe?
ausschnitt_vollstaendigYesLiegt der relevante Abschnitt des tatsächlich genutzten Vertragsschritts vollständig vor?
haushaltslieferung_bestaetigtYesNeugeräteabgabe im privaten Haushalt für diesen Kauf tatsächlich vereinbart?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/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. The description adds real context beyond that: the two disclosure strands (information given vs. actual inquiry) are kept separate, and it explicitly states no booking is created as a side effect. It does not say what happens when 'ausschnitt_vollstaendig' is false, which is the main remaining behavioral gap.

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 scope condition is front-loaded and the English gloss immediately after the German sentence resolves ambiguity for a non-native reader. The German clause is dense and slightly convoluted, but no sentence is filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a five-boolean, fully documented, read-only audit tool with no output schema, the description supplies purpose, context, and the key non-side-effect. Nothing an agent needs in order to invoke it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so a 3 is the baseline. The description earns a point above it by explaining why the boolean pairs exist separately: 'Informationen' maps to the two Hinweis fields while 'tatsächliche Nachfrage' maps to absicht_erfragt, giving the agent a rationale for filling them independently rather than collapsing them.

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 ('getrennt belegen' / audit) and a specific resource: the old-device return and pickup disclosures at the moment of contract signing for a planned household delivery. The English gloss 'Audit which checkout disclosures were actually observed' confirms it is an evidence/verification step rather than a mutation. It never names a sibling to contrast with, so the distinction from tools like 'altgeraete_abholvorgang_tatsaechliche_uebergabe' must be inferred from the name alone.

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 context is stated ('Bei einer geplanten Haushaltslieferung', at contract conclusion), and the phrase 'without turning them into a booking' implies a when-not boundary. However, no alternative tool is named for the case where the agent actually needs to record a booking or a pickup event, so the agent must guess the routing.

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