Skip to main content
Glama
trading-crew-mcp

trading-crew-mcp

delete_alert

Deletes a single price alert by its ID and verifies that it no longer exists.

Instructions

Delete one alert by id and confirm it is gone.

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_id": "<alert_id>"
    },
    "name": "delete_alert"
  }
}

Input Schema

NameRequiredDescriptionDefault
alert_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. 'Confirm it is gone' usefully implies a verification step, but it says nothing about irreversibility, permissions or auth requirements, what happens when the id does not exist, or whether the call errors or returns a confirmation payload.

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?

One tight sentence with the action front-loaded and zero filler. 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 tool with no annotations and no output schema, the description covers the core action but omits the not-found behavior, irreversibility, and return value, which matter for a delete operation.

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 coverage is 0% and the single parameter is undocumented in the schema, so the description's 'by id' is the only signal that alert_id is an identifier. It does not state the type (integer), whether it is a server-assigned alert id, or how to discover valid ids.

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?

States a specific verb and resource ('Delete one alert') plus the scoping mechanism ('by id') and the post-condition ('confirm it is gone'). This is clearly distinguishable from create_alert, modify_alert, and list_alerts, though it does not name them explicitly.

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?

No guidance on when to use this rather than modify_alert or list_alerts, and no prerequisites are stated (e.g., obtaining an alert_id from list_alerts). The only implicit cue is 'one alert', suggesting single-item deletion.

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