Local MCP

Telegram List Accounts

telegram_list_accounts

Read-only

List the Telegram accounts linked to LMCP on this Mac: each one's id (tg1, tg2, …), the label the user gave it, which one is the default, whether a session is stored, and a linked phone masked to its country code and last 4 digits. Pass an id or label as the account parameter of any telegram_* tool; without it they use the default account. Add another account with telegram_connect (add_account: true). Each entry's permissions carries only the permissions this service has (read, send, write; a key that is missing does not apply). true: allowed in the account's boxes (LMCP's icon → My apps → open the app's row → the account's Read · Send · Write) and the item accepts it. false: turned off there, or the item is read-only (read_only: true).

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description
`count`	Yes
`accounts`	Yes
`default_account`	No	The default account's label.
`default_account_id`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 22, 2026

addedOutput schema / properties / accounts / items / properties / permissions

Added value: +{
+  "properties": {
+    "read": {
+      "type": "boolean"
+    },
+    "send": {
+      "type": "boolean"
+    },
+    "write": {
+      "type": "boolean"
+    }
+  },
+  "type": "object"
+}

addedOutput schema / properties / accounts / items / properties / phone_masked

Added value: +{
+  "description": "The linked phone's country code and last 4 digits (+54 ••• 1234), to tell accounts apart. Never the full number. Absent when not linked or not known.",
+  "type": "string"
+}

addedOutput schema / properties / accounts / items / properties / read_only

Added value: +{
+  "description": "true: the system reports this item as not modifiable. Absent when it cannot tell.",
+  "type": "boolean"
+}

AddedOct 10, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already cover the read-only, non-destructive, local-only profile, and the description adds real interpretive context: phone numbers are masked to country code + last 4, `permissions` only carries applicable keys, and a missing key means the permission does not apply. The detailed true/false and `read_only` explanation is useful for reading results, though it drifts well past behavioral traits of this specific call.

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?

The first sentence front-loads the resource and the returned fields, which is the right ordering. The final permissions sentence is long and embeds UI navigation steps ("LMCP's icon → My apps → open the app's row → …") that add bulk beyond what an agent needs to select or call the tool.

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

Completeness5/5

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

An output schema exists so return values need no prose, yet the description still summarizes the entry shape and permission semantics. For a zero-parameter, read-only list tool, nothing needed to call it correctly is missing.

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?

Zero parameters means the baseline is 4; the description neither needs nor omits own-parameter detail. It does add cross-tool meaning by explaining that the `id`/`label` values returned here are what feed the `account` parameter elsewhere, which is non-obvious and actionable.

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?

Specific verb + resource scoped precisely ("Telegram accounts linked to LMCP on this Mac") and enumerates exactly what each entry contains (id, label, default flag, session, masked phone). It is clearly separable from telegram_connect, which it names as the way to add an account.

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?

Explicitly tells the agent to pass the returned id or label as the `account` parameter of any telegram_* tool and that omitting it falls back to the default, plus routes account creation to telegram_connect (add_account: true). It stops short of naming siblings like set_default_telegram_account or stating when-not to call it.

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

All Local MCP tools Inspect

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.