Skip to main content
Glama
trhonpavel

medusa-mcp

by trhonpavel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Inventory levels

list_inventory
Read-only

Retrieve inventory items with stocked, reserved, and available stock per location. Filter by SKU, search, location, or low-stock threshold to find items at or below a set limit.

Instructions

Inventory items with stock per location (stocked, reserved, available). With low_stock_threshold returns only items at or below the threshold.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qNoFull-text search – title, SKU
skuNoExact SKU
limitNoNumber of records (max 200)
offsetNoRecords to skip (pagination)
location_idNoOnly this stock location
low_stock_thresholdNoOnly return items whose available quantity is less than or equal to this value

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds useful behavioral detail by enumerating the returned quantity fields (stocked, reserved, available) and clarifying that the threshold filters rather than sorts, but says nothing about pagination defaults or result limits beyond what the schema states.

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 tight sentences, front-loaded with what the tool returns before the optional filter modifier. No filler or repetition.

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 read-only list tool with no output schema and fully documented parameters, this covers what an agent needs: the payload shape and the one non-obvious filter. Missing only pagination/ordering guidance, which the schema partially implies via limit/offset.

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 all six parameters are already documented, including that low_stock_threshold compares against available quantity — which the description simply restates. Baseline 3 for high coverage with no meaningful added meaning.

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 names the resource (inventory items with per-location stocked/reserved/available quantities) and a filtering behavior, so an agent knows exactly what data comes back. It stops short of an explicit 'list' verb and never distinguishes itself from list_products, a close sibling in the same catalog.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no statement of when to use this tool versus list_products or get_product, and no prerequisites or exclusions. The only usage signal is implicit in the low_stock_threshold sentence.

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

Deploy Server

Other Tools