Skip to main content
Glama

address_validate

Check a delivery address: the contiguous US + DC, or Hong Kong; no PO boxes or military addresses.

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": {
      "ship_to": "<ship_to>"
    },
    "name": "address_validate"
  }
}

Input Schema

NameRequiredDescriptionDefault
ship_toYesDelivery address: a JSON file, inline JSON, or - for stdin. As an object: US {name, line1, city, state, postal_code}; Hong Kong {name, line1, district, area, phone, email, country: "HK"}.

Output Schema

NameRequiredDescriptionDefault
okYes
dataNo
errorNo
summaryNo
warningsNo
next_actionsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare openWorldHint=true, readOnlyHint=false, idempotentHint=false, and destructiveHint=false, while the description adds useful validation rules about supported geography and excluded address types. It does not explain why the tool is not marked read-only or idempotent, nor does it describe side effects, authentication, or rate limits. With annotations present the bar is lower, so this is adequate but not rich.

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?

The description is a single front-loaded sentence that states the action, supported regions, and exclusions without filler. Every clause adds a constraint the caller needs.

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?

For a one-parameter validation tool with a rich input schema and an output schema, the description covers the supported geography and rejection rules needed to invoke it correctly. It omits workflow guidance and does not reconcile the non-read-only annotation, but those gaps are relatively minor for this level of tool complexity.

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 100%, so the nested ship_to formats for US and Hong Kong are already documented. The description still adds eligibility constraints not present in the schema—contiguous US + DC only and no PO boxes or military addresses—which directly affect how the parameter should be supplied.

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?

The description states a specific verb ('Check') and resource ('a delivery address'), then immediately limits it to the contiguous US + DC or Hong Kong and excludes PO boxes and military addresses. This is specific enough that an agent can tell it apart from the order, pickup, and ticket siblings 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 Guidelines3/5

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

It defines which addresses are eligible and which are rejected, which helps decide whether a given address can be checked. However, it does not say when in a workflow to call it (e.g., before order_create) or point to any alternative for unsupported addresses, so usage guidance 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.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources