Skip to main content
Glama

TravelCargo

Estimate quote

estimate_quote

Indicative price range for sending a package with a traveler on a known route (0.5–30 kg), optionally compared with the carrier’s published courier price including source and retrieval date. Live inventory link included.

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

Input Schema

NameRequiredDescriptionDefault
originYesOrigin city, e.g. "Berlin"
weightKgYesPackage weight in kg
destinationYesDestination city, e.g. "Mumbai"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does reasonably well: 'indicative' flags that the number is an estimate rather than a binding quote, the optional courier comparison is scoped as 'published' price plus source and retrieval date, and 'live inventory link included' tells the agent what the response contains and what to do next. It still omits operational traits such as whether results depend on live traveler availability, latency, or auth requirements.

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?

Two tight sentences with the core purpose front-loaded; the parenthetical weight range, the optional comparison, and the inventory link each carry information an agent needs. Nothing is filler.

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?

For a three-parameter tool with no annotations and no output schema, the description covers the shape of the result (range, comparison, link) but leaves open whether a route without matching travelers errors or returns empty, and what the optional comparison requires as input.

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 100%, so origin, destination, and weightKg are already fully documented with types, bounds, and examples. The description restates the weight range and only hints at route semantics via 'known route,' adding no meaning beyond 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 verb and output: an indicative price range for shipping a package via a traveler on a given route, with an optional courier-price comparison. That is clearly distinct from the trip-lookup siblings (get_trip, search_trips), though it does not call out that distinction explicitly.

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 only implied by phrases like 'for sending a package with a traveler on a known route' and the 0.5–30 kg bound; there is no explicit when-to-use rule, no statement of prerequisites (must a matching trip exist?), and no routing against get_trip or search_trips.

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