Skip to main content
Glama

Organisations Letters Events Issues

organisations_letters_events_issues

Retrieve a paginated collection of letter issue events across an organisation to track delivery problems and diagnose failures, with filters, query options, and field selection.

Instructions

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

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

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.4/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses that the collection is organisation-wide and paginated and explains exactly how page_number/page_limit map to page[number]/page[limit], but says nothing about permissions, rate limits, ordering, or what an 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?

Purpose is front-loaded, followed by the endpoint and then pagination/pass-through mechanics. Every sentence earns its place, though the endpoint path partly restates 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?

There is no output schema and no annotations, and the description does not describe the shape of returned event objects or pagination metadata. It covers enough to call the tool correctly but not enough to interpret results confidently.

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 explains two of four parameters (page_number, page_limit) and the semantics of the `query` pass-through keys (language, filter, q, include, fields[...]), but leaves organisation_id and the expected query value formats undocumented.

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 issue events') plus the exact endpoint path, and 'issues' narrows it against the delivered/sent/undeliverable event siblings. It does not explicitly name the sibling it contrasts with, so it falls just short of the top band.

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 only implied by the resource name: this is the 'issues' variant of letter delivery events. There is no statement of when to choose it over organisations_letters_events_delivered/sent/undeliverable, no prerequisites, and no exclusions.

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