delete_module
Delete one or more reusable modules by module_uuid.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| module_uuids | Yes | ||
| organization_uuid | Yes |
Air Pipe
by io.airpipe
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- First observed
TDQS
B3/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations exist, so description carries full burden. Fails to disclose irreversibility, permission requirements, or cascading effects. 'Delete' alone does not provide sufficient behavioral context for a destructive operation.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness3/5
Is the description appropriately sized, front-loaded, and free of redundancy?
Single sentence is concise but under-specified for a deletion tool. Lacks important details like irreversibility or confirmation, making it less effective despite brevity.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness1/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With two required params, no output schema, and no annotations, the description should cover return values, error handling, and destructive nature. It provides no such context, leaving agents underinformed about consequences.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters2/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 0%; description only mentions 'by module_uuid' without explaining parameters further. Does not clarify that module_uuids expects an array or that organization_uuid is required, offering no added meaning over the schema.
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?
Clearly states the action ('Delete'), resource ('reusable modules'), and method ('by module_uuid'). Distinguishes from siblings like create_module, update_module, get_module.
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?
No explicit guidance on when to use vs. alternatives (e.g., undeploy_module). Implied usage for permanent removal, but no exclusions or context provided.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Try in Browser
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
B3.3/5.0
Disambiguation5/5
Each tool targets a distinct resource (config or module) and action (create, read, update, delete, deploy, etc.), with clear descriptions that avoid overlap. No two tools appear to perform the same function.
Naming Consistency5/5
All tool names follow a consistent verb_noun pattern in snake_case (e.g., create_config, list_modules), with occasional specificity like deploy_config_revision. No mixing of conventions or unexpected naming.
Tool Count4/5
At 19 tools, the count is slightly above the typical 3-15 range but still well-scoped for a configuration management server covering CRUD, deployment, revision history, validation, and planning. Each tool earns its place.
Completeness4/5
The tool surface covers the full lifecycle of configurations and modules (create, read, update, delete, deploy, undeploy, toggle, validate, plan, edit). Minor gaps like bulk operations or search are absent but not critical for the domain.