Skip to main content
Glama

Local MCP

by com.local-mcp
OverviewDiscussionsAdmin

Telegram Connect

telegram_connect
Destructive

Links your own Telegram account to LMCP on this Mac. Shows a QR code (here and in a window on the Mac): on your phone open Telegram → Settings → Devices → Link Desktop Device and scan it. The Mac window also offers the phone-number login and asks for your two-step verification password if you have one. If that account is already connected, it says so. To link ANOTHER Telegram account, pass add_account: true (optionally with a label); account re-links an existing one (see telegram_list_accounts).

Input Schema

NameRequiredDescriptionDefault
labelNoWith add_account: the name for the new account (1-40 characters). Default "Telegram <n>".
accountNoWhich linked Telegram account to use: its label or id from telegram_list_accounts. Leave it out to use the default account.
confirmNoIgnored; kept for older clients.
add_accountNotrue to link an additional Telegram account (a new QR).

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / confirm / description
      Previous value: -"Must be true to start the link. Without it the call returns a preview and does nothing."New value: +"Ignored; kept for older clients."
  2. Changed1 schema field changed
    • addedInput schema / properties / confirm
      Added value: +{
+  "description": "Must be true to start the link. Without it the call returns a preview and does nothing.",
+  "type": "boolean"
+}
  3. Added

TDQS

A4.5/5.0
Behavior4/5

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

Annotations declare readOnlyHint=false, destructiveHint=true, openWorldHint=true; the description adds real behavior beyond that: a QR is shown both in-chat and in a Mac window, the window offers phone-number login and prompts for a two-step password, and it reports if the account is already linked. It does not explain why the tool is flagged destructive or any rate/limit issues, so it's strong but not complete.

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-loads the core action (linking via QR), then the phone steps, then the add_account/re-link distinctions. Multiple sentences but each contributes; slightly long for the silent `confirm` param but overall efficient.

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?

The tool is complex (an interactive linking flow) and an output schema exists so return values needn't be described. The description covers the flow, alternatives, and edge cases; only the destructive-hint rationale and any failure/recovery behavior are left implicit.

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?

Schema coverage is 100%, so the baseline is 3; the description still adds semantic context by explaining that add_account triggers a new QR (optionally with a label) and that `account` re-links an existing account sourced from telegram_list_accounts. This goes beyond restating 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?

Uses a specific verb (links) and precise resource (your own Telegram account) plus the mechanism (QR code from Mac window). It distinguishes the add_account path from the re-link `account` path and names the sibling telegram_list_accounts, so an agent can tell it apart from telegram_disconnect or telegram_send_message.

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

Usage Guidelines5/5

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

Explicitly states when to pass add_account: true (to link ANOTHER account, optionally with a label) versus using `account` to re-link an existing one, and points to telegram_list_accounts for the source of ids/labels. It also covers the already-connected case.

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

All Local MCP toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources