delete_build
Remove a specific build from Komodo infrastructure by providing its build ID.
Instructions
Elimina un build de Komodo
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| build_id | Yes | ID del build a eliminar |
Remove a specific build from Komodo infrastructure by providing its build ID.
Elimina un build de Komodo
| Name | Required | Description | Default |
|---|---|---|---|
| build_id | Yes | ID del build a eliminar |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Implies destructive action but does not disclose reversibility, impact on associated data, or authentication needs. With no annotations, the description provides minimal behavioral insight beyond the obvious.
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?
Single sentence with no fluff. However, it could be slightly more structured to include return or error info.
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?
Lacks details on return values, error handling, or what happens after deletion. With no output schema, the description should fill this gap but does not.
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 description for build_id. The tool description adds no extra meaning beyond what the schema already provides, so baseline 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 description 'Elimina un build de Komodo' clearly states the action (delete) and the resource (a Komodo build). It distinguishes from siblings like create_build, update_build, and cancel_build.
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 versus alternatives like cancel_build. Does not mention prerequisites, side effects, or when deletion is appropriate.
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/Nonetss/komodo-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server