Skip to main content
Glama

get_warehouses

Retrieve all configured warehouse locations for inventory management in Siigo. Use warehouse IDs when creating products or invoices to track inventory accurately.

Instructions

Get all configured warehouses/locations.

Returns a list of warehouses for inventory management. Use warehouse IDs when creating products or invoices with inventory.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The @mcp.tool decorated handler function that fetches all configured warehouses from the Siigo API using get_client(ctx).get('/warehouses'). No input parameters required.
    @mcp.tool
    async def get_warehouses(ctx: Context) -> list[dict[str, Any]]:
        """Get all configured warehouses/locations.
    
        Returns a list of warehouses for inventory management.
        Use warehouse IDs when creating products or invoices with inventory.
        """
        return await get_client(ctx).get("/warehouses")
  • Registration mapping in the lazy-loading tool functions dictionary, linking 'get_warehouses' to the reference.get_warehouses function.
    "get_warehouses": reference.get_warehouses,
  • Tool index entry in TOOL_INDEX list for discovery tools (list_siigo_tools), providing name, category, and summary for get_warehouses.
    {"name": "get_warehouses", "category": "reference", "summary": "Get all warehouse locations"},
  • Import statement that brings in the reference module containing the get_warehouses handler, used in lazy loading.
    from siigo_mcp.tools import reference, customers, products, invoices, credit_notes, journals
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It mentions that the tool 'Returns a list of warehouses for inventory management,' which gives basic behavioral context about the output. However, it lacks details on potential limitations (e.g., pagination, rate limits, or authentication needs), leaving some gaps in transparency for a tool with no annotation support.

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 highly concise and well-structured with three sentences that each serve a clear purpose: stating the action, describing the return value, and providing usage guidance. There is no wasted text, and it is front-loaded with the core functionality.

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 tool has 0 parameters, 100% schema coverage, and an output schema exists, the description is mostly complete. It explains what the tool does and how to use the results. However, with no annotations, it could benefit from more behavioral details (e.g., error handling or data freshness), slightly reducing completeness.

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?

The input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description adds value by explaining the purpose of the output ('warehouse IDs when creating products or invoices'), which goes beyond the schema. This earns a baseline 4 since it compensates with useful semantic context despite the lack of parameters.

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 clearly states the tool's purpose with specific verbs ('Get all configured warehouses/locations') and distinguishes it from siblings by focusing on warehouses for inventory management. It explicitly mentions the resource (warehouses/locations) and the action (get all configured ones), making it distinct from other get/list tools in the sibling set.

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

Usage Guidelines5/5

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

The description provides explicit usage guidance by stating 'Use warehouse IDs when creating products or invoices with inventory,' which tells the agent when to use this tool (to obtain IDs needed for other operations) and implies it's a prerequisite for those actions. This is clear and actionable without needing to list exclusions.

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/dsfaccini/siigo-mcp'

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