Skip to main content
Glama
Sign In
nubiia-dev

MCP Holded

by nubiia-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

list_warehouses

Retrieve all warehouses from Holded in one call, with optional field filtering and summary-only count mode for smaller responses.

Instructions

List all warehouses (Holded API v2). All warehouses are returned in a single call (no cursor pagination). Supports field filtering and summary mode.

Input Schema

NameRequiredDescriptionDefault
fieldsNoProject only these fields per item (e.g. ["id", "name", "address"]). Reduces response size.
summaryNoReturn only total count without items (default: false)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv2.0.3
    • changedInput schema / properties / fields / description
      Previous value: -"Select specific fields to return (e.g., [\"id\", \"name\", \"address\"]). Reduces response size by 70-90%. If not provided, returns default fields: id, name, address"New value: +"Project only these fields per item (e.g. [\"id\", \"name\", \"address\"]). Reduces response size."
    • removedInput schema / properties / page
      Removed value: -{
-  "description": "Page number (starting from 1, default: 1)",
-  "type": "number"
-}
    • removedInput schema / properties / pageSize
      Removed value: -{
-  "description": "Number of items per page (default: 50, max: 500)",
-  "type": "number"
-}
    • changedInput schema / properties / summary / description
      Previous value: -"Return only total count and page count without items (default: false)"New value: +"Return only total count without items (default: false)"
  2. First observedv1.6.0

TDQS

A3.6/5.0
Behavior3/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 does disclose a genuinely useful behavioral trait — the response is complete with no cursor pagination — but says nothing about permissions, rate limits, or the fact that this is a safe read operation beyond the implied 'List'.

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?

Three short sentences, front-loaded with the resource and the most decision-relevant fact (no pagination), then the optional modifiers. No filler or restated boilerplate.

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 zero-required-param read tool with full schema coverage and no output schema, the definition covers scope and response-size behavior adequately. The only real gap is an explicit steer away from the warehouse-stock sibling and a hint about response shape.

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 both optional params already carry their own descriptions and examples. The description only restates 'field filtering and summary mode' at a high level, adding no syntax, defaults, or interaction details beyond the schema; baseline 3 applies.

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?

States a specific verb and resource ('List all warehouses') plus the API version, which is enough to separate it from get_warehouse/create_warehouse/update_warehouse. It does not explicitly distinguish itself from the nearby 'list_warehouse_stock' sibling, which also lists warehouse-related data, so it falls short of a 5.

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?

Usage is implied rather than stated: the 'summary mode' and 'field filtering' mentions hint at when to reach for those options, but there is no explicit when-to-use, no exclusion, and no named alternative (e.g. 'for stock levels per warehouse use list_warehouse_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