Skip to main content
Glama

unsubscribe

Cancel an event subscription to stop writing that event type to the ring buffer and receive the remaining active subscriptions.

Instructions

取消事件订阅(停止向环形缓冲写入对应类型事件)。响应含剩余全部活跃订阅。

Args: subscription_id: subscribe_events 返回的 subscription_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": {
      "subscription_id": "<subscription_id>"
    },
    "name": "unsubscribe"
  }
}

Input Schema

NameRequiredDescriptionDefault
subscription_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden and does add real behavioral information: it states the side effect (stopping writes into the ring buffer) and that the response contains all remaining active subscriptions. It omits error behavior, idempotency, and any permission or state preconditions.

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?

The effect and return value are front-loaded in two short clauses, followed by a compact Args block for the single parameter. Almost nothing is wasted, though the Args section is slightly redundant given only one parameter exists.

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?

This is a simple one-parameter mutation tool with an output schema, so the return value need not be spelled out. Given the lack of annotations, the description supplies the essential side effect and id provenance; only failure modes and idempotency are missing.

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

Parameters4/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 documented only as 'Subscription Id' in the schema, so the description's note that it is the subscription_id returned by subscribe_events meaningfully compensates by telling the agent where to obtain a valid value.

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 names a specific verb and resource ('cancel event subscription') and adds the concrete effect: no further events of that type are written to the ring buffer. It also connects to the sibling 'subscribe_events' as the source of the id, so the tool is distinguishable from the rest of the catalog, though it never explicitly frames the subscribe/unsubscribe pairing as an alternative choice.

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?

Usage is implied rather than stated: the reader infers this is called after subscribe_events with the id it returned. There is no explicit when-to-use or when-not guidance, and no mention of what happens when an unknown or already-cancelled id is passed.

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