Skip to main content
Glama
Sign In

ActionShip by Teapplix Demo

by com.teapplix.api
OverviewDiscussionsAdmin

Manage Order Queues

teapplix_manage_queue

Create, update, or delete order queues, dispatched by Operation (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. Use teapplix_get_queues to list existing queues. [DEMO]

Input Schema

NameRequiredDescriptionDefault
QueueIdNoQueue ID. Optional explicit ID on create (1-4 reserved); identifier (update/delete).
OperationYescreate: 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).
ProfileIdNoShipping profile assignment (FK to /ShippingProfile). Applies to create/update.
QueueNameNoQueue name. Required unique name (create); identifier or new name (update); identifier (delete).
QueueTypeNoQueue behavior type. AGENT queues are processed by an AI agent using AgentInstructions. Defaults to DISPLAY. Applies to create/update.
ProfileNameNoShipping profile name — alternative to ProfileId. Applies to create/update.
WarehouseIdNoWarehouse assignment (FK to /Warehouse). Applies to create/update.
WarehouseNameNoWarehouse name — alternative to WarehouseId. Applies to create/update.
AgentInstructionsNoMarkdown instructions for the AI agent. Only applicable when QueueType is AGENT. Applies to create/update.

Output Schema

NameRequiredDescriptionDefault
QueuesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changed
    • changedInput schema / properties / Operation / description
      Previous value: -"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)."New value: +"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)."
    • changedInput schema / properties / Operation / enum
      Previous value: -[
-  "get",
-  "create",
-  "update",
-  "delete"
-]New value: +[
+  "create",
+  "update",
+  "delete"
+]
    • changedInput schema / properties / ProfileId / description
      Previous value: -"Shipping profile assignment (FK to /ShippingProfile). Applies to get/create/update."New value: +"Shipping profile assignment (FK to /ShippingProfile). Applies to create/update."
    • changedInput schema / properties / ProfileName / description
      Previous value: -"Shipping profile name — alternative to ProfileId. Applies to get/create/update."New value: +"Shipping profile name — alternative to ProfileId. Applies to create/update."
    • changedInput schema / properties / QueueId / description
      Previous value: -"Queue ID. Filter (get); optional explicit ID on create (1-4 reserved); identifier (update/delete)."New value: +"Queue ID. Optional explicit ID on create (1-4 reserved); identifier (update/delete)."
    • changedInput schema / properties / QueueName / description
      Previous value: -"Queue name. Substring filter (get); required unique name (create); identifier or new name (update); identifier (delete)."New value: +"Queue name. Required unique name (create); identifier or new name (update); identifier (delete)."
    • changedInput schema / properties / WarehouseId / description
      Previous value: -"Warehouse assignment (FK to /Warehouse). Applies to get/create/update."New value: +"Warehouse assignment (FK to /Warehouse). Applies to create/update."
    • changedInput schema / properties / WarehouseName / description
      Previous value: -"Warehouse name — alternative to WarehouseId. Applies to get/create/update."New value: +"Warehouse name — alternative to WarehouseId. Applies to create/update."
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Beyond the annotations it discloses the meaningful consequences: which queues are undeletable, that AGENT-type queues are driven by Markdown AgentInstructions, and the default QueueType of DISPLAY. There is mild tension with destructiveHint=false since deletion is supported, but the description compensates by spelling out exactly when deletion is blocked, so an agent is not misled about risk.

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?

Four tight sentences front-loaded with the operation dispatch and ending with the sibling pointer and demo tag. No filler, though the '[DEMO]' marker is noise for invocation decisions.

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 an output schema, full annotations, and 100% schema coverage, the description supplies the missing operational context: dispatch semantics, AGENT-queue behavior, and delete preconditions. Only the not-found/name-collision handling on update is unaddressed.

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?

Schema description coverage is 100%, so parameter meaning is already fully documented per-field. The description restates a few key points (QueueType=AGENT pairing with AgentInstructions, built-in QueueId range) but adds no format/syntax detail beyond the schema; baseline 3 is appropriate when the schema does the heavy lifting.

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 set and resource ('Create, update, or delete order queues') and explains the dispatch mechanism via Operation. It also states what a queue is conceptually (grouping orders by warehouse and shipping profile), which separates it cleanly from sibling tools like teapplix_get_queues or teapplix_manage_warehouse.

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 names the read counterpart explicitly ('Use teapplix_get_queues to list existing queues') and gives hard preconditions for delete (built-in queues 1-4 and queues with active orders cannot be deleted). It stops short of saying when to choose update vs create for an existing queue, or what to do when a QueueName collides, so it is clear but not fully exhaustive.

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
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources