Skip to main content
Glama

Remove an alert

remove_alert
Idempotent

Remove this account’s saved target. Needs account scope. Free.

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": {
      "id": "<id>"
    },
    "name": "remove_alert"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.8/5.0
Behavior3/5

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

The description adds two facts not present in the annotations: an account-scope requirement and that the call is free. That is genuine value, but it does not say what is removed beyond the saved entry, whether the removal is reversible, or what happens if the id does not exist. "Remove" sits in mild tension with destructiveHint=false, though removing a saved alert is plausibly low-stakes and recoverable, so this is not a clear contradiction.

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

Conciseness4/5

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

Three short sentences with the action front-loaded and no filler. The terseness costs some clarity, but nothing is redundant or padded.

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 one-parameter destructive-ish tool with annotations covering the safety profile and no output schema, most of the burden is met. Still missing is any statement of what the id refers to and whether removal is permanent, which matter for calling it correctly.

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 0% and the single parameter is only typed as a positive integer, so the description must explain what the id identifies. It does not; "saved target" never clarifies whether the id is an alert id, a target id, or an account-scoped identifier, leaving the caller to guess.

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

Purpose3/5

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

"Remove this account's saved target" gives a verb plus an object, so the basic action is inferable, but the resource is called a "saved target" rather than an alert, forcing the agent to reconcile the description with the tool name. It also offers no differentiation from siblings such as update_alert or delete_ask, which are the likely points of confusion.

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 when-to-use guidance and no mention of when not to use it or what the alternative is (e.g. update_alert to modify a saved alert instead of removing it). The only guidance-like content is "Needs account scope," which is a prerequisite rather than a usage rule.

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.

Resources