Skip to main content
Glama

list_inventories

List inventory check documents with filters for status, warehouse, date range, and SKU. Supports pagination to view matched, discrepancy, excess, or shortage results.

Instructions

List inventory check (kiểm kho) documents. Paginated.

IMPORTANT for AI:

  • Status: 1=pending, 10=awaiting confirmation, 200=completed

  • Done status: 1=matched, 2=discrepancy, 3=excess, 4=shortage

  • Use date filters + warehouse_id to narrow results.

  • Include: location,confirmer,creator,processer,sku

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qNoSearch by inventory code
warehouse_idNoFilter by warehouse
statusNo1=pending, 10=awaiting confirmation, 200=completed
done_statusNo1=matched, 2=discrepancy, 3=excess, 4=shortage
sku_skuNoFilter by SKU
includeNoRelations: location,confirmer,creator,processer,sku
start_create_dateNoCreation date start (YYYY-MM-DD)
end_create_dateNoCreation date end (YYYY-MM-DD)
start_done_dateNoCompletion date start (YYYY-MM-DD)
end_done_dateNoCompletion date end (YYYY-MM-DD)
sortNoSort order (default id:-1)id:-1
limitNoPage size
pageNoPage number

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

No annotations are provided, so the description carries the burden. It discloses pagination and key parameters, and explains status and done_status meaning. It does not explicitly state read-only behavior, but 'list' implies it. No contradictions.

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 extremely concise: two lines of purpose plus a bulleted list of key points. It is front-loaded with the main action and every sentence serves a purpose. No wasted words.

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 13 parameters and presence of an output schema, the description covers the essential patterns: pagination, filter advice, and relation includes. It does not explain the output format, but that is handled by the output schema. Sufficient for the tool's complexity.

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 100%, so baseline is 3. The description adds value by emphasizing which filters are most effective (date + warehouse_id) and listing recommended include relations, providing strategic guidance beyond the schema.

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 clearly states the tool lists inventory check documents and is paginated. However, there is a sibling tool 'search_all_inventories' with similar purpose, and this description does not differentiate when to use one over the other.

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 provides explicit notes on status codes, done_status codes, and recommends using date filters and warehouse_id to narrow results. It lacks explicit guidance on when not to use the tool or when to use alternatives (e.g., search_all_inventories), but the given instructions are practical.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Winter279/gobox-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server