Skip to main content
Glama

Certified Mail Sender

List letters

list_letters
Read-only

List this API key's letters newest first, with cursor pagination. Listing is free and requires the creating API key; it changes nothing. first_usps_scan identifies the earliest individual-letter scan, not shipment receipt; only proof_of_mailing establishes acceptance. partner_checked_at is the last successful tracking poll, not the scan date. files_deleted_at means downloads are gone. Repeated adjacent checks carry observations and last_at; at stays the first check. Timestamps are UTC RFC 3339 with milliseconds; date-only fields retain their documented calendar dates. Pass next_cursor as cursor to read the next page. Example: {"limit":20}

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_letters"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
cursorNo

Output Schema

NameRequiredDescriptionDefault
lettersYes
next_cursorYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover readOnly/destructive/openWorld, but the description adds real behavioral context beyond them: the auth model (creating API key), the fact that listing is free, cursor-based pagination, and the warning that repeated adjacent checks carry observations. Much of the remaining text explains output fields, which is useful but partly redundant given an output schema exists.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The actionable information (ordering, pagination, auth, example) is front-loaded in the opening sentences, which is good. The middle is a dense run of output-field clarifications (first_usps_scan, partner_checked_at, files_deleted_at, check/at semantics) that are not needed to invoke the tool correctly and crowd out the core guidance.

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

Completeness4/5

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

For a two-parameter read tool with annotations and an output schema, everything needed to invoke it is present: ordering, cursor continuation, free/no-op behavior, and auth requirement. It over-delivers on return-value explanation that the output schema could own, but nothing essential is missing.

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 description coverage is 0%, so the description must carry the load. It explains the cursor parameter meaningfully ('Pass next_cursor as cursor to read the next page') and gives a limit example, which resolves ambiguity the bare integer/string schema leaves. It doesn't restate the limit bounds, but those are visible in the schema.

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 first sentence gives a specific verb and resource ('List this API key's letters') plus ordering ('newest first') and pagination mode, which is enough to distinguish it from a single-letter read like get_letter. It stops short of explicitly naming a sibling or stating what it excludes, so it is clear but not maximally differentiated.

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?

It states a prerequisite ('requires the creating API key') and a cost property ('Listing is free'), and implies usage through the field-semantics notes (e.g., use proof_of_mailing rather than first_usps_scan to establish acceptance). However, there is no explicit when-to-use-this-vs-a-sibling guidance, so usage is inferred rather than directed.

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.

Resources