Mailrith Email Marketing

Check sequence readiness

sequences_preflight

Read-onlyIdempotent

Checks the saved Sequence, its published emails, and its sender without changing data or sending email. Permission: sequences:read. API reference: https://mailrith.com/developers/api-reference.

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": {
      "sequence_id": "<sequence_id>"
    },
    "name": "sequences_preflight"
  }
}

Input Schema

Name	Required	Description	Default
`sequence_id`	Yes	The Sequence identifier.

Output Schema

Name	Required	Description
`error`	No
`response`	No
`request_id`	Yes	The stable correlation ID for this MCP tool invocation.
`operation_id`	Yes	The stable Mailrith public API operation ID.

Schema Changelog

Changes observed during successful MCP inspections.

First observedJul 30, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, and non-destructive, so the bar is lower, yet the description still adds real value: it states the required permission scope (sequences:read) and explicitly clarifies that no email is sent, which disambiguates it from sequences_send_test. It does not describe what 'readiness' failures look like, but the output schema covers results.

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?

A single compact sentence with the behavioral guarantee front-loaded, followed by permission and reference metadata. The API reference URL is marginally useful boilerplate but does not dilute clarity.

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 one-parameter read-only check with a full output schema, the description supplies purpose, safety guarantee, and authorization scope. The only shortfall is leaving the notion of 'readiness' undefined, which an agent must infer from the tool name and output.

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?

Only one parameter exists and schema description coverage is 100%, so the schema already defines sequence_id. The description adds no extra meaning about format, source, or constraints on the identifier, making 3 the appropriate baseline.

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 ('checks') and enumerates exactly what is inspected: the saved Sequence, its published emails, and its sender. The 'preflight/readiness' framing separates it from sequences_get, though it never names that sibling explicitly.

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?

Usage is implied rather than stated: the readiness framing plus 'without sending email' suggests a pre-send validation step, but there is no explicit when-to-use or when-not-to-use guidance versus sequences_get, sequences_preview_journey, or sequences_send_test.

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

All Mailrith Email Marketing tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.