Skip to main content
Glama

dieAnalysten Adressshop – German B2B company addresses

bestellung_anlegen

Bestellung verbindlich anlegen. Erst aufrufen, wenn der Kunde im Chat Zielgruppe, Anzahl, Preis und Zahlart gesehen und ausdrücklich zugestimmt hat, die AGB akzeptiert und bestätigt hat, dass er die Daten rechtmäßig nutzt. Dann mit bestaetigt=true, agb=true und rechtmaessig=true. Ergebnis: Bestellnummer und ggf. Zahlungslink. (erfordert die Anmeldung mit dem Kundenkonto)

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": {
      "auswahl": "<auswahl>",
      "bestaetigt": "<bestaetigt>",
      "agb": "<agb>",
      "rechtmaessig": "<rechtmaessig>",
      "verwendungszweck": "<verwendungszweck>"
    },
    "name": "bestellung_anlegen"
  }
}

Input Schema

NameRequiredDescriptionDefault
agbYestrue nur, wenn der Kunde die AGB bestätigt hat
kundeNooptionale Rechnungsadresse: firma, name, strasse, plz, ort, land, telefon, uid
limitNonur so viele Firmen (Standard: alle passenden)
auswahlYesZielgruppe. Alle Angaben optional und UND-verknüpft (Regionen untereinander ODER). Werte für „merkmale“ liefert das Tool „kriterien“, Branchen das Tool „branchen_suchen“.
zahlartNo
optionenNoZusatzangaben wie im Shop (z. B. Telefon, E-Mail, Ansprechpartner)
gutscheinNoGutscheincode, falls vorhanden
bestaetigtYestrue = der Kunde hat ausdrücklich zugestimmt
rechtmaessigYestrue nur, wenn der Kunde bestätigt hat, die Daten rechtmäßig zu nutzen
verwendungszweckYeswofür die Adressen genutzt werden, z. B. Neukundenakquise per Brief

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the annotations (readOnlyHint=false), the description discloses that the order is binding ("verbindlich"), that a customer-account login is required, and that the result is an order number and possibly a payment link. The authentication requirement and the irreversibility implied by "verbindlich" are exactly the behavioral facts an agent needs before committing a write.

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?

Purpose is front-loaded in the first sentence, followed by the precondition, the required flag values, and the result. The "Dann mit bestaetigt=true, agb=true und rechtmaessig=true" clause partly repeats the schema, and the trailing parenthetical about login sits awkwardly at the end, but nothing is padded.

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 10-parameter, nested, non-read-only tool with no output schema, the description covers the essentials: what it creates, when it may be called, that authentication is required, and what comes back. The remaining selection fields are well documented in the schema itself at 90% coverage.

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 description coverage is already 90%, so the baseline is 3; the description adds real meaning by tying the three boolean parameters to a customer-consent condition rather than letting them be set opportunistically. It does not explain zahlart, optionen, gutschein or limit beyond what the schema already documents.

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 leads with a specific verb and resource ("Bestellung verbindlich anlegen") and states the outcome (order number, possibly a payment link), so an agent knows exactly what operation this performs. It does not explicitly contrast itself with siblings such as preis_berechnen or bestellungen, which keeps it short of 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 Guidelines5/5

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

It gives an explicit call gate: "Erst aufrufen, wenn der Kunde im Chat Zielgruppe, Anzahl, Preis und Zahlart gesehen und ausdrücklich zugestimmt hat" plus AGB acceptance and lawful-use confirmation. It also states the required flag settings (bestaetigt=true, agb=true, rechtmaessig=true), which functions as a clear when-not-to-call condition for every other case.

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