Skip to main content
Glama
Sign In
telegram-mcp

telegram-mcp

by draiqw
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

tg_block

Block a Telegram user to restrict contact, or unblock by setting unblock=true.

Instructions

Block a user, or unblock with unblock=true.

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": "<user>"
    },
    "name": "tg_block"
  }
}

Input Schema

NameRequiredDescriptionDefault
userYes
unblockNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/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. It only states the action without disclosing effects, permission requirements, or reversibility beyond the unblock flag. This is insufficient for a mutation tool.

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?

The description is a single concise sentence that gets straight to the point. Every word contributes to understanding the tool's function.

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?

The tool is simple with two parameters and an output schema, so the description is mostly adequate. However, it omits details about what value the user parameter expects (e.g., ID, username) and any side effects or restrictions, leaving room for ambiguity.

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?

The description adds semantic meaning to both parameters: 'user' is the target of the block, and 'unblock=true' toggles to unblocking. This goes beyond the schema's type and default definitions, though it lacks specifics on the expected format of the user identifier.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool blocks a user and can unblock with the 'unblock=true' flag. This is a specific verb+resource action that distinguishes it from sibling tools like tg_mute or tg_delete.

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?

The description implies usage for blocking or unblocking a user but provides no explicit guidance on when to choose this over alternatives. No exclusions or alternative tool references are given.

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