DirectMailAmerica — Full

Get Email Letter Polling

get_email_letter_polling

Read-onlyIdempotent

No charge. Read global Email to Letter polling settings and worker diagnostics. Requires a key issued to an administrator, directly or through OAuth with the admin scope. Legacy keys and ordinary workspace keys cannot read global administrative diagnostics.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_email_letter_polling"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`error`	No
`control`	No
`operation`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 31, 2026

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": {
+    "control": {
+      "additionalProperties": true,
+      "properties": {},
+      "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"
+}

First observedOct 22, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description still adds real behavioral context beyond them: cost ("No charge") and the authentication model (admin key directly or OAuth admin scope, with legacy/workspace keys refused). These are exactly the facts an agent needs before attempting the call and that no structured field conveys.

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?

Three short sentences, no filler: cost, then purpose, then access constraint. Each sentence carries distinct operational information and the resource being read is front-loaded before the auth caveat.

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?

With zero params, an output schema present, and rich annotations, the only things left for prose to cover are cost and access requirements, and both are stated explicitly including the negative case. Nothing an agent needs to decide whether it may call this tool 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?

Zero parameters, so there is nothing for the description to disambiguate and the baseline is 4. The description correctly avoids inventing arguments.

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?

States a specific verb ("Read") plus a precise resource ("global Email to Letter polling settings and worker diagnostics"), which cleanly separates it from the sibling update_email_letter_polling and from get_email_to_letter / get_workspace_settings. An agent can route on the words "global" and "polling" without opening the schema.

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?

Gives a clear when-to-use context via the access gate: only admin-issued keys or OAuth admin scope, and explicitly excludes legacy and ordinary workspace keys. It does not name the write-side alternative (update_email_letter_polling) for changing these settings, so the alternative routing is left implicit.

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

All DirectMailAmerica — Full tools Inspect

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

Need Help?