Simple Inventory Management

create_order

Create a new order for the company. Use Type "Inbound" to restock items from a supplier (the default) or "Outbound" to ship items out. Supply a name and the line items to order (each line is an inventory item plus a count). Identify each line's item by inventoryItemId (from get_inventory) or by itemName. Items not listed are still added to the order with a count of zero, just like creating an order in the app. Setting a count increases the item's on-order amount (Inbound) or outbound amount (Outbound); finishing the delivery is done separately when the order is completed.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "order": "<order>"
    },
    "name": "create_order"
  }
}

Input Schema

Name	Required	Description	Default
`order`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 7, 2026

TDQS

A3.9/5.0

Behavior4/5

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

With no annotations supplied, the description carries the full behavioral burden and does well: it discloses the non-obvious side effect that unlisted items are still added with count zero, and that setting a count increments on-order (Inbound) or outbound (Outbound) amounts. It omits permissions/auth requirements, whether the call is idempotent, and what the response contains.

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?

Purpose and the type decision are front-loaded, and each sentence adds real information (type semantics, item identification, zero-count behavior, side effects). It runs slightly long with some app-comparison framing ("just like creating an order in the app") that could be trimmed.

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 nested-object mutation tool with no annotations and no output schema, the description covers the important semantics: order types, item identification strategy, zero-count inclusion, and on-order/outbound side effects. Gaps remain on the notes/supplier fields and on what the tool returns after creation.

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 0% for a nested object with five sub-fields, so the description must compensate. It explains name, type, and the items array well, including the itemName-vs-inventoryItemId choice and a pointer to get_inventory, but says nothing about notes or supplier, leaving two fields completely undocumented.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb+resource ("Create a new order for the company") and immediately disambiguates the two order types, Inbound vs Outbound, with their real-world meanings. It does not, however, distinguish this tool from the sibling generate_purchase_orders, which an agent could plausibly confuse it with.

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 gives explicit selection guidance for the type field ("Inbound" to restock from a supplier, the default, vs "Outbound" to ship items out) and clarifies a common misconception by stating that finishing the delivery is done separately when the order is completed. No exclusions or comparison against generate_purchase_orders are given.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Simple Inventory Management tools Inspect

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

Need Help?