Skip to main content
Glama
Sign In
Telegram MCP

Telegram MCP

by Anonymouse8882
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

set_username

Set your Telegram @username or clear it by passing an empty string.

Instructions

设置或清空自己的 @username（传空字符串表示清空）。

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": {
      "username": "<username>"
    },
    "name": "set_username"
  }
}

Input Schema

NameRequiredDescriptionDefault
usernameYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are present, so the description must carry the full burden. It reveals only the basic operation (set/clear) but does not disclose side effects, whether it requires authentication, rate limits, or what happens if the username is invalid. The description is too minimal for full behavioral transparency.

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 sentence (in Chinese) that directly states the purpose and a key usage note. It is front-loaded and contains no extraneous information.

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 (one parameter), and an output schema exists. However, the description does not explain what the tool returns or potential errors. It is minimally complete for the task but could be improved with more context.

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 coverage is 0%, so the description must compensate. It adds that passing an empty string clears the username, which is not in the schema. However, it does not explain format, length limits, or allowed characters. The added value is modest.

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 action (set or clear) and the resource (@username). It explicitly mentions that passing an empty string clears the username, making the purpose unambiguous. The sibling tools cover different operations (e.g., managing chats, contacts), so this tool is distinct.

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?

The description provides no guidance on when to use this tool versus alternatives, nor does it specify prerequisites or exclusions. It only describes what the tool does, leaving the agent to infer usage context from sibling names.

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