Skip to main content
Glama
Sign In
Telegram MCP Server

Telegram MCP Server

by lyduchuy1204
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

whoami

Read-only

Shows which Telegram account this server is logged in as, so you can verify the active account before reading chats or changing settings.

Instructions

Show which Telegram account this server is logged in as.

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": "whoami"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds the useful detail that the result concerns the server's logged-in session rather than an arbitrary user, but says nothing about failure modes (e.g. not logged in) or what form the identity takes.

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?

A single, front-loaded sentence with no filler. Every word earns its place.

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 trivial zero-argument read tool with annotations covering safety, the description is essentially complete. The only minor gap is not hinting at the shape of the returned identity (id, username, phone), which an output schema would otherwise have covered.

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 tool takes no parameters, so there is nothing beyond the empty schema to explain; the description implicitly confirms no input is required. Baseline 4 applies for zero-param tools.

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

Purpose4/5

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

States a concrete verb ('Show') and a precise resource: the Telegram account the server is logged in as. That is enough for an agent to distinguish it from data-listing tools, though it doesn't explicitly contrast with close siblings like get_profile.

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 rather than stated – an agent can infer 'use this to verify the authenticated session' – but there is no explicit when-to-use/when-not guidance, nor a pointer to get_profile for a different identity target.

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