Skip to main content
Glama

Preview a check

lob_checks_preview
Idempotent

Validate a check payload and receive a textual summary. Obtain a confirmation token to commit the same payload when creating the check.

Instructions

Validate a check payload and return a textual summary. Lob does not produce check proofs, so no PDF is rendered. Returns a confirmation_token to pass to lob_checks_create — required in live mode. The token binds the payload: committing a different amount or recipient is rejected.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
descriptionNoInternal description (max 255 chars).
toYesRecipient address. Either a saved address ID (`adr_…`) or an inline address.
fromYesSender (return) address. Either a saved address ID (`adr_…`) or an inline address.
send_dateNoISO 8601 timestamp (e.g. '2026-05-01T00:00:00Z') to schedule the send. Must be at most 180 days in the future.
mail_typeNoMail class. Defaults to usps_first_class for most pieces.
merge_variablesNoKey/value pairs substituted into Handlebars-style {{variables}} in your HTML/template content.
metadataNoUp to 20 string key/value pairs to attach to the resource.
billing_group_idNoBilling group ID (`bg_…`) to attribute the charge to.
use_typeNoRequired for some mail classes. 'marketing' for promotional, 'operational' for transactional.
bank_accountYesVerified Lob bank account ID.
amountYesCheck amount in USD (e.g. 125.50).
check_numberNoOptional check number; auto-assigned if omitted.
memoNoMemo line on the check (max 40 chars).
messageNoPlain-text message printed on the bottom of the check page (max 400 chars). Mutually exclusive with `check_bottom`.
check_bottomNoCustom artwork for the bottom half of the check page. Accepts a Lob template ID (`tmpl_…`), an HTML string, an https:// URL, or a base64 PDF. Mutually exclusive with `message`.
logoNoLogo printed on the check face (upper-left, grayscale; PNG or JPG).
attachmentNoSecondary document included in the envelope after the check page. Up to 6 pages.
idempotency_keyNoIdempotency key (max 256 chars). If omitted, the server auto-generates a value derived from the confirmation_token when present, otherwise a fresh UUIDv4. Lob deduplicates identical keys for 24 hours.
extraNoAdditional Lob API parameters not enumerated above. Merged into the request body verbatim. See https://docs.lob.com for the full parameter list per resource.
Behavior4/5

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

Annotations indicate idempotentHint=true and destructiveHint=false. The description adds critical behavioral insight: 'Lob does not produce check proofs, so no PDF is rendered.' This goes beyond annotations. It also explains the token's binding behavior (rejects different amount/recipient). No contradiction with 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?

The description is only three sentences, front-loading the core purpose and providing essential context without any fluff. Every sentence adds value.

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?

The tool has 19 parameters and no output schema. The description explains the main output (textual summary and token) and its usage. It could be more complete about error scenarios or the summary format, but it covers the most critical aspects for correct invocation.

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 coverage is 100% with detailed descriptions for all parameters. The description does not elaborate on individual parameters but adds value by explaining the role of the confirmation_token. Given the schema already does the heavy lifting, this is adequate.

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 definition clearly states 'Validate a check payload and return a textual summary', specifying both the action (validate) and the output (textual summary + confirmation_token). The title 'Preview a check' further reinforces the purpose. It distinguishes itself from siblings like lob_checks_create, which actually creates the check.

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 explicitly says to use this before lob_checks_create, and explains that the confirmation_token binds the payload, making it clear when and how to use the tool. However, it does not mention scenarios where preview might be skipped or alternative approaches.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/optimize-overseas/lob-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server