Skip to main content
Glama

Lager-Logistik Berlin

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

Input Schema

NameRequiredDescriptionDefault
originNo
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
destinationNo
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.2/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, but the description adds real context beyond them: nothing is sent yet, the call validates the payload, the response contains exactly what will be sent plus a privacy notice and a 15-minute preview_token, and a human reply arrives by e-mail. It does not cover what a validation failure looks like or what happens if the token expires, which keeps it just short of the top.

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 tight sentences, front-loaded with the two-step framing and the 'Nothing is sent yet' reassurance before the operational instructions. No redundant restatement of the name or title.

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 flow-critical tool with no output schema, the description does well on process and return content (summary, privacy_notice, preview_token). But given 16 mostly undocumented parameters and no annotations on validation rules, an agent still lacks enough input guidance to fill the payload confidently without leaning on schema guessing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 44% across 16 parameters, several of them nested objects, so the description is expected to compensate — and it does not. The only semantic input guidance is the privacy constraint on contact data; cargo fields such as weight_kg, pallets, loading_meters, dimensions_cm, dangerous_goods, temperature_controlled, oversize, pickup_date and delivery_by are undocumented in both places.

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 — validate and preview a transport inquiry to the operator's sales team — and frames it as 'Step 1 of 2' with an explicit hand-off to submit_inquiry. An agent can distinguish it from submit_inquiry and get_service_profile without opening the 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 (call this before submit_inquiry), an explicit pre-call obligation (show the summary AND privacy_notice and obtain explicit confirmation), and a constraint on inputs ('Only use contact details the user provided for this purpose'). When-to-use and how-to-proceed are both spelled out.

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