delete_warehouse
Remove a warehouse from your Holded account by specifying its unique ID.
Instructions
Delete a warehouse
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| warehouseId | Yes | Warehouse ID to delete |
Remove a warehouse from your Holded account by specifying its unique ID.
Delete a warehouse
| Name | Required | Description | Default |
|---|---|---|---|
| warehouseId | Yes | Warehouse ID to delete |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description must disclose behavioral traits. It only says 'Delete', which implies destruction, but fails to mention whether deletion is irreversible, requires permissions, or affects related data.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Extremely concise but under-informative. A single sentence without elaboration on usage or behavior is under-specification, not effective conciseness.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the destructive nature of the tool, the description lacks essential context like irreversibility, confirmation steps, or permission requirements. No output schema or annotations to supplement.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% with a clear parameter description. The tool description adds no additional meaning beyond the schema, earning a baseline score of 3.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The verb 'Delete' and resource 'warehouse' clearly state the action and target, distinguishing it from non-delete siblings like 'create_warehouse' and 'get_warehouse', but does not differentiate from other delete tools like 'delete_contact'.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance on when to use this tool vs alternatives. No indications of prerequisites, consequences, or what makes this tool appropriate over other delete tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/nubiia-dev/mcp-holded'
If you have feedback or need assistance with the MCP directory API, please join our Discord server