Skip to main content
Glama
Sign In
telegram-mcp

telegram-mcp

by Maxsh
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

get_chat_status

Retrieve detailed status information for any Telegram chat, including unread message count and read status. Identify chats by username, phone number, or chat ID.

Instructions

Get detailed status information about a chat including unread count and read status

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": {
      "chat": "<chat>"
    },
    "name": "get_chat_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
chatYesChat identifier: username (@username), phone number (+1234567890), or chat ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It does not state whether this requires authentication, whether it is read-only or mutates read state, or what the returned status contains beyond two named fields.

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?

A single efficient sentence that front-loads the verb and resource with no wasted words. Appropriately sized for a one-parameter read tool.

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

Completeness3/5

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

Adequate for a simple one-param tool, but with no annotations and no output schema it should disclose more about the return payload and whether fetching status affects read state, which would help disambiguate from check_unread_messages.

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

Parameters3/5

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

Schema description coverage is 100% and the 'chat' parameter already documents accepted identifier formats (@username, phone, chat ID). The description adds no further meaning beyond the schema. Baseline 3 applies.

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?

Clear verb (get) plus resource (chat status) with specific fields named ('unread count and read status'). It does not differentiate from siblings like check_unread_messages or get_channel_info, which overlap in the unread/channel domain.

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?

No indication of when to use this versus check_unread_messages, which also reports unread status, or get_channel_info for chat metadata. No exclusions or context provided.

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