Simple Inventory Management

restore_inventory_item

Restores a deleted inventory item by Id (see list_deleted_inventory_items), with its counts, units, custom field values and history. Order lines and assembly parts removed by the delete are not restored. Returns the restored item.

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": {
      "inventoryItemId": "<inventoryItemId>"
    },
    "name": "restore_inventory_item"
  }
}

Input Schema

Name	Required	Description	Default
`inventoryItemId`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 7, 2026

TDQS

A4.4/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 that counts, units, custom field values, and history are restored, while order lines and assembly parts removed by the delete are not restored. It also states the return value. It omits permission requirements and error behavior, which are secondary but relevant.

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 two compact sentences, front-loaded with the action and resource. Every sentence adds material information about scope, restoration behavior, and return value.

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 simple one-parameter restore operation with no output schema, the description covers the core action, what is restored, what is not restored, and the return value. It could be slightly more complete by addressing permission or failure conditions, but it is sufficient for correct invocation.

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 description coverage is 0%, so the description must compensate. It identifies the parameter as an Id and directs the agent to list_deleted_inventory_items to find it, adding useful meaning beyond the bare integer schema, though it does not clarify type or formatting explicitly.

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 states a specific verb and resource: restores a deleted inventory item by Id. It distinguishes the tool from siblings like delete_inventory_item and list_deleted_inventory_items, so an agent can identify its role without opening the schema.

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 points the agent to list_deleted_inventory_items for obtaining the required Id, giving clear context for use. It does not explicitly state when not to use the tool or describe prerequisite states such as whether the item must still be deleted, but the intended usage is clear.

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?