Skip to main content
Glama

Logisticoo Freight

Richtpreis Straßentransport / Indicative road freight price

estimate_transport_price
Read-onlyIdempotent

Non-binding indicative price range (EUR net) for one dedicated vehicle between two locations in Europe — same formula as the calculator on the operator's website. No booking is made. Location needs country plus city (or German postal code). Returns status: estimated | needs_information (answer the questions and call again) | manual_quote_required | unsupported. Never present the result as a fixed price.

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>"
    },
    "name": "estimate_transport_price"
  }
}

Input Schema

NameRequiredDescriptionDefault
originYes
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
destinationYes
pickup_dateNoYYYY-MM-DD
dimensions_cmNoLargest single piece
loading_metersNo
dangerous_goodsNo
temperature_controlledNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, and the description adds meaningful behavior beyond them: no booking is created, results are non-binding, the four possible status values, and the instruction never to present the result as a fixed price. It stops short of describing what the price payload contains or how wide the range typically is.

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?

The core definition, the no-booking caveat and the status enumeration are front-loaded in three dense sentences with little wasted wording. The em-dash aside about the website calculator is mildly promotional but brief.

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 12-parameter tool with nested location objects and no output schema, the description covers the important unknowns: non-binding nature, currency and net basis, location input requirements, and all status outcomes including the manual-quote escape hatch. Only the shape of the returned range and handling of optional cargo attributes remain unexplained.

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 description coverage is only 25%, and the description compensates for just part of that gap by stating that a location needs country plus city, or a German postal code. It says nothing about the roles of weight_kg, pallets, loading_meters, dangerous_goods, temperature_controlled, oversize or language, leaving half the surface to the schema's own inline text.

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 names a specific verb and resource: an indicative price range (EUR net) for one dedicated vehicle between two European locations, explicitly non-binding. It distinguishes itself from booking tools by stating 'No booking is made', though it never names the sibling tools it contrasts with (submit_inquiry, preview_inquiry).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

It gives clear context for use (quote before booking, non-binding estimate) and an explicit follow-up rule for the needs_information status: 'answer the questions and call again'. It does not explicitly say when to skip the estimate and go straight to submit_inquiry, so the routing guidance is clear but not exhaustive.

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