Skip to main content
Glama
Sign In
Cloady

Cloady

Official
by Cloady
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Delete Alert

deleteAlert
Destructive

Deletes a specific alert by ID from a Cloady workspace and app, optionally scoped by environment and region, while past incident history remains.

Instructions

Past incidents stay in the history.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "workspaceSlug": "<workspaceSlug>",
      "appSlug": "<appSlug>",
      "alertId": "<alertId>"
    },
    "name": "deleteAlert"
  }
}

Input Schema

NameRequiredDescriptionDefault
envNo
regionNo
alertIdYes
appSlugYes
workspaceSlugYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.18.0

TDQS

C2/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already mark the tool as destructive and open-world, so the safety profile is known. The description adds one useful behavioral detail—historical incidents are retained after deletion—but omits irreversibility, permission requirements, and cascade effects.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single sentence, but it is cryptic and under-specified rather than appropriately concise. The sentence is not front-loaded with the action and does not earn its place as the entire description.

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?

For a destructive five-parameter mutation with no output schema and no parameter documentation, the description is nowhere near complete. It omits the action, required identifiers, effects, and permission context.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Five parameters with 0% schema description coverage, and the description names none of them. It provides no meaning for workspaceSlug, appSlug, alertId, env, or region beyond what the bare schema names imply.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The sentence 'Past incidents stay in the history' does not state that the tool deletes an alert; the verb and resource only come from the name and title. It hints at a retention side effect but leaves the core action implicit.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to use deleteAlert versus updateAlert or listAlerts, no prerequisites, and no warnings. The only hint is that past incidents remain, which is not usage guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools