Skip to main content
Glama
Sign In
Cloady

Cloady

Official
by Cloady
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Update Alert

updateAlert
Destructive

Modify a Cloady alert rule's threshold, time window, notification channels, or on/off state; turning it off silences notifications while retaining the rule.

Instructions

Changes the threshold, durations, notifications or the on/off switch. Turning a rule off silences it, so it stops notifying.

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": "updateAlert"
  }
}

Input Schema

NameRequiredDescriptionDefault
envNo
regionNo
alertIdYes
appSlugYes
requestBodyNoThe metric and the service stay as created; delete the rule and create another to change them
workspaceSlugYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.18.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare this as a non-read-only, destructive, open-world mutation, so the safety profile is covered. The description adds one useful behavior: turning the rule off silences it. It does not disclose partial-update semantics, permissions, or what happens to fields that are omitted.

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

Conciseness5/5

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

The description is two front-loaded sentences with no wasted wording. Each sentence contributes directly to purpose and the important off-switch behavior.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive update tool with a nested request body and no output schema, the description covers the main mutation targets and the silencing effect of disabling. However, it omits critical update semantics such as whether omitted fields are preserved and how identifiers are required, leaving an adequate but incomplete picture.

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 description coverage is low at 17%, so the description should compensate for undocumented parameters. It groups the mutable fields into threshold, durations, notifications, and on/off switch, but it does not clarify the required identifiers, env/region usage, or partial-update behavior, leaving substantial parameter meaning to the schema.

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

Purpose4/5

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

The description states a specific mutation verb and names the mutable aspects: threshold, durations, notifications, and the on/off switch. It is clear what the tool changes, but it does not explicitly distinguish itself from siblings such as createAlert or deleteAlert.

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?

Usage is implied: use this tool to modify an existing alert's threshold, durations, notifications, or enabled state. There is no explicit when-not guidance in the description, and alternatives are not named, though the schema hints that metric/service changes require delete-and-create.

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