Skip to main content
Glama
serve-delivery-mcp

serve-delivery-mcp

by edtechniti

List deliveries

list_deliveries
Read-only

Retrieve deliveries newest first, defaulting to active jobs only, to review current delivery activity or include completed deliveries by disabling the active-only filter.

Instructions

List deliveries, newest first. Defaults to active deliveries only.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_deliveries"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
active_onlyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/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 safety is covered. The description adds the ordering guarantee and the default filter behavior, which are useful, but it says nothing about pagination limits, total counts, or how to see non-active deliveries beyond flipping a flag.

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 short sentences, front-loaded with the resource and ordering, then the default filter. No redundant or filler wording; every clause carries information.

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 simple two-parameter read tool with no output schema, the description covers purpose, ordering, and the default filter, which is close to sufficient. It still leaves the shape of returned deliveries and the effect of limit unexplained, which matters since no output schema exists.

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 0%, so the two parameters (limit, active_only) are documented only by type and default. The description compensates partly by explaining that active-only is the default, but it never explains limit's purpose or the maximum of 100, leaving the pagination parameter without semantic guidance.

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?

States a specific verb and resource ("List deliveries") and adds ordering ("newest first"), so an agent can distinguish it from mutation siblings like cancel_delivery or dispatch_robot. It does not name any read-side alternative (e.g. track_delivery), so differentiation from siblings is only partial.

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?

The default scoping note ("Defaults to active deliveries only") implies when this list view is appropriate, but there is no explicit when-to-use or when-not-to-use guidance and no routing to siblings such as track_delivery for a single delivery's status.

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