Telegram OSINT

Overview Schema Source Related Servers Discussions Admin

login_request_code

Request a Telegram login code for a phone number to start authentication, then submit the received code to complete sign-in.

Instructions

Start logging in: ask Telegram to send a login code.

Telegram delivers the code in the Telegram app itself if the user is signed in elsewhere, otherwise by SMS. Follow with login_submit_code.

Ask the user for their phone number rather than guessing it.

Args: phone: phone number in international format, e.g. +14155550123. session: which session to log in — 'watcher' (default, the one monitoring needs) or 'mcp' (for this server's read tools).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "phone": "<phone>"
    },
    "name": "login_request_code"
  }
}

Input Schema

Name	Required	Description	Default
`phone`	Yes
`session`	No		watcher

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 28, 2026

TDQS

A4.4/5.0

Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses how the code is delivered (in-app if signed in elsewhere, otherwise SMS) and what each session value means. It omits failure modes such as invalid numbers or whether a new request invalidates a previous code, so it falls short of a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the action and sequencing, then a compact Args block. Every sentence carries information, though the two-session explanation is somewhat verbose relative to its size.

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?

No output schema exists, and the description covers the call's purpose, follow-up step, and both parameters, which is sufficient for an agent to invoke it correctly. Error and retry behavior is not covered, keeping it just under a 5.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate fully. It specifies the phone format with a concrete example ('+14155550123') and enumerates the session values with their semantics and default ('watcher' for monitoring, 'mcp' for read tools) — all information absent from the schema.

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?

States a specific verb and resource ('Start logging in: ask Telegram to send a login code') and explicitly names the next sibling tool (login_submit_code). An agent can distinguish this from login_submit_code and auth_status without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives clear sequencing ('Follow with login_submit_code') and a strong usage instruction ('Ask the user for their phone number rather than guessing it'). It does not state a when-not condition (e.g., what to do if already signed in via auth_status), so it stops short of full exclusion guidance.

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