Skip to main content
Glama

Preview staged postcard campaign

spur_preview_mail_campaign
Read-onlyIdempotent

Show staged postcard artwork, recipient count, return address, cost and USPS clear zones. Returns a token tied to all sendable jobs, template and return address. Nothing dispatches until approval.

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": {
      "campaign_id": "<campaign_id>",
      "return_address_id": "<return_address_id>"
    },
    "name": "spur_preview_mail_campaign"
  }
}

Input Schema

NameRequiredDescriptionDefault
campaign_idYes
return_address_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so safety is covered structurally. The description still adds real value by stating that no dispatch occurs without approval and by disclosing the return value's nature (a token tied to all sendable jobs, template and return address) — behavior not evident from the annotations.

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?

Two tight sentences: the first lists exactly what is rendered, the second explains the token and the no-dispatch guarantee. Zero filler, and the most decision-relevant facts are front-loaded.

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 read-only, two-parameter preview tool with no output schema, the description covers what is shown, what is returned, and the safety guarantee. The one meaningful gap is the unresolved meaning of the two required identifiers, which the schema does not cover either.

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

Parameters2/5

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

Schema description coverage is 0% and neither campaign_id nor return_address_id is documented. The mention of 'return address' being displayed only obliquely hints at why a return address must be supplied, and nothing explains whether campaign_id refers to a staged draft versus a dispatched campaign.

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 ('Show staged postcard artwork, recipient count, return address, cost and USPS clear zones') and names the artifact being previewed, so an agent can identify the operation. It stops short of explicitly contrasting itself with the near-identical siblings such as spur_preview_postcard_campaign or spur_preview_letter_campaign, leaving that distinction to be inferred from the title.

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?

'Nothing dispatches until approval' implies this is a pre-dispatch preview step, which is useful circumstantial guidance. However, it never names the follow-up tool (e.g., dispatch) or states when not to use this preview, so the workflow positioning is only implied.

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