Skip to main content
Glama
Sign In
aiogram-mcp

aiogram-mcp

by Py2755
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

unsubscribe_events

Cancel a subscription to stop receiving real-time Telegram events for a given subscription ID.

Instructions

Unsubscribe from real-time Telegram events.

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_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
subscription_idYesThe subscription ID returned by subscribe_events.

Output Schema

NameRequiredDescriptionDefault
okYes
errorNo
subscription_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / subscription_id / description
      Added value: +"The subscription ID returned by subscribe_events."
  2. First observedv0.7.1

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description must carry behavioral info. It only states the action without disclosing effects, required permissions, or error states. Insufficient for a mutation operation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is very short but achieves clarity. Could be improved without becoming verbose (e.g., mentioning that it stops events for that subscription). Acceptable conciseness.

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 simple unsubscription with a single parameter and no output schema details, the description is minimally adequate. Lacks warnings about invalid IDs or side effects.

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 parameter description is clear. The tool description adds no extra meaning beyond the schema, so baseline 3.

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 clearly states the action (unsubscribe) and the resource (real-time Telegram events), distinguishing it from the sibling subscribe_events. However, it does not elaborate on scope or specific behavior.

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 tool or prerequisites (e.g., must have an active subscription). Similar to subscribe_events, but no explicit mention of context.

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