Skip to main content
Glama

DirectMailAmerica — Full

Update Email Letter Polling

update_email_letter_polling
DestructiveIdempotent

Admin-only: enable/pause global polling or set intervalMinutes from 1 to 1440 (default 10). Requires a production key issued to an administrator, directly or through OAuth with the admin scope. Legacy keys cannot control global polling. Enabling may resume already authorized autosend across workspaces. Preserves active scheduler leases; does not invoke the worker immediately.

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": {
      "enabled": "<enabled>",
      "intervalMinutes": "<intervalMinutes>"
    },
    "name": "update_email_letter_polling"
  }
}

Input Schema

NameRequiredDescriptionDefault
enabledYes
intervalMinutesYes

Output Schema

NameRequiredDescriptionDefault
errorNo
controlNo
operationYes

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": {
      +    "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"
      +}
  2. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare destructiveHint=true, idempotentHint=true and openWorldHint=true, so the bar is lower — yet the description still adds material context the annotations cannot convey: enabling 'may resume already authorized autosend across workspaces', active scheduler leases are preserved, and the worker is not invoked immediately. That is exactly the blast-radius information an agent needs before a destructive global toggle.

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?

Four tight sentences, front-loaded with the admin restriction and the action, then the credential requirement, then side effects. No filler and no repetition of the title or name.

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?

An output schema exists, so return values need not be explained. For a two-parameter, high-impact global setting, the description covers auth requirements, key-type exclusions, side effects, scope of impact and immediate-vs-deferred behavior — everything an agent needs to call it safely.

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?

Schema description coverage is 0%, so the description must carry the load; it documents the interval bounds, the default of 10, and gives 'enabled' the concrete semantics of enable vs. pause. The bounds duplicate the JSON Schema minimum/maximum, but the default and the pause meaning are genuine additions; only a brief note on whether both params are always required is missing.

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?

Starts with a specific verb pair and resource ('enable/pause global polling') plus the exact tunable ('set intervalMinutes from 1 to 1440 (default 10)'). An agent can immediately distinguish this mutation from the read-only sibling get_email_letter_polling without opening either 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?

Explicitly states the access precondition and the condition that selects it: 'Requires a production key issued to an administrator, directly or through OAuth with the admin scope. Legacy keys cannot control global polling.' That is strong when-to-use guidance, but no explicit exclusions or named alternatives (e.g., use get_email_letter_polling to inspect current state before changing it).

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