Skip to main content
Glama

delete_signal

Delete a signal; returns { deleted: true }. Its checks stop immediately. Events it already produced stay available in get_signal_events until their 90 days run out. To watch the target of a stopped signal again, delete it and create it again with create_signal. Fails with signalNotFound for an unknown id.

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": {
      "signalId": "<signalId>"
    },
    "name": "delete_signal"
  }
}

Input Schema

NameRequiredDescriptionDefault
signalIdYesSignal id, as returned by create_signal or get_signals.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior5/5

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

Goes well beyond the annotations (readOnlyHint=false, openWorldHint=true), which only say this is a write in an open world. The description discloses the exact response ({ deleted: true }), that checks halt immediately, that already-produced events survive in get_signal_events for 90 days, the recreate-to-resume workaround, and the signalNotFound error case.

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?

Four short sentences, each carrying distinct information - effect, return value, event retention, recovery path, error case - with the most decision-relevant facts front-loaded. No filler or repeated restatements.

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

Completeness5/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 output schema, the description covers effect timing, side effects, data retention, recovery, and error semantics. There is nothing further an agent needs in order to call it correctly and interpret the outcome.

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?

One required parameter with 100% schema description coverage, so the schema already explains signalId and its origin (create_signal/get_signals). The description adds only a marginal hint about invalid ids via the signalNotFound behavior, which meets the baseline for a fully documented single param.

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 a signal') and immediately discloses the return shape and the fact that its checks stop. It implicitly separates the tool from the pause/resume siblings by noting events persist and that re-watching requires deleting and re-creating, though it never names pause_signal explicitly.

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

Usage Guidelines4/5

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

Gives a concrete when-to-use path: to watch the target of a stopped signal again, delete it and re-create it with create_signal. It also names the failure mode (signalNotFound for an unknown id), but offers no explicit 'do not use this to temporarily stop a signal, use pause_signal instead' exclusion.

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.