Fetches default Telegram administrator rights for the bot, optionally for channels, so you can verify permissions before promoting or configuring admin roles.
Get default admin rights.
| Name | Required | Description | Default |
|---|---|---|---|
| for_channels | No |
Changes observed during successful MCP inspections.
v0.2.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is fully covered. The description adds no additional behavioral context beyond what the annotations provide, such as response format or edge cases. This meets the baseline for a read-only tool with strong annotation coverage.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, concise sentence that is front-loaded and contains no unnecessary words. It efficiently states the tool's purpose without fluff, making it easy to scan.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool has no output schema and one optional parameter, the description is too minimal to be complete. It does not explain the parameter's effect or what the return value will be. For a getter with no structured output documentation, the description should provide more context about the response or usage, which it fails to do.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The single parameter 'for_channels' is a boolean with no schema description, and the description does not mention it at all. With 0% schema description coverage, the description fails to compensate by explaining what the parameter does or how it affects the results. The parameter name offers some hint, but the description leaves it unexplained.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description 'Get default admin rights' clearly indicates a read operation to retrieve default administrator rights, matching the tool name and distinguishing it from the sibling setter 'set_my_default_administrator_rights'. However, it does not elaborate on what 'default admin rights' means or who they apply to, so it is clear but not deeply specific.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
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. There is no mention of the setter sibling or any context suggesting when this getter is appropriate. The sibling list implies a pair with 'set_my_default_administrator_rights', but the description itself offers no such guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.