ActionShip by Teapplix Demo

Submit Order to 3PL

teapplix_submit_3pl

Submit an order to a 3PL (third-party logistics) vendor for fulfillment. Handles both unshipped orders (submit path) and already-shipped orders (review path, when a tracking number exists). Status is one of: Accepted, Declined, NotFound. Use teapplix_get_ship_methods with Carrier=<3PLType> to discover valid ShipMethod values for the vendor. [DEMO]

Input Schema

TableJSON Schema

Name	Required	Description
`TxnId`	Yes	Teapplix order ID to submit to the 3PL.
`3PLKey`	No	If you linked more than one account with the same 3PLType, 3PLKey uniquely identifies the account.
`Weight`	No	Total weight of the order items. Optional; many 3PLs will compute this themselves based on item info in the order.
`3PLType`	Yes	3PL vendor type (e.g. "lingxingwms", "eccangwms"). The value of this is typcally provided from request context.
`ShipMethod`	No	3PL service code or ship method requested. May be required for certain 3PLs; for others it may be computed based on other parameters.
`3PLWarehouseCode`	No	For most 3PLs, an id indicating requested warehouse facility to ship the order out of. For 3PLType="teapplix" this is the receiver_account_name.

Output Schema

TableJSON Schema

Name	Required	Description
`TxnId`	No	Original Teapplix TxnId
`Status`	No	Accepted vs Declined
`Message`	No
`Success`	No	true for success, false for failure
`DropshipTxnId`	No	3PL assigned order id. This is saved internally also to Teapplix so you not have to remember them

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already indicate readOnlyHint=false and idempotentHint=false, signaling a non-read-only, non-idempotent operation. The description adds behavioral insight by explaining the dual-path (submit/review) behavior and the possible status outcomes (Accepted, Declined, NotFound). It does not contradict annotations and provides context beyond the structured flags.

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 three sentences, all informative and free of fluff. It front-loads the main action, then adds relevant details about paths, status, and parameter discovery. The [DEMO] tag is minor noise but does not detract from conciseness.

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?

Given the tool's complexity (6 params, nested object, multiple paths), the description covers key aspects: the purpose, the two modes, status values, and a useful parameter tip. The existence of an output schema and full schema descriptions reduces the need to detail return values. It could have elaborated more on account prerequisites or the submit/review difference, but it is sufficiently complete for an agent to use.

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 baseline is 3. The description adds valuable guidance for the ShipMethod parameter by advising the use of teapplix_get_ship_methods with Carrier=<3PLType> to discover valid values. This goes beyond the schema's generic description, enhancing semantic understanding.

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 clearly states the tool's function: 'Submit an order to a 3PL vendor for fulfillment.' It uses a specific verb ('Submit') and resource ('order to 3PL'), and differentiates from siblings by focusing on 3PL submission. It also specifies handling of both unshipped and already-shipped orders, adding clarity.

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?

The description provides clear context for when to use the tool: for submitting orders to a 3PL, including the submit path for unshipped and review path for already-shipped orders. It also gives a practical tip to use teapplix_get_ship_methods to discover valid ShipMethod values. However, it does not explicitly contrast with sibling tools or state when not to use it, which would have pushed it to 5.

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?