Skip to main content
Glama
Sign In

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.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "formular-link"
  }
}

Input 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 des Nutzers (Pflicht beim Absenden – für Rückfragen der Containerdienste)
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 / telefon / description
      Previous value: -"Telefonnummer (optional, hilft den Anbietern bei Rückfragen)"New value: +"Telefonnummer des Nutzers (Pflicht beim Absenden – für Rückfragen der Containerdienste)"
  2. Changed3 schema fields changed
    • changedInput schema / properties / containerart / enum
      Previous value: -[
-  "absetzcontainer",
-  "abrollcontainer"
-]New value: +[
+  "absetzcontainer",
+  "abrollcontainer",
+  "unbekannt"
+]
    • changedInput schema / properties / containergroesse / enum
      Previous value: -[
-  "klein",
-  "5",
-  "7",
-  "10",
-  "gross"
-]New value: +[
+  "klein",
+  "5",
+  "7",
+  "10",
+  "gross",
+  "unbekannt"
+]
    • changedInput schema / properties / deckel / enum
      Previous value: -[
-  "ja",
-  "nein"
-]New value: +[
+  "ja",
+  "nein",
+  "unbekannt"
+]
  3. Changed1 schema field changed
    • changedInput schema / properties / containergroesse / enum
      Previous value: -[
-  "klein",
-  5,
-  7,
-  10,
-  "gross"
-]New value: +[
+  "klein",
+  "5",
+  "7",
+  "10",
+  "gross"
+]
  4. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Beyond the readOnlyHint/openWorldHint annotations, the description adds behaviorally meaningful facts: nothing is sent, the end user performs the submission, and all fields are optional. It does not say how long the link stays valid or what exactly is returned, which keeps it at 4.

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?

Four short sentences, purpose front-loaded, then the user workflow, then the no-send clarification and the optionality note. No filler or repeated schema content.

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 tool with no output schema, the description conveys the workflow well but never states what is returned (URL string? object?) or how the link is passed on. It implies the return via 'Erstellt einen Link' but does not close the gap.

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% with per-field descriptions and enums, so the schema already carries the parameter semantics. The description only adds that 'Alle Felder sind optional', which is largely redundant with required=[] and adds no field-level meaning.

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 and resource: it creates a link to the inquiry form with the supplied details prefilled. It also implicitly distinguishes itself from 'anfrage-senden' by stating 'Verschickt nichts'. The opaque 'Variante A' prefix, whose counterpart is never named, keeps it from a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It clearly sets the context: the user completes contact data, accepts the privacy terms and submits the request themselves. That is a clear when-to-use signal versus a direct-submission tool, but no sibling is named and no explicit exclusion is stated.

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