removeStops a running deploy, deletes its record and logs, and removes the associated Cloudflare worker.
Stop (if running) and delete the deploy record and logs. On the workers backend, also deletes the worker on Cloudflare.
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | Deploy name |
Changes observed during successful MCP inspections.
v0.5.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description adds valuable behavior beyond annotations: it mentions stopping the deploy if running, deleting logs, and the Cloudflare worker deletion. This goes beyond the destructiveHint flag and provides concrete side effects. No contradiction with annotations.
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?
The description is extremely concise—two sentences that front-load the primary action and then add a specific backend nuance. No wasted words, every sentence adds value.
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?
For a simple one-parameter destructive tool with no output schema and annotations covering safety, the description covers all necessary aspects: what is deleted, the conditional stop, and the backend-specific behavior. Nothing essential is missing.
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?
The schema already fully covers the single parameter 'name' with description 'Deploy name' (100% coverage). The description adds no additional detail about the parameter's format, constraints, or semantics beyond what the schema provides. Baseline 3 is appropriate.
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 clearly states the action: 'Stop (if running) and delete the deploy record and logs.' It also adds the specific Cloudflare worker deletion for the workers backend. This distinguishes it from sibling tools like 'stop' (which only stops) and 'deploy' (which creates).
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?
The description implies this is for full removal, but it does not explicitly say when to use it versus alternatives like 'stop' or 'list'. It does not mention that it is destructive or that it should be used only when permanent deletion is intended. The destructive hint is in annotations, but the description itself lacks explicit usage guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.