Skip to main content
Glama
serve-delivery-mcp

serve-delivery-mcp

by edtechniti

Get delivery quote

get_delivery_quote
Read-only

Get a robot delivery price and ETA between pickup and dropoff before dispatch; quotes expire in about 5 minutes and do not reserve a robot.

Instructions

Price and ETA for a robot delivery from pickup to dropoff. Reserves nothing. Quotes expire after about 5 minutes and can be used once. Always show the fee, ETA and both resolved addresses to the user and get their explicit approval before calling dispatch_robot.

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>",
      "dropoff": "<dropoff>"
    },
    "name": "get_delivery_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
pickupYesWhere the robot collects the items
dropoffYesWhere the robot delivers the items
dropoff_deadlineNoLatest acceptable delivery time (UTC ISO 8601)
simulate_rejectionNoMock/sandbox only: force a specific rejection for testing

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the readOnly and openWorld annotations, the description discloses critical behavior: the quote does not reserve capacity, expires after about five minutes, and can be used only once. It also adds a required user-approval step before dispatch.

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 four compact sentences, front-loaded with purpose and followed by operational constraints and the next-step approval gate. Every sentence contributes useful information without repetition.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, but the description names the key outputs to show the user: fee, ETA, and both resolved addresses. Combined with the fully documented nested address schema, it gives enough context for an agent to call and use this tool correctly.

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?

The input schema has 100% description coverage, so pickup, dropoff, deadline, and simulate_rejection are already fully documented there. The description adds only the expectation that resolved addresses be shown, not additional meaning for the input parameters themselves.

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 states a specific resource (price and ETA) and scope (robot delivery from pickup to dropoff), clearly distinguishing this quotation step from dispatch_robot by noting it reserves nothing.

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 workflow context: get a quote, show fee/ETA/addresses to the user, obtain explicit approval, then call dispatch_robot. It does not explicitly compare against other sibling tools, but the intended usage and approval gate are unambiguous.

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