ActionShip by Teapplix Demo

Validate Shipping Address

teapplix_validate_address

Read-only

Validate and normalize a US shipping address against a carrier's validation engine. Only US addresses (CountryCode=US) are supported — non-US addresses return an error. Branch on Status: "Validated Changed" → engine corrected one or more fields, diff Address vs. input and update the record; "Validated Not Changed" → address is already valid, no action needed; "Not Changed" → engine rejected the address, surface Message to the user. [DEMO]

Input Schema

TableJSON Schema

Name	Required	Description	Default
`Address`	Yes	US address to validate. Supply at least Street, City, State, and ZipCode (or Street + ZipCode for ZIP-only normalization). Only US addresses (CountryCode=US) are supported.
`Provider`	No	Address validation engine. Defaults to TEAPPLIX (uses the account default, typically EasyPost). UPS and FEDEX route to that carrier's native validator — only specify these if the user explicitly requests carrier-specific validation and has that carrier account linked.	TEAPPLIX

Output Schema

TableJSON Schema

Name	Required	Description
`Status`	Yes	Validation result. Three known values: "Validated Changed" — address is valid but change is suggested; "Validated Not Changed" — address is valid no change needed; "Not Changed" — address is invalid impossible to fix.
`Address`	Yes	Input address, but if suggested change is given under Status="Validated Changed", certain fields in this object are modified based on carrier feedback.
`Message`	No	Detail message about address validation return.
`Residential`	No	True for residential delivery, false for commercial. Populated when the validating carrier reports it.
`DeliveryPoint`	No	USPS DPV postal-barcode delivery point digits, when available.

TDQS

A4.5/5.0

Behavior5/5

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

Annotations already mark readOnlyHint=true, and the description adds significant behavioral context beyond that: normalization behavior, US-only restriction with error result, and the exact meaning of each Status value ('Validated Changed' → corrected fields, 'Validated Not Changed' → no action, 'Not Changed' → rejected with Message). This is valuable operational detail.

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 compact but information-dense: first sentence states the core function, second states the constraint, third gives actionable status handling. Each sentence earns its place, and the structure is front-loaded. The trailing [DEMO] is minor but does not hurt.

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?

Given the output schema is present and annotations mark it read-only, the description covers the essential operational context: what the tool validates, the supported country restriction, and how to interpret the three statuses. Nothing critical is missing for an agent to invoke and process results.

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

Parameters3/5

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

The input schema has 100% description coverage with field-level explanations and the Provider enum is documented. The description does not add additional parameter meaning beyond behavioral flow, so baseline 3 is appropriate.

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 opens with a specific verb+resource: 'Validate and normalize a US shipping address against a carrier's validation engine.' It further distinguishes scope (US-only) and gives clear status branches, making it unambiguous what the tool does and how it differs from sibling tools around labels/orders.

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?

It gives clear context: only US addresses supported, non-US returns error, and it instructs how to branch on Status. It does not explicitly name alternatives or say when not to use it, but the context is sufficient for an agent to select it appropriately among the siblings.

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

All ActionShip by Teapplix Demo tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.9/5.0

Disambiguation4/5

Most tools have clearly distinct purposes (orders, labels, rates, zones, profiles). A few name pairs like manage_tag vs manage_order_tags and set_order_ship_options vs update_order could be confused, but the descriptions explicitly clarify when to use each.

Naming Consistency5/5

All tools share the teapplix_ prefix and follow a consistent verb_noun pattern (e.g., get_orders, create_order, purchase_label, validate_address). The only deviation is the bare 'help' tool, which is conventional and does not disrupt the pattern.

Tool Count4/5

At 28 tools, the server is slightly over the ideal 3-15 range, but the breadth of shipping operations (orders, labels, rates, manifests, tracking, configuration) justifies the count. It is not bloated.

Completeness5/5

The tool surface covers the full order-to-shipping lifecycle: order create/update/retrieve, splitting/merging, label purchase and cancellation, rate quotes, tracking, manifesting, address validation, 3PL submission, and configuration (profiles, warehouses, queues, tags). No significant gaps are apparent.

Resources

Need Help?