Skip to main content
Glama
FantomaSkaRus1

telegram-bot-mcp

get_my_default_administrator_rights

Retrieve your Telegram bot's default administrator rights. Specify whether the rights apply to channels.

Instructions

Get the bot's default administrator rights.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
for_channelsNoGet rights for channels
Behavior2/5

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

With no annotations provided, the description carries the full burden. It simply states 'Get the bot's default administrator rights' without disclosing any behavioral traits, such as authentication requirements, idempotence, or the effect of the 'for_channels' parameter. It does not explain the return format or any 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?

The description is a single sentence with no extraneous words. It is appropriately concise and front-loaded with the core purpose.

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?

Given the simplicity of the tool (one optional boolean parameter, no output schema), the description is minimally sufficient but lacks completeness. It does not explain what the bot's default administrator rights are or what the return value contains. The agent may need to infer from context.

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 schema already describes the 'for_channels' parameter as a boolean with description 'Get rights for channels'. The tool description does not add any additional meaning beyond this, so score remains at baseline.

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 'Get the bot's default administrator rights', using a specific verb ('Get') and resource ('bot's default administrator rights'). It distinguishes from the sibling tool 'set_my_default_administrator_rights' which performs a write operation.

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 vs alternatives. There is no mention of typical usage patterns, such as checking current rights before modifying with set_my_default_administrator_rights, or any conditions where the tool is inappropriate.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/FantomaSkaRus1/telegram-bot-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server