@instantreply/mcp

check_journey_status

Read-only

Retrieve delivery status and failure explanation for a journey enrollment by ID. Quickly diagnose why a message failed to deliver or confirm it was sent.

Instructions

Check delivery status and failure explanation for a journey enrollment.

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": {
      "enrollment_id": "<enrollment_id>"
    },
    "name": "check_journey_status"
  }
}

Input Schema

Name	Required	Description	Default
`enrollment_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Sep 12, 2026

TDQS

B3.3/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds that the call surfaces a failure explanation, not just a status, which is useful context, but says nothing about scoping, eventual consistency, or what happens for enrollments still in progress.

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?

One sentence, front-loaded with the verb and the two things returned. No filler.

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?

For a single-parameter read tool with no output schema and annotations covering safety, the description covers the essentials. It still leaves ambiguity about what status values exist and how this differs from explain_delivery_failure, which is material given the sibling list.

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 bare uuid parameter carries no documentation. The description ties the input implicitly to a 'journey enrollment', which narrows what enrollment_id means, but adds no format or sourcing detail beyond that.

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?

Clear specific verb ('Check') plus resource ('delivery status and failure explanation for a journey enrollment'). An agent understands what it returns, but the description does not distinguish it from the sibling explain_delivery_failure, which appears to overlap.

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?

No when-to-use guidance, no prerequisites, and no mention of alternatives. The presence of explain_delivery_failure and list_journey_history among siblings makes the absence of routing guidance a real gap.

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