Skip to main content
Glama
serve-delivery-mcp

serve-delivery-mcp

by edtechniti

Get delivery route

get_delivery_route
Read-only

Fetch the planned route for a delivery, with per-leg distances and optional GeoJSON geometry for mapping.

Instructions

The robot's planned route for a delivery: distance per leg, and optionally the GeoJSON geometry for mapping.

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": {
      "delivery_id": "<delivery_id>"
    },
    "name": "get_delivery_route"
  }
}

Input Schema

NameRequiredDescriptionDefault
delivery_idYesDelivery id returned by dispatch_robot
include_geometryNoInclude GeoJSON LineStrings

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds useful content structure — per-leg distances and optional geometry — but says nothing about what happens when a delivery has no planned route yet, or whether results are cached/live. With annotations covering the basics, this is a reasonable but not rich disclosure.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

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

A single well-formed sentence with no filler; the resource comes first and the payload contents follow. It is efficient, though slightly compressed into a noun phrase rather than an actionable statement.

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?

For a simple two-parameter read tool with full schema descriptions, annotations covering safety, and no output schema, the description is nearly sufficient. Only the missing distinction from sibling route/tracking tools and the pre-dispatch precondition keep it short of complete.

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%: delivery_id is documented as coming from dispatch_robot and include_geometry as GeoJSON LineStrings. The description merely restates that geometry is optional, adding no new syntax or format detail. Baseline 3 applies when the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description identifies the resource precisely — the robot's planned route for a delivery — and enumerates its contents (distance per leg, optional GeoJSON geometry). However, it is a noun phrase with no verb, and it never distinguishes this from plausible siblings like track_delivery or get_delivery_quote, so an agent must infer whether this is a planned vs. live route.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance, no prerequisites (e.g. whether the delivery must already be dispatched), and no mention of any alternative tool. The agent is left to guess the correct moment to call this versus tracking or quoting.

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