Skip to main content
Glama
Sign In
telegram-bot-mcp

telegram-bot-mcp

by FantomaSkaRus1
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript

set_my_name

Set or remove your Telegram bot's name with optional language code. Provide a new name up to 64 characters, or empty string to delete.

Instructions

Set the bot name (max 64 chars). Empty string removes the name.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "set_my_name"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoNew bot name (empty to remove)
language_codeNoTwo-letter language code

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.0.3

TDQS

A3.8/5.0
Behavior3/5

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

No annotations provided; the description mentions the max length and empty-removes-name behavior, but does not disclose other behavioral traits like permissions required or side effects.

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?

Two concise sentences with no wasted words, directly conveying the purpose and key constraint.

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?

For a simple setter with no output schema, the description covers the essential behavior and constraint, making it mostly complete for an AI agent to use correctly.

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%, so baseline is 3. The description adds value for the 'name' parameter by specifying empty behavior, but the 'language_code' parameter only restates the schema description.

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 sets the bot name, with a max length constraint and behavior for empty string, distinguishing it from related tools like get_my_name.

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 but there is no explicit guidance on when to use this tool versus alternatives, nor any when-not-to-use conditions.

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