Skip to main content
Glama

Logisticoo Freight

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
vehicleNosprinter (van ≤1.2 t/3 pallets), lkw75 (7.5 t truck ≤3 t/10 pallets), lkw12 (12 t truck ≤6 t/14 pallets), ftl (semi-trailer ≤24 t/33 pallets/13.6 LDM). Every estimate is for one dedicated vehicle (Komplettladung); its size follows the shipment, so pass weight_kg and pallets when known. Set ftl only if a semi-trailer is explicitly requested. Omit to pick the smallest fitting class by cargo size.
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.3/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, so safety is covered; the description nonetheless adds real context beyond them — that nothing is transmitted, that the operator's sales team replies by e-mail with a quote, and that the preview_token expires after 15 minutes. It stops short of saying what happens if the token expires or how long the preview remains valid after a parameter change.

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?

Five tight sentences, front-loaded with the workflow step and the 'nothing is sent yet' assurance before the return values and the confirmation requirement. No restatement of the name or title, and every clause carries operational information.

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?

For a 16-parameter, nested-object tool with no output schema, the description still conveys the workflow position, the return payload (summary, privacy notice, preview_token), and the mandatory next step. The remaining gap is parameter-level detail, which the schema only half-documents.

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?

With 16 parameters and only 44% schema description coverage, roughly half the inputs (pallets, weight_kg, pickup_date, loading_meters, dangerous_goods, temperature_controlled, language, phone) carry no explanation anywhere. The description adds no meaning beyond the single rule about contact details, so it does not compensate for the coverage gap on a complex nested schema.

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 states a specific verb and resource — it validates a transport inquiry and returns exactly what would be sent, plus a privacy notice and a preview_token — and explicitly positions itself as 'Step 1 of 2' ahead of submit_inquiry. An agent can distinguish it from submit_inquiry and the estimate tool without opening any 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 gives explicit sequencing ('get explicit confirmation before calling submit_inquiry'), the exact UI obligation ('show the summary AND privacy_notice to the user'), and a data-handling constraint ('Only use contact details the user provided for this purpose'). The alternative and the condition that selects it are both named.

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