Skip to main content
Glama

Read messages

get_delivery_messages
Read-onlyIdempotent

The full message thread between you and the driver for one delivery, oldest first.

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

Input Schema

NameRequiredDescriptionDefault
delivery_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare this a read-only, idempotent, closed-world, non-destructive operation, so the safety profile is covered. The description adds genuine context beyond that: the result is the complete thread (not a summary), it is ordered oldest first, and it covers only messages between the caller and the driver. It does not address pagination or what an empty thread looks like.

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?

One sentence with no filler, and the scope constraint plus the ordering are front-loaded. It is tight, but the terseness borders on under-specification rather than optimal density.

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?

This is a simple one-parameter read with strong annotations, so the bar is modest. However, with no output schema, the description gives no indication of message record shape (sender, timestamp, body) or whether pagination applies, leaving the agent to discover return structure by calling.

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 single delivery_id parameter has no schema description (0% coverage), so the description must carry the meaning. 'For one delivery' confirms the parameter selects a delivery, but it does not clarify format or provenance (e.g., that it is the ID returned by create_delivery).

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?

Names a specific resource (the message thread between the caller and the driver) scoped to a single delivery, with a stated ordering. An agent can distinguish this from get_delivery_events and get_delivery, though it never names a sibling explicitly.

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?

Usage is only implied: you would call this to read the driver conversation for a delivery. There is no statement of when this is preferable to get_delivery_events or get_delivery, and no prerequisites (e.g., whether the delivery must be active).

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.