Skip to main content
Glama

Spedition Log

Ab-Preis laut Website / Starting price (website calculator)

estimate_transport_price
Read-onlyIdempotent

Starting prices exactly as published by Spedition Log on https://www.spedition-log.com/preise: part load (LTL) per pallet, full load (FTL) and 40 t semi-trailer "from" prices. No route-based calculation; direct/special runs are quoted individually. Never present a starting price as the final 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": {
      "shipment_type": "<shipment_type>"
    },
    "name": "estimate_transport_price"
  }
}

Input Schema

NameRequiredDescriptionDefault
palletsNoNumber of pallets (part load)
languageNo
shipment_typeYesltl = part load (needs pallets), ftl = full load, sattel = 40 t semi-trailer, direkt = direct/special run (individual quote)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, closed-world behavior, so the description's added value is its disclosure of provenance (prices copied from the website price list), the absence of route-based computation, and the presentation rule 'never present a starting price as the final price.' That last constraint is genuinely non-obvious behavioral guidance. It stops short of saying whether prices may be stale or how they are formatted/currencied.

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?

Two tight sentences, front-loaded with what is returned and its source, followed by the scope caveat. Minor redundancy between 'starting prices' repeated in the opening and the closing warning, but nothing is padded.

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?

With no output schema and a mutation-free read tool, the description covers provenance and the semantic caveat well. The gaps are the response shape (currency, whether a price range or single figure is returned) and the behavior when shipment_type=direkt or ltl-without-pallets is supplied, both of which an agent would need.

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 67% and the enum descriptions already explain ltl/ftl/sattel/direkt. The description corroborates the pallet-per-LTL relationship and clarifies that direct runs are individually quoted, but says nothing about the 'language' parameter or what happens if shipment_type=direkt is passed. Roughly baseline value over the schema.

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 resource (published starting prices) and enumerates exactly what is covered: LTL per pallet, FTL, and 40 t semi-trailer 'from' prices, with the source URL. It also bounds the scope by stating there is no route-based calculation, which separates it from a quoting tool. It does not name a sibling such as preview_inquiry or submit_inquiry, so differentiation is inferential rather than explicit.

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

Usage Guidelines3/5

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

Usage is implied rather than stated: the agent learns this tool yields catalogue 'from' prices and that direct/special runs are quoted individually, which hints where to go instead. There is no explicit 'use this when... use preview_inquiry when...' instruction and no stated prerequisite (e.g., that pallets is required for LTL).

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