Skip to main content
Glama

ActionShip by Teapplix Demo

by com.teapplix.api

Set Order Shipping Options

teapplix_set_order_ship_options
Idempotent

Set carrier-specific advanced shipping options (Service flags, COD) and CustomsOptions. For the common sparse options — InsuranceType and Delivery.Signature / Delivery.Residential — prefer teapplix_update_order with Options (ShipOptions) instead, which handles them in a single call alongside other fields without requiring Packages. Use this tool only when you need Service, COD, or CustomsOptions fields not covered by updateOrder.Options. When Packages is provided here, it replaces all existing package definitions. [DEMO]

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
TxnIdYesTeapplix order ID to modify.
OptionsNoAdvanced shipping options applied to all packages: InsuranceType, Delivery (Signature, Residential, etc.), Service, Cod, etc.
PackagesNoPackage definitions required when setting Options or CustomsOptions (to specify carrier method context). If provided, ALL existing package definitions for the order are replaced. First entry is the main package; additional entries are extra packages. To update ship method / weight / dimensions without advanced options, use teapplix.updateOrder with ShippingDetails (OrderShipment) instead.
CustomsOptionsNoCustoms options for international shipments (e.g. ReasonForExport).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
OrdersResultNo

TDQS

A4.9/5.0
Behavior5/5

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

Annotations indicate idempotent and non-destructive behavior, but the description adds critical context by disclosing that providing Packages replaces all existing package definitions. This is valuable behavioral information beyond what annotations convey, and it does not contradict them.

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 concise (4 sentences), front-loaded with purpose, and every sentence serves a distinct function: purpose, alternative guidance, restrictive use case, and a caveat. No unnecessary repetition or fluff.

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 tool's complexity (nested objects, multiple advanced options) and rich schema, the description adequately covers what it does, when to use it, and a key behavioral caveat. The output schema handles return-value documentation, so no further explanation is needed.

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% with detailed descriptions, so the baseline is 3. The description adds value by explaining when Packages is required (for setting Options or CustomsOptions) and clarifying its replacement semantics, which enriches understanding beyond the schema alone.

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 purpose: 'Set carrier-specific advanced shipping options (Service flags, COD) and CustomsOptions.' It distinguishes from sibling teapplix_update_order by explicitly naming when to use which tool, making its role unique.

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?

The description provides explicit usage guidance: prefer teapplix_update_order for common sparse options, and use this tool only when Service, COD, or CustomsOptions fields are needed. It also warns about Packages replacing existing definitions, giving clear when-to-use and when-not-to-use context.

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 toolsInspect
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