ActionShip by Teapplix Demo

Manage Order Queues

teapplix_manage_queue

Create, read, update, or delete order queues, dispatched by Operation (get/create/update/delete). Queues group orders by warehouse and shipping profile. Use QueueType=AGENT with AgentInstructions (Markdown) to create an AI-managed queue. Built-in queues (QueueId 1-4) and queues with active orders cannot be deleted. [DEMO]

Input Schema

TableJSON Schema

Name	Required	Description
`QueueId`	No	Queue ID. Filter (get); optional explicit ID on create (1-4 reserved); identifier (update/delete).
`Operation`	Yes	get: list/filter queues. create: new queue (QueueName required). update: modify queue (QueueId or QueueName required). delete: remove queue (QueueId or QueueName required; built-in queues 1-4 and queues with active orders cannot be deleted).
`ProfileId`	No	Shipping profile assignment (FK to /ShippingProfile). Applies to get/create/update.
`QueueName`	No	Queue name. Substring filter (get); required unique name (create); identifier or new name (update); identifier (delete).
`QueueType`	No	Queue behavior type. AGENT queues are processed by an AI agent using AgentInstructions. Defaults to DISPLAY. Applies to create/update.
`ProfileName`	No	Shipping profile name — alternative to ProfileId. Applies to get/create/update.
`WarehouseId`	No	Warehouse assignment (FK to /Warehouse). Applies to get/create/update.
`WarehouseName`	No	Warehouse name — alternative to WarehouseId. Applies to get/create/update.
`AgentInstructions`	No	Markdown instructions for the AI agent. Only applicable when QueueType is AGENT. Applies to create/update.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`Queues`	No

TDQS

A3.8/5.0

Behavior1/5

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

The description discloses multiple behavioral traits, including operation dispatch, grouping logic, AI-managed queue configuration, and deletion restrictions. However, it contradicts the annotations: destructiveHint=false conflicts with the ability to delete queues, which is a destructive operation. This contradiction reduces transparency score to 1.

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, with three sentences covering purpose, grouping, special case, and constraints. No redundant information; front-loaded with the core CRUD action.

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 multi-action CRUD tool with 9 parameters and an output schema, the description covers the key operational aspects and important constraints. However, it omits details like default QueueType behavior and update semantics, but these are available in the schema. The contradiction with annotations slightly reduces completeness, but overall it is adequate.

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 covers all 9 parameters with detailed descriptions, providing a baseline of 3. The description adds value by highlighting the AGENT QueueType with AgentInstructions and the deletion restrictions for built-in queues, which helps in parameter selection. It also clarifies the Operation dispatch mechanism.

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 with specific verbs 'Create, read, update, or delete' and identifies the resource as 'order queues'. It also provides distinguishing context about grouping by warehouse/shipping profile and AI-managed queues, separating it from sibling management tools.

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 implies the tool is for queue management but does not explicitly state when to use it over alternatives or provide exclusions. However, given the clear resource (order queues) and distinct siblings, the usage context is unambiguous. It does note important constraints (deletion limitations) that guide usage.

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?