Skip to main content
Glama
stockbit-mcp

stockbit-mcp

Delete alerts

alert_delete
Destructive

Delete alerts by ID only after user confirmation. Removes specified alerts from your Stockbit account when approved.

Instructions

Deletes alerts after the user confirms.

Endpoint: POST exodus /alert/v2/delete.

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": {
      "alert_ids": "<alert_ids>"
    },
    "name": "alert_delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
alert_idsYesAlert ids, from alert_list.
confirmation_tokenNoOnly for clients without confirmation popups: the token a previous call returned with its preview. Send it only after the user has confirmed that preview.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false, openWorldHint=true, and idempotentHint=false, so the safety profile is well covered. The description adds only that deletion happens after user confirmation and the endpoint path; it does not describe permanence, response behavior, or batch effects beyond what the schema already says.

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?

Two short sentences with the action front-loaded and no filler; the endpoint line is compact. It is appropriately sized overall, though the endpoint line is more implementation detail than decision support.

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

Completeness4/5

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

For a simple two-parameter destructive tool with full schema coverage and rich annotations, the description covers the core action and confirmation requirement. It omits alternative-selection guidance, but the schema and annotations carry the remaining complexity.

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

Parameters3/5

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

Schema description coverage is 100% and both parameters have detailed schema descriptions, including alert_ids sourced 'from alert_list' and the confirmation_token flow. The description adds no additional parameter meaning beyond the schema baseline, so 3 is appropriate.

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 the specific verb and resource ('Deletes alerts') and adds a prerequisite ('after the user confirms'), so the agent knows exactly what the tool does. It does not explicitly distinguish this from sibling deletion or status tools such as alert_set_status or watchlist_delete, which keeps it from a 5.

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?

The only usage guidance is the confirmation prerequisite; there is no statement of when to choose this over alert_set_status or other alternatives. The implied use case is clear but alternatives and exclusions are absent.

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