Skip to main content
Glama

Get a delivery quote

get_quote
Read-onlyIdempotent

Price and conditional ETA for a pickup and one or more drop-offs. Null ETA means driver availability is unconfirmed; never promise a pickup time. Free, no key. Returns a quote_id valid 15 minutes; pass it to create_delivery. The quote card shows these details: reply in one short line instead of repeating them.

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_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemsNo
pickupYes
serviceNointercity = same-day delivery to a neighbouring launch city up to 160 km by road; auto picks it when the drop-off is in oneauto
urgencyNoasap
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 cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description adds genuinely new behavior: a null ETA means unconfirmed driver availability, so the agent must never promise a pickup time. It also discloses the 15-minute quote validity and the no-key/no-cost access model, which are not visible in any structured field.

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?

The description is five tight sentences with no filler, and the most decision-relevant fact (price plus conditional ETA) leads. The closing line about replying in one short line rather than repeating the quote card usefully constrains the response format.

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, the description does well to describe the return payload (ETA, quote_id and its TTL) and the next-step handoff. However, for a tool with 8 parameters, two required objects, and nested item arrays, the absence of any guidance on the item, service, urgency, or scheduling inputs leaves real gaps.

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 only 13% across 8 parameters, including nested items and dropoffs objects, so the description must carry the load. It mentions only pickup, dropoffs, and ETA and says nothing about items, service, urgency, scheduled_at, vehicle_class, or the pickup window fields, leaving most inputs explained solely by their enum or type.

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 first sentence names a specific verb-and-resource pair: pricing and conditional ETA for a pickup with one or more drop-offs. That is far more informative than the title alone, but it never distinguishes this tool from siblings such as get_intercity_quote or get_pricing, even though the service enum here already covers intercity.

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 definition gives clear workflow routing: the returned quote_id is passed to create_delivery, and the 'Free, no key' note tells the agent this is a zero-cost pre-booking step. It does not say when to prefer get_intercity_quote or get_pricing instead, so the guidance is clear but has no explicit exclusions.

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.