Skip to main content
Glama

Order: Validate Address

validate_order_address
Read-onlyIdempotent

[Order] [What it does] Read-only check of one order's currently saved shipping address against DSers required-field, length, and format rules; never accepts or saves candidate address fields. [When to use] Use to inspect the saved address or investigate a reported address-rule failure before deciding whether an update is needed. [When not to use] It cannot validate an unsaved candidate address or confirm real postal deliverability. To change the address, use update_order_information. [How to use] Copy dsers_order_id from list_orders or get_order. Optional supplier_platform_id selects which supplier's address rules to load; omit, empty, or 0 defaults to AliExpress 159831080. address returns the currently saved shipping address and recipient details using the same fields and values as get_order.order.address, including street address lines, name, phone, email, tax ID, passport numbers, company, and birthday when populated. sales_order_recipient_birthday is returned exactly as stored; AliExpress Brazil rules use DDMMYYYY. Values are returned as stored, without masking; empty fields are omitted. Only supported required, length, and regexp validators with an executable pattern are included; fields and rule types this tool does not apply are omitted. passed_fields lists fields whose effective validators have no failed or unevaluable result. error_fields contains definite validation failures and returns every effective validator applied by this tool to each affected field; inspect those validator statuses because the same field may also contain an unevaluable rule. unevaluated_fields contains fields with no definite failure whose effective validators could not be checked safely. Empty error_fields and unevaluated_fields mean only that the effective rules detected no problem; they do not confirm postal deliverability. [Side effects] Read-only; no order data changes. [Confirmation] No confirmation required. [Follow-up] If error_fields is non-empty, collect the corrected fields, show the proposed change, and call update_order_information after confirmation. If unevaluated_fields is non-empty, report that an effective validator could not be checked safely. Call this Tool again only after the update if the saved address must be checked again.

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": {
      "dsers_order_id": "<dsers_order_id>"
    },
    "name": "validate_order_address"
  }
}

Input Schema

NameRequiredDescriptionDefault
dsers_order_idYesCopy from list_orders results orders[].dsers_order_id field. Required.
supplier_platform_idNoOptional supplier platform ID whose address rules should be used. Copy from list_stores supplier_apps[].supplier_platform_id. Omit, empty, or 0 defaults to AliExpress 159831080.

Output Schema

NameRequiredDescriptionDefault
addressYesCurrently saved shipping address and recipient details, with the same fields and values as get_order order.address
error_fieldsYesFields with at least one definite required, length, or regular-expression failure; validators contains every effective validator applied by this tool to each field
passed_fieldsYesFields whose effective validators produced no failure or unevaluable result
dsers_order_idYesDSers order ID as a decimal string
unevaluated_fieldsYesFields with no definite validation failure but at least one effective validator that could not be evaluated safely
toolcall_response_atYesUTC timestamp when the Tool response was returned, formatted as RFC3339.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare readOnlyHint/idempotentHint/destructiveHint=false, yet the description adds substantive behavior: which validator types are applied (required, length, regexp with executable pattern), the exact meaning of passed_fields / error_fields / unevaluated_fields, that the same field may carry an unevaluable rule, and that empty error fields do not imply deliverability. It also flags that values are returned unmasked and empty fields omitted, which is operationally important.

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?

Bracketed section headers keep it front-loaded and scannable despite its length, and each block maps to a decision the agent must make. There is minor repetition (the AliExpress 159831080 default appears twice; read-only is restated in [Side effects] after being established earlier).

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?

Complete for a tool with an output schema, annotations, and two parameters: it covers scope, exclusions, the semantics of the three result buckets, side effects, confirmation, and next steps on both error and unevaluated outcomes. What remains (exact response shape) is already carried by the output schema.

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 coverage is 100%, so both parameters are already documented, but the description reinforces where to copy dsers_order_id from and explains that supplier_platform_id selects which supplier's rule set is loaded, with omit/empty/0 defaulting to AliExpress 159831080. That is slightly redundant with the schema text, so it adds value in framing rather than new syntax.

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 and resource: a read-only check of one order's saved shipping address against required-field, length, and format rules. It immediately draws the boundary that matters ('never accepts or saves candidate address fields'), which separates it from address-writing paths such as update_order_information.

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 use] and [When not to use] sections name both the positive trigger (inspect saved address, investigate a rule failure) and the exclusions (cannot validate an unsaved candidate, cannot confirm postal deliverability). It also names the concrete alternative for the change case: update_order_information.

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.