Skip to main content
Glama
Sign In
telegram-mcp

telegram-mcp

by jgalea
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

unblock_user

Restore communication by removing a user from your Telegram block list, allowing them to message you again.

Instructions

Unblock a user

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": {
      "user_id": "<user_id>"
    },
    "name": "unblock_user"
  }
}

Input Schema

NameRequiredDescriptionDefault
user_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

C2.8/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 burden of behavioral disclosure. It only restates the action and does not explain side effects, idempotency, permission requirements, or behavior when the user is not already blocked.

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 description is appropriately short and front-loaded, conveying the essential action in four words with no filler. It is concise rather than under-specified for such a simple tool.

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 tool with no output schema and no annotations, the description is minimally adequate but has clear gaps. It does not address edge cases like unblocking an already-unblocked user or what the expected result is, though the basic action is unambiguous.

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

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, and the description does not mention the required user_id parameter at all. While the parameter is self-explanatory from its name, the description adds no meaning beyond the schema and fails to compensate for the coverage gap.

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 uses a specific verb 'unblock' with a clear resource 'user', so an agent immediately understands the core action. It does not explicitly contrast with the sibling block_user, but the inverse relationship is strongly implied by the verb itself.

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 is given about when to use unblock_user versus block_user or any other user-related tool. There is no mention of prerequisites such as the user needing to be currently blocked.

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