Skip to main content
Glama

Dispatch approved postcard campaign

spur_dispatch_mail_campaign
Destructive

Dispatch exactly the staged campaign reviewed by spur_preview_mail_campaign. Rejects changed jobs/artwork/address and expired or cross-purpose tokens. Confirm only after the user approves the artwork and cost.

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": {
      "confirmation_token": "<confirmation_token>",
      "confirm": "<confirm>"
    },
    "name": "spur_dispatch_mail_campaign"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmYesSet to true ONLY after the user explicitly approved this exact action in the conversation. Never assume approval.
confirmation_tokenYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, openWorldHint=true and idempotentHint=false, so the safety profile is known; the description adds genuinely new behavior: the dispatch is bound to the exact staged job, and changed jobs/artwork/address or expired/cross-purpose tokens will be rejected. It does not disclose the success response, cost implications beyond the approval gate, or whether a partial dispatch can occur.

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?

Three short sentences, front-loaded with the action and its binding, followed by failure modes and the approval gate. No sentence is redundant with the name, title, or annotations.

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 destructive, irreversible one-shot dispatch with no output schema, the description covers the preconditions, the exact-target guarantee, and the validation failures that matter. What is missing is the post-call outcome (confirmation ID, queued-vs-sent state) and any cost/irreversibility statement beyond the approval prompt.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The 'confirm' parameter is already documented in the schema, but the bare 'confirmation_token' (only minLength in the schema) gains real meaning here: it is purpose-bound and expires, and cross-purpose tokens are rejected. That compensates well for the 50% schema coverage, though it does not say where or how the token is obtained.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ('Dispatch') and a precisely scoped resource ('exactly the staged campaign reviewed by spur_preview_mail_campaign'), which both defines the action and ties it to the sibling that must precede it. An agent can distinguish this from spur_preview_mail_campaign or spur_manage_mail_campaign without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives a clear precondition chain (preview first, then confirm only after the user approves the artwork and cost) plus the rejection conditions that trigger a failure. It stops short of saying what to do on rejection (e.g. re-run preview) or naming any non-alternative, so it is strong context rather than a full when/when-not map.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources