Skip to main content
Glama

Organisations Letters Events Undeliverable

organisations_letters_events_undeliverable

Retrieve paginated undeliverable letter events for an organisation, with filters, to identify failed physical mail deliveries and support follow-up.

Instructions

Get a collection of all undeliverable events. GET /organisations/{organisationId}/deliveries/letters/events/undeliverable

Organisation-wide, paginated collection. page_number maps to page[number] and page_limit to page[limit]; query keys (language, filter, q, include, fields[...]) pass through verbatim.

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": {
      "organisation_id": "<organisation_id>"
    },
    "name": "organisations_letters_events_undeliverable"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNo
page_limitNo
page_numberNo
organisation_idYes

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?

With no annotations, the description must carry behavioral weight, and it does disclose some: the GET verb signals a read-only operation, pagination is declared, and the mapping of page_number/page_limit onto page[number]/page[limit] is spelled out. It says nothing about what the returned events contain, ordering, default/maximum page size, or what an empty result means, leaving meaningful gaps for an unannotated tool.

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?

The first sentence gives the purpose up front and the endpoint follows as corroboration; the third sentence efficiently bundles scope plus the pagination and pass-through semantics. Minimal waste, though the raw endpoint path is arguably redundant with the tool name.

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 4-parameter read tool with no output schema and no annotations, the description covers filtering and pagination adequately but leaves the response shape undocumented. An agent can construct a call correctly, yet cannot predict result fields or the semantics of the opaque query pass-through keys.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description must compensate, and it largely does: it explains that page_number and page_limit are wire-level renames of page[number] and page[limit], and that query keys (language, filter, q, include, fields[...]) are forwarded verbatim, which is real meaning absent from the schema. It does not clarify organisation_id beyond the path template or constrain the accepted values of the filter keys.

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 ("Get a collection of all undeliverable events") and pins it to an endpoint path, so the agent knows exactly which delivery-event subset this returns compared with the delivered/sent/issues siblings. It stops short of explicitly naming a sibling to differentiate against, so it is not a 5.

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?

Usage is implied rather than stated: the tool is scoped as an "organisation-wide, paginated collection" of undeliverable events, which lets an agent infer it fits failure-triage work. There is no explicit when-to-use/when-not, no mention of how this differs from the delivered or sent variants, and no prerequisite guidance for obtaining organisation_id.

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