Skip to main content
Glama

Deliveries Emails Create

deliveries_emails_create

Creates a new email delivery by sending a full JSON:API payload to the Pingen API for a specified organisation.

Instructions

Create a new email. POST /organisations/{organisationId}/deliveries/emails

payload is the full JSON:API document, sent through unchanged.

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": "deliveries_emails_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
payloadYes
organisation_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose one genuinely useful behavioral trait — the payload is forwarded unmodified, so the caller is responsible for a valid JSON:API document — but it says nothing about what happens after creation (does the email send immediately or get queued?), permissions, or whether the operation is reversible.

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 followed by the payload contract. The raw path/method line is somewhat redundant with the description text but does add the exact route, so little is wasted.

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?

This is a mutation endpoint with a free-form nested object parameter, zero schema coverage, no annotations, and no output schema — the most demanding combination. An agent still cannot construct a valid call from this definition alone, since the required JSON:API resource shape for `payload` is unaddressed.

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%, so the description must compensate. It meaningfully characterizes the opaque `payload` object as a full JSON:API document passed through unchanged, which is real value, but it gives no hint about required resource type or attributes, and `organisation_id` is only understood via the endpoint path 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 opens with a specific verb and resource ("Create a new email") and pins the exact endpoint, which clearly separates it from the cancel/delete/list/show siblings that share the deliveries_emails prefix. It stops short of naming an alternative explicitly, but the verb alone is differentiating.

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 guidance, no prerequisites, and no pointer to a sibling for the adjacent operations (e.g., cancelling or inspecting an email after creation). The reader can infer that this is the creation step, but nothing steers tool selection beyond the verb in the name.

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