Skip to main content
Glama

Berliner Kurierdienst

Anfrage-Vorschau / Preview transport inquiry

preview_inquiry
Read-only

Step 1 of 2 for a real transport inquiry to the operator's sales team (they reply by e-mail with a quote). Validates the data and returns exactly what will be sent, a privacy notice and a preview_token (15 min). Nothing is sent yet. Show the summary AND privacy_notice to the user and get explicit confirmation before calling submit_inquiry. Only use contact details the user provided for this purpose.

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": {
      "origin": "<origin>",
      "destination": "<destination>",
      "contact": "<contact>"
    },
    "name": "preview_inquiry"
  }
}

Input Schema

NameRequiredDescriptionDefault
originYes
contactYesThe requesting person's business contact — required
messageNoAdditional notes for the sales team, max 1000 chars
palletsNo
vehicleNoRequested vehicle, free text (optional)
languageNo
oversizeNo
weight_kgNo
delivery_byNoLatest delivery date YYYY-MM-DD
destinationYes
pickup_dateNoYYYY-MM-DD
dimensions_cmNoLargest single piece
loading_metersNo
dangerous_goodsNo
cargo_descriptionNoWhat is shipped (goods, packaging), max 500 chars
temperature_controlledNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description's "Nothing is sent yet" is consistent with them while adding the crucial nuance that a later call does send data. It also discloses the 15-minute preview_token lifetime and that data is validated, which the annotations cannot convey. It does not say what a validation failure looks like, which keeps it from a 5.

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 sentences, front-loaded with the workflow position, then behavior, then the required user interaction, then the privacy constraint. No filler or restatement of the title.

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

Completeness4/5

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

With 16 parameters, nested objects and no output schema, the description usefully names the three return artifacts (summary, privacy_notice, preview_token) and the confirmation gate. It leaves the meaning of many optional logistics fields to the schema, but an agent can still call the tool correctly from what is given.

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 44% across 16 parameters and nested objects, so the description would need to compensate but mostly does not — fields like origin, destination, pickup_date, loading_meters and dangerous_goods are left entirely to the schema. It does add real meaning for the contact object by restricting it to user-provided details, which is why this is not lower than baseline.

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 (validate/preview), the resource (a transport inquiry to an operator's sales team), and its position in a workflow ("Step 1 of 2"). It names the sibling it precedes (submit_inquiry), so an agent can distinguish the two without inspecting 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?

Gives explicit sequencing (preview first, submit only after explicit user confirmation), a negative guarantee ("Nothing is sent yet"), a required UI step (show summary AND privacy_notice), and a data-handling constraint (only contact details the user supplied for this purpose). There is no ambiguity about when to call this versus submit_inquiry.

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