Skip to main content
Glama

Organisations Letters Events Sent

organisations_letters_events_sent

Retrieves a paginated, organisation-wide collection of sent letter events, with query filters and page controls for tracking delivery activity.

Instructions

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

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

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.3/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 burden, and it does disclose useful traits: the collection is organisation-wide and paginated, and it explains that query keys pass through verbatim rather than being validated. It does not cover the read-only nature explicitly, return shape, default page size, or error behavior, which matters for a zero-annotation 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 purpose is front-loaded in one sentence, followed by the endpoint and then the parameter mapping notes. The name/title is partially restated in the opening line, but the rest of the text is dense and earns its place.

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 four-parameter paginated collection with no output schema and no annotations, the description covers pagination and query pass-through but omits what an 'event' record contains and what defaults apply when page_limit or page_number are null. It is adequate to call the tool but not complete.

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 does for three of four parameters: page_number maps to page[number], page_limit to page[limit], and query keys (language, filter, q, include, fields[...]) pass through verbatim. Only organisation_id is left unelaborated, though its role is evident from the endpoint template.

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?

The description gives a specific verb and resource ('Get a collection of all sent events') and reinforces it with the literal endpoint path. The word 'sent' is the status distinction from siblings like organisations_letters_events_delivered or _undeliverable, but the description never states that contrast explicitly, leaving the agent to infer it from names alone.

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?

There is no guidance on when to choose this tool over the sibling event collections (delivered, issues, undeliverable) or over letters_events. Usage is only implied by the word 'sent' and the endpoint path; no prerequisites, exclusions, or alternatives are named.

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