delete_alertAdmin or owner. The rule and its recorded firings go; notifications already in someone's inbox stay. Set enabled: false with update_alert instead if the intent is only to stop being told for now.
| Name | Required | Description | Default |
|---|---|---|---|
| alert_id | Yes | Which rule to delete. From list_alerts. |
| Name | Required | Description | Default |
|---|---|---|---|
| deleted | Yes |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Beyond the destructiveHint annotation, it discloses that recorded firings are deleted while already-delivered notifications remain, and warns about the alternative non-destructive action.
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 compact, front-loaded with permission and effect, and includes the alternative in a single additional sentence without unnecessary detail.
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 delete operation, the description covers permission, side effects, and the alternative action. No important context is missing given the output schema is not relevant to invocation.
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 documents alert_id as 'Which rule to delete. From list_alerts.' and the description adds no additional parameter-level detail beyond that.
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 tool deletes an alert and specifies the required admin or owner role. It distinguishes itself from update_alert by noting when to use that alternative.
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?
Explicitly instructs to use update_alert with enabled: false when the intent is only to stop notifications, providing clear decision guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.