Skip to main content
Glama
natejonesbaby

PostGrid MCP Server

postgrid_create_letter

Send physical letters through PostGrid, selecting First Class, Certified, or Certified with Return Receipt. Preview the mailing details before confirming to trigger the actual send.

Instructions

Send a physical letter via PostGrid. Supports standard First Class, Certified Mail, and Certified Mail with Return Receipt. Call without confirmed=true to preview the send details; call with confirmed=true to actually send.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
toYesRecipient: contact ID (e.g., 'contact_xxx') or inline object as JSON string
fromYesSender: contact ID or inline object as JSON string
htmlNoLetter content as HTML (use this OR template OR uploadedPDF)
colorNoPrint in color (default: false)
sendDateNoScheduled send date in YYYY-MM-DD format
templateNoTemplate ID to use for letter content
confirmedNoSet to true to confirm and send. Without this, only a preview is returned.
descriptionNoInternal description
doubleSidedNoPrint double-sided (default: false)
uploadedPDFNoURL of a PDF to use as letter content
envelopeTypeNoEnvelope type (e.g., 'standard_window', 'standard_double_window')
mailingClassNoMailing class: 'first_class' (default), 'standard_class', 'certified', 'certified_return_receipt'
mergeVariablesNoTemplate merge variables as key-value pairs
addressPlacementNoWhere to print the address: 'top_first_page' (overlays address on page 1) or 'insert_blank_page' (adds a separate address page, preserving your content). Automatically defaults to 'insert_blank_page' when uploadedPDF is provided, since PDFs are pre-formatted and the overlay would cover existing content. Defaults to 'top_first_page' for HTML/template content.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.9/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It usefully explains the two-phase preview/confirmed workflow, but it does not disclose that sending is a real-world, likely costly and irreversible action, nor does it describe what the preview returns.

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?

The description is three sentences with no wasted words. It front-loads the core action, then explains the critical preview/confirmed workflow, making every sentence earned.

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?

The input schema is detailed, but there is no output schema and no annotations. The description covers the essential confirmation workflow but omits response shape, physical-mail side effects, and guidance on choosing among html, template, and uploadedPDF, leaving meaningful gaps for an autonomous agent.

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 100%, so the baseline is 3. The description restates the confirmed behavior and mailing classes already described in the schema without adding new parameter-level meaning or clarifying contact IDs vs inline objects further.

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?

The description uses a specific verb and resource: 'Send a physical letter via PostGrid.' It is clearly distinct from sibling tools like postgrid_cancel_letter, postgrid_get_letter, and postgrid_create_cheque, and it names supported mailing classes, leaving no ambiguity about what the tool does.

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?

The description provides clear operational guidance: call without confirmed=true to preview, and with confirmed=true to actually send. It does not explicitly contrast this tool with alternatives or state when to choose it over related letter tools, so it stops short of a 5.

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