Skip to main content
Glama

Letters Delete

letters_delete

Deletes a specified letter from an organisation's deliveries, returning an empty response after successful removal.

Instructions

Delete a letter. DELETE /organisations/{organisationId}/deliveries/letters/{letterId}

Answers 204; the client returns an empty document for empty bodies.

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>",
      "letter_id": "<letter_id>"
    },
    "name": "letters_delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
letter_idYes
organisation_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It helpfully discloses the HTTP method, endpoint, and that a 204 with an empty body is returned, but says nothing about irreversibility, permission/auth requirements, or side effects on delivery records — the traits that matter most for a delete.

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

Conciseness5/5

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

Three compact lines: the action first, then the endpoint, then the response contract. Nothing is padded and the most important information is front-loaded.

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?

With no annotations, no output schema, and undocumented parameters, the description covers the mechanics (endpoint, status, empty body) but omits the safety and prerequisite context an agent needs before performing an irreversible delete. Adequate for invocation, thin for decision-making.

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 description coverage is 0% for two parameters, so the description must compensate. It does add limited value by placing organisation_id and letter_id in the path template, clarifying they are address-style path identifiers, but it gives no format, validation, or sourcing guidance for either ID.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Delete a letter') and pins the exact REST endpoint with both path parameters, so an agent knows precisely which object is removed. Sibling tools like letters_cancel exist, and although the description does not name them, the verb+resource pairing is unambiguous enough to distinguish delete from cancel/send/create.

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 delete versus when to use letters_cancel, nor any prerequisites or state requirements. The agent is left to infer that this is a hard removal rather than a soft cancel, which is a consequential inference for a destructive operation.

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