Skip to main content
Glama
Sign In
nubiia-dev

MCP Holded

by nubiia-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

list_warehouse_stock

Retrieve product stock levels for a specific Holded warehouse by ID, with cursor pagination, optional field filtering, and summary-only responses to reduce payload size.

Instructions

List all products stock in a specific warehouse (Holded API v2). Cursor-paginated: pass the previous response nextCursor as cursor. Server-paginated; use limit to control page size. Supports field filtering to reduce response size.

Input Schema

NameRequiredDescriptionDefault
limitNoMax items per page (server-paginated; use limit to control page size)
cursorNoCursor from a previous response nextCursor
fieldsNoProject only these fields per item (e.g. ["product_id", "stock"]). Reduces response size.
summaryNoReturn only count and pagination metadata without items (default: false)
warehouseIdYesWarehouse ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv2.0.3
    • addedInput schema / properties / cursor
      Added value: +{
+  "description": "Cursor from a previous response nextCursor",
+  "type": "string"
+}
    • changedInput schema / properties / fields / description
      Previous value: -"Select specific fields to return (e.g., [\"productId\", \"productName\", \"sku\", \"stock\"]). Reduces response size by 70-90%. If not provided, returns default fields: productId, productName, sku, stock"New value: +"Project only these fields per item (e.g. [\"product_id\", \"stock\"]). Reduces response size."
    • changedInput schema / properties / limit / description
      Previous value: -"Maximum number of items to return (default: 50, max: 500)"New value: +"Max items per page (server-paginated; use limit to control page size)"
    • removedInput schema / properties / page
      Removed value: -{
-  "description": "Page number for pagination (optional)",
-  "type": "number"
-}
  2. First observedv1.6.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden; it does disclose meaningful behavior (cursor pagination, server-side paging, field projection to shrink payloads). But it omits the read-only nature, permission/auth requirements, return item shape, and does not mention the 'summary' parameter that changes the response format.

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?

Four short sentences with the purpose front-loaded and no filler. There is mild redundancy between the pagination sentences and the schema wording, but nothing egregious.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a paginated list tool with no output schema and no annotations, the description should say more about what is returned and the summary mode. Pagination mechanics are well covered, but response content and the response-altering summary parameter are left undisclosed.

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 the baseline is 3, and the description largely restates what the schema already documents (cursor from nextCursor, limit for page size, fields filtering). It adds no syntax or format detail beyond the schema and never explains the summary flag.

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 and resource ('List all products stock in a specific warehouse') and scopes it via the required warehouseId. It is clearly distinct from siblings such as list_warehouses or update_product_stock, though it does not name an alternative explicitly.

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

Usage Guidelines3/5

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

It gives procedural guidance for iteration ('pass the previous response nextCursor as cursor') and page sizing, which tells the agent how to call it repeatedly. However, it offers no when-to-use/when-not guidance or comparison against related tools like list_warehouses or update_product_stock.

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