Skip to main content
Glama

Berliner Kurierdienst

Anfrage absenden / Submit transport inquiry

submit_inquiry

Step 2 of 2: sends the previewed inquiry to the operator's sales team. Only call after the user explicitly confirmed the summary and privacy notice. Use a new random idempotency_key per inquiry and reuse it when retrying the same inquiry. Status accepted means we received it; it is NOT a booking and NOT a binding price — a person replies by e-mail.

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": {
      "preview_token": "<preview_token>",
      "idempotency_key": "<idempotency_key>",
      "user_confirmed": "<user_confirmed>"
    },
    "name": "submit_inquiry"
  }
}

Input Schema

NameRequiredDescriptionDefault
languageNo
preview_tokenYes
user_confirmedYestrue = the user explicitly confirmed summary and privacy notice
idempotency_keyYesRandom key, e.g. a UUID; same key for retries

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

The annotations already declare readOnlyHint=false, openWorldHint=true, and destructiveHint=false, so the safety profile is provided. The description adds high-value behavioral context beyond that: accepted status only means receipt, it is not a booking or binding price, and a person replies by e-mail.

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?

The description is front-loaded with the 'Step 2 of 2' framing and concisely covers prerequisite, retry semantics, and status interpretation. Every sentence adds operational value with no wasted wording.

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 an open-world, non-read-only submission tool with no output schema, the definition supplies the key information an agent needs: when to call, how to retry safely with idempotency_key, and what an accepted status does and does not mean.

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 only 50%, and the description helps by linking preview_token to a 'previewed inquiry' and reinforcing that user_confirmed must reflect explicit confirmation. However, it adds no detail about the optional language parameter or the preview_token format, so it only partially compensates for the schema gap.

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?

The description gives a specific verb and resource: 'sends the previewed inquiry to the operator's sales team,' and explicitly frames it as 'Step 2 of 2,' which cleanly distinguishes it from preview_inquiry. An agent can identify the operation without opening either schema.

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 states the prerequisite clearly: 'Only call after the user explicitly confirmed the summary and privacy notice.' The 'Step 2 of 2' phrasing also implies the prior preview step without requiring inference about omitted siblings.

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