Skip to main content
Glama

DirectMailAmerica — Full

Generate Postcard Artwork

generate_postcard_artwork
Destructive

Generate postcard front artwork only after the human authorizes sharing prompt text with the image service, with confirmed:true and a unique UUID requestId. Uses website size/color rendering and shared 10-per-hour workspace limit. Requires production write access. Returns a PDF plus PNG resources, without mailing. Requests are not replayable: a reused requestId is rejected, not regenerated. Do not automatically retry an uncertain generation with a new ID. Workspace authentication required.

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": {
      "prompt": "<prompt>",
      "productId": "<productId>",
      "requestId": "<requestId>",
      "confirmed": "<confirmed>"
    },
    "name": "generate_postcard_artwork"
  }
}

Input Schema

NameRequiredDescriptionDefault
colorNo
promptYes
confirmedYes
productIdYes
requestIdYes

Output Schema

NameRequiredDescriptionDefault
uriNo
errorNo
pagesNo
filenameNo
mimeTypeNo
operationYes
sizeBytesNo
priceCentsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "additionalProperties": true,
      +  "description": "Read operation first for financial/mail state and recovery. Optional service fields are absent on failure. Unknown is not zero or permission to retry. Legacy service fields remain available.",
      +  "properties": {
      +    "error": {
      +      "type": "string"
      +    },
      +    "filename": {
      +      "type": "string"
      +    },
      +    "mimeType": {
      +      "type": "string"
      +    },
      +    "operation": {
      +      "additionalProperties": false,
      +      "properties": {
      +        "amountCents": {
      +          "description": "USD cents. Null means not applicable or not known; never interpret null as zero.",
      +          "type": [
      +            "integer",
      +            "null"
      +          ]
      +        },
      +        "code": {
      +          "type": "string"
      +        },
      +        "currency": {
      +          "const": "USD"
      +        },
      +        "expiresAt": {
      +          "type": [
      +            "string",
      +            "null"
      +          ]
      +        },
      +        "fundsState": {
      +          "enum": [
      +            "none",
      +            "reserved",
      +            "debited",
      +            "captured",
      +            "credited",
      +            "refunded",
      +            "unknown",
      +            "simulated"
      +          ]
      +        },
      +        "mailingState": {
      +          "enum": [
      +            "none",
      +            "submitted",
      +            "pending",
      +            "unknown",
      +            "simulated"
      +          ]
      +        },
      +        "receiptId": {
      +          "type": [
      +            "string",
      +            "null"
      +          ]
      +        },
      +        "recovery": {
      +          "additionalProperties": false,
      +          "properties": {
      +            "action": {
      +              "enum": [
      +                "none",
      +                "retry_same_request",
      +                "check_existing_job",
      +                "fresh_approval",
      +                "requires_user_action"
      +              ]
      +            },
      +            "instructions": {
      +              "type": "string"
      +            },
      +            "nextTool": {
      +              "type": [
      +                "string",
      +                "null"
      +              ]
      +            },
      +            "safeToRetry": {
      +              "type": "boolean"
      +            }
      +          },
      +          "required": [
      +            "action",
      +            "safeToRetry",
      +            "nextTool",
      +            "instructions"
      +          ],
      +          "type": "object"
      +        },
      +        "requestId": {
      +          "type": "string"
      +        },
      +        "status": {
      +          "enum": [
      +            "succeeded",
      +            "failed",
      +            "pending",
      +            "needs_review"
      +          ]
      +        },
      +        "tool": {
      +          "type": "string"
      +        }
      +      },
      +      "required": [
      +        "requestId",
      +        "tool",
      +        "status",
      +        "code",
      +        "amountCents",
      +        "currency",
      +        "expiresAt",
      +        "receiptId",
      +        "fundsState",
      +        "mailingState",
      +        "recovery"
      +      ],
      +      "type": "object"
      +    },
      +    "pages": {
      +      "type": "integer"
      +    },
      +    "priceCents": {
      +      "type": "integer"
      +    },
      +    "sizeBytes": {
      +      "type": "integer"
      +    },
      +    "uri": {
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "operation"
      +  ],
      +  "type": "object"
      +}
  2. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Goes well beyond the annotations: discloses the 10-per-hour workspace limit, production write access requirement, workspace authentication, that output is PDF+PNG and no mailing occurs, and that reused requestIds are rejected rather than regenerated. This is exactly the operational context an agent needs before calling a non-idempotent, destructive mutation.

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?

Dense but front-loaded: the human-authorization precondition and confirmed/requestId requirements lead, followed by limits and the no-retry rule. Every sentence adds real operational value with no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a non-idempotent mutation with an output schema, the description covers preconditions, rate limits, auth, return format, and the critical no-replay behavior. Nothing an agent needs to call it safely is missing.

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?

With 0% schema description coverage, the description carries the burden and does well: it explains confirmed:true, a unique UUID requestId, prompt text sharing, and size/color rendering (covering productId and color). It doesn't enumerate productId enum values or color's default, keeping it from a 5.

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?

States a specific verb (generate) and resource (postcard front artwork), plus the crucial precondition that a human authorizes sharing prompt text. Clear enough to distinguish from send/quote siblings. It doesn't explicitly distinguish itself from the sibling generate_email_postcard_artwork, so it falls just short of a 5.

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?

Explicitly states the precondition (human authorization, confirmed:true, unique UUID) and gives a strong negative rule: 'Do not automatically retry an uncertain generation with a new ID.' It doesn't name an alternative tool, so it stops short of full alternative routing.

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