Skip to main content
Glama

Containerdienst-Regional

by de.containerdienst-regional
OverviewDiscussionsAdmin

Vorausgefüllten Anfrage-Link erstellen (Variante A)

formular-link
Read-only

Variante A: Erstellt einen Link zu unserem Anfrageformular, in dem die übergebenen Angaben bereits eingetragen sind. Im Formular ergänzt der Nutzer seine Kontaktdaten, stimmt dem Datenschutz zu und sendet die Anfrage selbst ab. Verschickt nichts. Alle Felder sind optional.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ortNoOrt (optional)
plzNo5-stellige Postleitzahl des Aufstellorts
mailNoE-Mail-Adresse des Nutzers
nameNoNachname bzw. Firmenname (nur Buchstaben, Leerzeichen, -, &, /)
anredeNoAnrede
deckelNoContainer mit Deckel (abschließbar/regengeschützt)?
terminNoWunschtermin für die Aufstellung, Format JJJJ-MM-TT, heute oder später
messageNoNachricht an die Containerdienste, z. B. Menge, Zufahrt, Stellplatz auf Gehweg/Grundstück (optional)
strasseNoStraße und Hausnummer des Aufstellorts (optional)
telefonNoTelefonnummer (optional, hilft den Anbietern bei Rückfragen)
containerNoAbfallart. Gemischter Bauabfall = baumischabfall, Gartenabfälle = gruenschnitt, Möbel/Hausrat = sperrmuell, Unklares = sonstige.
firstnameNoVorname (nur Buchstaben, Leerzeichen, -, &, /)
containerartNoabsetzcontainer (üblich bis ca. 10 cbm, für Privatleute) oder abrollcontainer (große Mengen, ab ca. 10 cbm)
containeranzahlNoAnzahl Container
containergroesseNoklein = unter 5 cbm, 5/7/10 cbm, gross = über 10 cbm

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / containergroesse / enum
      Previous value: -[
-  "klein",
-  5,
-  7,
-  10,
-  "gross"
-]New value: +[
+  "klein",
+  "5",
+  "7",
+  "10",
+  "gross"
+]
  2. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, non-destructive, and closed-world. The description adds meaningful workflow context: the user fills in contact data, consents to privacy terms, and sends the request themselves, and the tool sends nothing. It also notes all fields are optional, though that repeats the schema's zero required parameters.

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?

Front-loads the core action and variant. Four short sentences with minimal waste, though the final 'Alle Felder sind optional' is redundant given the schema, and 'Verschickt nichts' is a useful but isolated negation.

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?

For a 15-parameter, zero-required link generator with no output schema, the description explains what the link is for and the user workflow, but does not describe the returned link format, persistence, or how to use it after creation.

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% with 15 documented parameters. The description adds only 'Alle Felder sind optional', which is already implied by required=0 in the schema, so it does not deepen parameter understanding beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: 'Erstellt einen Link zu unserem Anfrageformular' with prefilled data. It distinguishes itself from the sending sibling via 'Verschickt nichts', making clear this generates a link while anfrage-senden would send directly.

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?

Provides no explicit when-to-use guidance or comparison to the sibling 'anfrage-senden'. 'Variante A' and 'Verschickt nichts' hint at the use case but do not state conditions for selecting this tool over the alternatives.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Containerdienst-Regional toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources