Skip to main content
Glama

Letters Create

letters_create

Creates a new letter for an organisation by submitting a complete JSON:API payload to the deliveries endpoint, enabling programmatic dispatch of physical mail.

Instructions

Create a new letter. POST /organisations/{organisationId}/deliveries/letters

payload is the full JSON:API document (LetterCreatePOST) 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>",
      "payload": "<payload>"
    },
    "name": "letters_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
payloadYes
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?

No annotations are supplied, so the description carries the full behavioral burden; it does add one useful fact — the payload is forwarded unchanged as the request body — but says nothing about required permissions, whether the letter is dispatched on creation or held, or what side effects occur. For an unannotated mutation tool this is a substantial gap.

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?

Front-loaded with the action, followed by the endpoint and one focused sentence on payload handling. The endpoint restates what the first sentence already implies, a minor redundancy, but nothing is padded.

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?

The payload is a free-form nested object with no schema and no output schema, so the agent has no way to learn which fields a LetterCreatePOST requires. Naming a type the agent cannot inspect does not close that gap, and the absence of annotations leaves the mutation's safety profile undocumented.

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 does explain 'payload' as a full JSON:API document of type LetterCreatePOST sent verbatim, which is meaningful, but it simply references an external type name without any field detail and leaves organisation_id entirely uninterpreted.

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 ('Create a new letter') and even pins the REST endpoint. It is clear what the tool does, but it never distinguishes itself from siblings such as letters_send or batches_create, so the agent cannot tell from the description alone whether 'create' also triggers delivery.

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 when-to-use or when-not-to-use guidance at all. With a sibling named letters_send sitting right next to letters_create, the agent is left to guess whether creation implies sending, which is exactly the ambiguity the description should resolve.

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