Skip to main content
Glama

Letters Send

letters_send

Send a physical letter by submitting a full JSON:API payload to Pingen for a specified organisation and letter ID.

Instructions

Send a letter. PATCH /organisations/{organisationId}/deliveries/letters/{letterId}/send

payload is the full JSON:API document (LetterSendPATCH) and is sent unchanged as the request body.

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>",
      "payload": "<payload>"
    },
    "name": "letters_send"
  }
}

Input Schema

NameRequiredDescriptionDefault
payloadYes
letter_idYes
organisation_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full burden for a mutating, real-world action. It does disclose that the payload is sent unchanged as the request body, but says nothing about irreversibility, cost/charging, validation failures, or what state the letter must be in before sending.

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?

Two short sentences, front-loaded with the action and then the payload contract. The endpoint path is arguably redundant but is the only clue to how the IDs map to the request.

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 nested, free-form payload mutation with no annotations and no output schema, the definition leaves the payload's required contents undocumented and does not describe the response. An agent could not confidently construct a valid call from this description alone.

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%, but the description usefully explains that payload is the full JSON:API document (LetterSendPATCH) transmitted verbatim, which tells the agent not to reshape it. organisation_id and letter_id are only implied by the path template and receive no explanation, and the shape of LetterSendPATCH itself is never located.

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 ("Send a letter") plus the exact endpoint, so the action is unambiguous. It does not distinguish this from near-siblings such as letters_create or letters_cancel, leaving the create-vs-send boundary implicit.

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 use this versus letters_create, nor any prerequisite such as the letter needing to be in a draft state or already created. The agent must infer the whole workflow from the name alone.

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