Skip to main content
Glama
Sign In

DirectMailAmerica — Full

by com.directmailamerica
OverviewDiscussionsAdmin

Save Cover Sheet

save_cover_sheet
Destructive

Create or update a reusable workspace cover sheet: name, heading, message, sans/serif font, heading/body sizes and alignment. An empty heading or message omits it. Read list_cover_sheets first; preview changes with render_cover_sheet. Use a new 64-character lowercase hexadecimal id and version:0 to create, or the existing id and current version to edit. A stale version fails; reread before saving again. Use defaultDesign to reset a draft. Maximum 25 designs. Validates fit and preserves fixed envelope address windows. No charge or mailing; does not attach the design to mail or change existing PDFs or saved quotes. Requires OAuth read/write and production workspace access, except the isolated reviewer workspace may save synthetic test designs. 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": {
      "id": "<id>",
      "version": "<version>",
      "name": "<name>",
      "design": "<design>"
    },
    "name": "save_cover_sheet"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
nameYes
designYes
versionYes

Output Schema

NameRequiredDescriptionDefault
errorNo
operationYes
coverSheetNo

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": {
+    "coverSheet": {
+      "additionalProperties": true,
+      "properties": {
+        "id": {
+          "type": "string"
+        },
+        "version": {
+          "type": "integer"
+        }
+      },
+      "type": "object"
+    },
+    "error": {
+      "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"
+    }
+  },
+  "required": [
+    "operation"
+  ],
+  "type": "object"
+}
  2. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Goes well beyond the annotations, which only flag destructiveHint=true and readOnlyHint=false: it discloses optimistic concurrency ('A stale version fails; reread before saving again'), the 'No charge or mailing; does not attach the design to mail or change existing PDFs or saved quotes' side-effect boundary, envelope-window validation, and specific auth requirements (OAuth read/write, production workspace, reviewer-workspace exception). That is exactly the extra context the destructive hint alone cannot convey.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with purpose and the create/edit rule, then constraints, then side effects and auth; nearly every sentence carries distinct information. Minor waste: 'Workspace authentication required' restates the preceding auth sentence, and the versioning story is split across two non-adjacent sentences.

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 4-required-param nested mutation with an output schema available (so return values need not be described), the description covers concurrency, cardinality limits, validation behavior, side-effect boundaries, and auth prerequisites. Nothing an agent needs before invoking it 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 must carry all parameter meaning, and it largely does: the id format, version semantics (0 to create, current to edit), the design fields, and that empty heading/message fields are omitted. However it instructs 'Use defaultDesign to reset a draft', which is not a valid parameter under the schema (additionalProperties: false), so that guidance is misleading.

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?

Opens with a specific verb plus resource and scope: 'Create or update a reusable workspace cover sheet', then enumerates the editable fields. It is clearly distinguishable from siblings like list_cover_sheets, render_cover_sheet, and delete_cover_sheet, and states both the create and update modes of a single tool.

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

Usage Guidelines5/5

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

Explicit when-to and when-not guidance with named alternative tools: 'Read list_cover_sheets first; preview changes with render_cover_sheet.' It also gives the precise selection rule between the two modes (new 64-char hex id + version:0 to create, existing id + current version to edit) and names a limit ('Maximum 25 designs').

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

All DirectMailAmerica — Full toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources