Skip to main content
Glama
Sign In

ActionShip by Teapplix Demo

by com.teapplix.api
OverviewDiscussionsAdmin

Manage Warehouses

teapplix_manage_warehouse

Create, update, or delete warehouses, dispatched by Operation (create/update/delete). WarehouseId 1 (default) cannot be deleted; warehouses with active orders, channel mappings, or listings cannot be deleted. Use teapplix_get_warehouses to list existing warehouses. [DEMO]

Input Schema

NameRequiredDescriptionDefault
3PLKeyNoIdentifies which account when you have multiple accounts at the same 3PL. Leave blank if you only have one account per 3PL.
OperationYescreate: new warehouse (WarehouseType and WarehouseName required). update: modify warehouse (WarehouseId or WarehouseName required). delete: remove warehouse (WarehouseId or WarehouseName required).
CountryCodeNoISO country code for the 3PL warehouse location. Applies to create/update.
WarehouseIdNoUnique warehouse identifier. For create: omit to auto-assign. For update/delete: identifies the warehouse. WarehouseId 1 is the default warehouse and cannot be deleted.
WarehouseNameNoWarehouse display name. Must be unique across all warehouses. Required on create. For update/delete: exact-match identifier (alternative to WarehouseId).
WarehouseTypeNoType of warehouse. Required on create. GENERIC: your own warehouse, inventory tracked in Teapplix. QB: inventory tracked in QuickBooks. RECONCILE: virtual warehouse to compare quantities against a 3rd-party report. DROPSHIP/DROPSHIP-T: dropship warehouses. FBA: Amazon Fulfillment. 3PL types (e.g. ECCANGWMS): third-party warehouses that manage your inventory. For 3PL and FBA types, WarehouseType cannot be changed after creation.
3PLWarehouseCodeNoIdentifies a specific warehouse facility at the 3PL. Required on create for 3PL types. Links this warehouse entry to a facility for inventory tracking and order fulfillment.
QuantityAlgorithmNoInventory quantity calculation method. CALCULATED: from credits/debits plus order activity (each inbound order debits inventory). STATIC: from credits/debits only, without order activity. FIXED: always shows a fixed quantity. Applicable to GENERIC and RECONCILE warehouse types only; ignored for externally managed warehouses.
ReconcileForWarehouseIdNoOnly for WarehouseType RECONCILE. The existing warehouse with this ID will have its paired reconcile warehouse set to the newly created warehouse.

Output Schema

NameRequiredDescriptionDefault
WarehousesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedInput schema / properties / Operation / description
      Previous value: -"get: list/filter warehouses. create: new warehouse (WarehouseType and WarehouseName required). update: modify warehouse (WarehouseId or WarehouseName required). delete: remove warehouse (WarehouseId or WarehouseName required)."New value: +"create: new warehouse (WarehouseType and WarehouseName required). update: modify warehouse (WarehouseId or WarehouseName required). delete: remove warehouse (WarehouseId or WarehouseName required)."
    • changedInput schema / properties / Operation / enum
      Previous value: -[
-  "get",
-  "create",
-  "update",
-  "delete"
-]New value: +[
+  "create",
+  "update",
+  "delete"
+]
    • changedInput schema / properties / WarehouseId / description
      Previous value: -"Unique warehouse identifier. For get: exact match filter. For create: omit to auto-assign. For update/delete: identifies the warehouse. WarehouseId 1 is the default warehouse and cannot be deleted."New value: +"Unique warehouse identifier. For create: omit to auto-assign. For update/delete: identifies the warehouse. WarehouseId 1 is the default warehouse and cannot be deleted."
    • changedInput schema / properties / WarehouseName / description
      Previous value: -"Warehouse display name. Must be unique across all warehouses. For get: case-insensitive substring filter. Required on create. For update/delete: exact-match identifier (alternative to WarehouseId)."New value: +"Warehouse display name. Must be unique across all warehouses. Required on create. For update/delete: exact-match identifier (alternative to WarehouseId)."
  2. First observed

TDQS

A3.5/5.0
Behavior1/5

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

The description explicitly advertises deletion ('delete warehouses', 'cannot be deleted') while the annotations declare destructiveHint=false, which per MCP semantics means non-destructive/additive only. An agent trusting the annotation could invoke a delete without confirmation. The description does add useful constraint context, but the direct conflict with the annotation is disqualifying.

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?

Three tight sentences: operation dispatch first, then deletion constraints, then the listing alternative. No filler, though the trailing '[DEMO]' marker is noise.

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?

An output schema exists, so return values need no explanation, and the schema carries all parameter detail. The description covers the mutation scope and the key guardrails; only confirmation/permission expectations for destructive operations are missing.

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 Operation, WarehouseType, WarehouseId, and the 3PL fields are already fully documented in structured form. The description only restates the Operation dispatch and the WarehouseId 1 restriction, adding nothing beyond the schema.

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?

States a specific verb set and resource ('Create, update, or delete warehouses') and immediately explains the dispatch mechanism (Operation). It is clearly distinguished from the read-only sibling teapplix_get_warehouses, which it names explicitly.

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?

Explicitly routes listing to teapplix_get_warehouses and states the two deletion preconditions (WarehouseId 1 is undeletable; warehouses with active orders, channel mappings, or listings cannot be deleted). It does not explain when to prefer create vs update vs delete, though the schema's Operation enum covers that.

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