DirectMailAmerica — Full

Validate Address

validate_address

Read-onlyIdempotent

Check and normalize U.S. postal address formatting. This is not postal deliverability or address verification. No persistence or mailing. 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": {
      "address": "<address>"
    },
    "name": "validate_address"
  }
}

Input Schema

Name	Required	Description	Default
`address`	Yes

Output Schema

Name	Required	Description	Default
`note`	No
`error`	No
`valid`	No
`issues`	No
`operation`	Yes
`normalized`	No

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": {
+    "error": {
+      "type": "string"
+    },
+    "issues": {
+      "items": {
+        "additionalProperties": true,
+        "properties": {},
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "normalized": {
+      "additionalProperties": true,
+      "properties": {},
+      "type": "object"
+    },
+    "note": {
+      "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"
+    },
+    "valid": {
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "operation"
+  ],
+  "type": "object"
+}

First observedOct 22, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, so the safety profile is covered. The description adds genuinely new context: no persistence, no mailing side effects, and workspace authentication required — exactly the kind of behavior an agent can't infer from 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?

Four short sentences, front-loaded with what the tool does, then exclusions, then auth. Nothing is padded or repeated from the schema.

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?

An output schema exists, so return-value explanation isn't required, and the description covers scope, exclusions, and auth. It stops short of describing what happens on an invalid address (error vs. normalized output), which would round out an otherwise complete definition.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

One parameter, but it is a nested address object with eight subfields and 0% schema description coverage. The description says nothing about the individual fields (name, line1 vs line2, company optional, 2-letter state, ZIP/ZIP+4), leaving the schema's regex patterns to carry all meaning. The only added hint is 'U.S.', which merely echoes the schema's country const.

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 pair ('Check and normalize') plus resource ('U.S. postal address formatting'), and immediately scopes it away from deliverability/verification and persistence/mailing. An agent can tell this is a pure format-validation utility rather than a save/list/delete address operation.

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?

'This is not postal deliverability or address verification. No persistence or mailing' gives clear negative guidance about what the tool is not for. It doesn't name a specific sibling (e.g., 'use save_address to persist'), so the routing to alternatives is implied rather than explicit.

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?