Skip to main content
Glama
DLHellMe
by DLHellMe

telegram_logout

Clear authentication cookies to log out from Telegram sessions, removing stored login credentials and access tokens.

Instructions

Clear Telegram authentication cookies

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function that implements the core logic of the 'telegram_logout' tool. It invokes the auth.logout() method to clear Telegram authentication cookies and returns a standardized MCP response confirming the logout.
    private async handleTelegramLogout(): Promise<any> {
      await this.auth.logout();
      
      return {
        content: [
          {
            type: 'text',
            text: '✅ Successfully logged out from Telegram. Authentication cookies have been cleared.'
          }
        ]
      };
    }
  • src/server.ts:235-243 (registration)
    The registration of the 'telegram_logout' tool within the MCP server's tool list, including its name, description, and input schema (which requires no parameters).
    {
      name: 'telegram_logout',
      description: 'Clear Telegram authentication cookies',
      inputSchema: {
        type: 'object',
        properties: {},
        required: []
      }
    },
  • The input schema definition for the 'telegram_logout' tool, specifying an empty object with no required properties.
    inputSchema: {
      type: 'object',
      properties: {},
      required: []
    }
  • The dispatch case in the main tool execution switch statement that routes calls to the 'telegram_logout' handler.
    case 'telegram_logout':
      return await this.handleTelegramLogout();
Behavior2/5

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

No annotations are provided, so the description carries full burden. 'Clear Telegram authentication cookies' implies a destructive action that removes authentication state, but it doesn't disclose behavioral traits such as whether this logs the user out of all sessions, if it's reversible, what happens on failure, or if it requires specific permissions. For a mutation tool with zero annotation coverage, this is a significant gap in 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, efficient sentence with zero waste. It's front-loaded with the core action and target, making it immediately understandable. Every word earns its place, and there's no unnecessary elaboration.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (a mutation operation with no annotations and no output schema), the description is incomplete. It lacks details on what 'clear' means behaviorally (e.g., does it invalidate sessions, is it idempotent), what the expected outcome is, or any error conditions. For a tool that modifies authentication state, more context is needed to guide safe usage.

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 has 0 parameters, and schema description coverage is 100% (since there are no parameters to describe). The description doesn't need to add parameter semantics, so a baseline of 4 is appropriate. It implicitly confirms no inputs are required, which aligns with the empty schema.

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?

The description 'Clear Telegram authentication cookies' clearly states the action (clear) and target (Telegram authentication cookies). It distinguishes from siblings like 'telegram_login' (establish authentication) and 'telegram_auth_status' (check authentication), though it doesn't explicitly mention these alternatives. The purpose is specific but could be slightly more precise about what 'clear' entails.

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. It doesn't mention prerequisites (e.g., must be logged in first), consequences (e.g., will log you out), or when it's appropriate (e.g., to reset authentication state). With siblings like 'api_logout' and 'telegram_login', explicit usage context is missing.

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/DLHellMe/telegram-mcp-server'

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