Skip to main content
Glama

Intercity quote

get_intercity_quote
Read-onlyIdempotent

Price a same-day delivery to a neighbouring city: pickup in a launch city, drop-off in (or within 20 km of) another launch city in the same country at most 160 km away by road. One dedicated driver collects within about an hour; it must arrive by 21:00 local time, otherwise pickup moves to the next morning. Trips over 160 km return too_far. Returns quote_id, the price breakdown incl. the drive-back allowance, and pickup/arrival times. Free, no key.

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": {
      "pickup": "<pickup>",
      "dropoffs": "<dropoffs>"
    },
    "name": "get_intercity_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemsNo
pickupYes
dropoffsYes
scheduled_atNo
workspace_idNo
vehicle_classNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior5/5

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

Annotations already declare readOnly/openWorld=false/idempotent/non-destructive, and the description adds substantial context beyond them: no cost, no API key required, the 21:00 arrival cutoff with its next-morning pickup consequence, and the too_far outcome for >160 km routes. It also previews the response shape (quote_id, price breakdown including drive-back allowance, pickup/arrival times).

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 dense sentences with the core purpose, the eligibility constraints, the failure case, and the return payload in that order. No filler, nothing repeated from the title, and the most decision-relevant facts come first.

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?

The return values and the service-level rules are well covered and no output schema is needed, but for a six-parameter nested payload the description leaves the item and vehicle inputs unexplained. An agent could call it, but would be guessing on several input fields.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across six parameters with nested objects, so the description must carry the load and it largely does not. It never explains vehicle_class, scheduled_at, workspace_id, the items array (category, size_class, weight limits), or that dropoffs accepts up to three stops within 20 km of a launch city. The only parameter-adjacent content is the 20 km / 160 km routing constraint.

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?

Opens with a specific verb and resource ("Price a same-day delivery to a neighbouring city") and pins the scope tightly: launch city to launch city, same country, ≤160 km by road. An agent can tell this is a quoting tool for intercity lanes, though it never names the intracity sibling (get_quote) that would handle the other case.

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?

The eligibility envelope (launch city to launch city, same country, ≤160 km, must arrive by 21:00 local or pickup rolls to next morning) tells the agent when this tool applies, and it explicitly states the failure mode ("Trips over 160 km return too_far"). It stops short of naming an alternative tool to use when the trip is out of range or same-city.

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.