Skip to main content
Glama

ActionShip by Teapplix Demo

by com.teapplix.api

Manage Warehouses

teapplix_manage_warehouse

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
3PLKeyNoIdentifies which account when you have multiple accounts at the same 3PL. Leave blank if you only have one account per 3PL.
OperationYesget: list/filter warehouses. create: 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 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.
WarehouseNameNoWarehouse 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).
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

TableJSON Schema
NameRequiredDescriptionDefault
WarehousesNo

TDQS

A4.2/5.0
Behavior4/5

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

Annotations carry no safety hints (all false), so the description is the primary source of behavioral disclosure. It adds valuable restrictions on deletion (WarehouseId 1 and warehouses with active dependencies cannot be deleted), which go beyond the schema's mention of WarehouseId 1. However, it doesn't describe side effects of create/update or error conditions.

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?

Two sentences, front-loaded with the primary verb phrase and resource. Every clause adds value (CRUD scope, dispatch method, deletion constraints, demo context). No redundancy or filler.

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 (9 parameters, CRUD operations, type-specific behavior) and the presence of a rich schema and output schema, the description provides sufficient high-level guidance. It could mention the need for required fields on create, but the schema already covers that, so overall completeness is strong.

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?

The input schema provides detailed descriptions for every parameter (100% coverage), including enums and per-operation behavior. The description adds only high-level operational context (e.g., Operation dispatch) and the delete constraint, which maps to existing parameter descriptions. Thus, the description adds marginal value 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?

The description clearly states the tool's CRUD scope ('Create, read, update, or delete warehouses') and identifies the dispatch mechanism via Operation. It distinguishes itself from sibling tools by naming the 'warehouses' resource, which no other sibling tools mention.

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 implicitly communicates when to use this tool (when managing warehouses) and provides specific usage constraints for delete operations. It doesn't explicitly name alternatives or exclusions, but since no sibling tool overlaps with warehouse management, the guidance is adequate.

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