Skip to main content
Glama

Berliner Kurierdienst

Kurierpreis laut Website-Rechner / Courier price (website calculator)

estimate_transport_price
Read-onlyIdempotent

Non-binding tariff price (EUR net and gross) for a dedicated courier run by Berliner Kurierdienst, computed by the same calculator as on https://berliner-kurierdienst.de. Domestic runs within Germany by postal code; abroad and semi-trailer return manual_quote_required. No booking is made. Returns status: estimated | needs_information | manual_quote_required | unsupported.

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

Input Schema

NameRequiredDescriptionDefault
dateNoPickup date YYYY-MM-DD (Europe/Berlin), today up to +90 days; default today
timeNoPickup time HH:MM
stopsNo
extrasNozeitfenster30 (30-min time window), zustellnachweis (proof of delivery), geldauslage (cash advance), ladehilfe (loading help)
originYes
vehicleYespkw (car), kombi (estate car), transporter (van), planensprinter (curtainside van, 1–3 pallets), lkw75 (7.5 t truck), lkw12 (12 t truck), sattel (semi-trailer: on request)
languageNo
destinationYes
waiting_minutesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent and non-destructive, and the description still adds real behavioral context: results are non-binding, mirror the public web calculator, and one of four statuses is returned (estimated, needs_information, manual_quote_required, unsupported). It does not explain what triggers needs_information or how pricing scales with stops or waiting time, which keeps it short of 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with what the tool returns and the key caveat (non-binding, no booking), then the geographic limits and the status list. Dense but each sentence carries information; the parenthetical currency detail and status enumeration are slightly compressed into run-on form.

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 nine-parameter, nested-object tool with no output schema, the description covers the essential contract: what is priced, where it applies, the fallback path, and the status vocabulary of the response. Gaps remain around the pricing effect of stops, waiting time and extras, which matter for an estimation tool.

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 44% across nine parameters, so the description must compensate. It clarifies the country and vehicle (sattel) fallback to manual quoting, but leaves stops, waiting_minutes and language undocumented in both schema and description, so partial compensation only.

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 names a specific verb and resource (non-binding tariff price for a dedicated courier run), states the provider and the exact calculation basis (same calculator as the website), and bounds scope to domestic German postal-code runs. An agent can distinguish it from submit_inquiry purely from this text because it explicitly says no booking is made.

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 boundary conditions: domestic by postal code, abroad and semi-trailer routes fall back to manual_quote_required, and no booking results from calling it. The implicit routing to the booking tools is understandable, but it does not name submit_inquiry or preview_inquiry as the follow-up alternatives, so the when-to-use-next step is left to inference.

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