Skip to main content
Glama

Organisations Letters Events Delivered

organisations_letters_events_delivered

Retrieve a paginated collection of delivered letter events for an organisation. Use page and query filters to review delivery status across all letters.

Instructions

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

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

Input Schema

NameRequiredDescriptionDefault
queryNo
page_limitNo
page_numberNo
organisation_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations exist, so the description carries the full behavioral burden. It discloses the pagination mapping and query passthrough mechanic, which is useful, but says nothing about auth needs, rate limits, default page sizes, ordering of events, or what a delivered event record contains.

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?

Front-loaded with purpose, followed by the path and the pagination/query mapping. The raw endpoint line is mildly redundant with the name but overall there is little wasted wording.

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

Completeness2/5

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

For a 4-parameter, annotation-free tool with no output schema, the description should say more about defaults, ordering, and response shape. It covers the pagination and query mechanics but leaves the agent guessing about the return payload and safe usage.

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 0%, so the description must compensate. It does explain that page_number/page_limit map to page[number]/page[limit] and that query keys (language, filter, q, include, fields[...]) pass through verbatim, which genuinely clarifies the opaque free-form 'query' object; however organisation_id is left unexplained and no value formats or valid filter values are given.

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 delivered events') and pins it down with the endpoint path. The 'delivered' qualifier implicitly separates it from sibling event feeds (issues, sent, undeliverable), though the description never explicitly contrasts them.

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?

Mentions it is an organisation-wide, paginated collection, which implies the context in which to use it, but gives no explicit when-to-use or when-to-prefer-a-sibling guidance (e.g. vs. sent/undeliverable events) and no prerequisites.

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