Skip to main content
Glama

mcp-livedatapro

by site.livedatapro
OverviewDiscussionsAdmin

getCourierShippingRates

Compare live express parcel shipping rates and delivery ETAs across DHL, UPS, FedEx, and DPD. Use when comparing door-to-door express parcel and air-freight courier quotes (DHL, UPS, FedEx, DPD) and transit ETAs by weight. Do not use for maritime 20ft/40ft ocean containers (use getContainerFreightRates) or passenger rides (use getTaxiEstimate). Requires weight in kg and returns sorted USD quotes.

Input Schema

NameRequiredDescriptionDefault
weight_kgYesTotal billable package weight in kilograms (0.1 to 1000 kg).
origin_country_zipYesOrigin ISO-2 country code and postal code hyphenated (e.g., GB-DE14, US-10001).
destination_country_zipYesDestination ISO-2 country code and postal code hyphenated (e.g., US-10001, DE-10115).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / destination_country_zip / examples
      Added value: +[
+  "US-10001"
+]
    • addedInput schema / properties / destination_country_zip / pattern
      Added value: +"^[A-Z]{2}-[A-Za-z0-9\\s-]+$"
    • addedInput schema / properties / origin_country_zip / examples
      Added value: +[
+  "GB-DE14"
+]
    • addedInput schema / properties / origin_country_zip / pattern
      Added value: +"^[A-Z]{2}-[A-Za-z0-9\\s-]+$"
    • addedInput schema / properties / weight_kg / default
      Added value: +1
    • addedInput schema / properties / weight_kg / examples
      Added value: +[
+  2.5
+]
    • addedInput schema / properties / weight_kg / maximum
      Added value: +1000
    • addedInput schema / properties / weight_kg / minimum
      Added value: +0.1
  2. Changed3 schema fields changed
    • changedInput schema / properties / destination_country_zip / description
      Previous value: -"Destination country and postal code (e.g., US-10001)"New value: +"Destination ISO-2 country code and postal code hyphenated (e.g., US-10001, DE-10115)."
    • changedInput schema / properties / origin_country_zip / description
      Previous value: -"Origin country and postal code (e.g., UK-DE14)"New value: +"Origin ISO-2 country code and postal code hyphenated (e.g., GB-DE14, US-10001)."
    • changedInput schema / properties / weight_kg / description
      Previous value: -"Package weight in kilograms"New value: +"Total billable package weight in kilograms (0.1 to 1000 kg)."
  3. First observed

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does disclose that rates are live, that results are sorted and denominated in USD, and that weight in kg is mandatory. It doesn't cover quota/rate-limit behavior, whether quotes are bookable, or coverage gaps (only four carriers listed), 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.

Conciseness5/5

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

Three tight sentences ordered purpose → when to use → when not to use, with the core capability front-loaded. No filler or restated title.

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?

No output schema or annotations exist, yet the description signals the return content (per-carrier quotes plus delivery ETAs, sorted, in USD) and the input requirement. It stops short of describing the response fields or failure modes (e.g., unsupported lane), which an agent operating without an output schema would still benefit from.

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 100% with per-parameter descriptions, formats, patterns, examples, and a 0.1–1000 kg range, so the schema already does the work. The description only echoes the weight requirement and adds no syntax detail beyond it, which matches the baseline 3.

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 (compare) plus resource (live express parcel shipping rates and delivery ETAs) and enumerates the exact carriers covered. It explicitly contrasts with ocean container and passenger-ride siblings, so an agent can distinguish it 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?

Gives both the positive condition (door-to-door express parcel and air-freight quotes by weight) and two explicit exclusions with named alternatives: getContainerFreightRates for maritime containers and getTaxiEstimate for passenger rides. Nothing is left to inference about routing.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All mcp-livedatapro toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources