Skip to main content
Glama

Unsubscribe from Alerts

unsubscribe
Idempotent

Cancel a subscription by id. Ownership is enforced, you can only cancel your own subscriptions. The row is deactivated (not deleted) so its historical events stay available via recent_alerts.

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

Input Schema

NameRequiredDescriptionDefault
idYesSubscription id (uuid) returned by subscribe.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior3/5

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

The annotations already declare a non-read-only, idempotent, non-destructive mutation, and the description adds genuinely useful behavior the annotations cannot express: ownership enforcement and the fact that the row is deactivated rather than deleted, with events still reachable via recent_alerts. That is real added value, though it doesn't say what happens if the id is unknown or already cancelled, or what the response contains.

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, front-loaded with the action and followed by the two facts that matter most (ownership, soft delete). Wording is efficient; nothing is wasted, though the middle sentence about ownership could be tightened.

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 mutation with no output schema, the definition covers everything an agent needs: what it does, the ownership precondition, and the reversibility model including where historical data survives. Annotations carry the safety profile, so no essential disclosure is missing.

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 100% and the schema already documents id as a uuid returned by subscribe. The description repeats the id-based contract without adding format, validation, or error semantics beyond the schema, so baseline 3 applies.

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 ('Cancel a subscription by id') so the operation is unambiguous, and it references subscribe/recent_alerts to situate the tool in a lifecycle. It does not explicitly contrast itself with list_subscriptions or forget, so sibling differentiation is partial rather than stated.

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 clear operating context: cancellation is by id and restricted to subscriptions the caller owns. It stops short of naming an alternative (for hard deletion, or for finding the id via list_subscriptions), so there is no explicit when-not guidance.

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.