Skip to main content
Glama
Sign In
telegram-mcp-connector

telegram-mcp-connector

by nitatsuu
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Get Unread

get_unread
Read-only

Retrieve unread messages grouped by chat from the main Telegram list without marking them as read. Limit messages per chat and number of chats, and optionally include muted chats.

Instructions

Unread messages grouped by chat (main list, not Archive). Does not mark anything as read.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_unread"
  }
}

Input Schema

NameRequiredDescriptionDefault
per_chatNoMax unread messages to return per chat
max_chatsNo
include_mutedNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, but the description adds real value by explicitly promising the call will not mark anything as read — the single most important behavioral fact about a read-only unread-fetching tool. The Archive scoping is a second useful disclosure. It still says nothing about truncation/pagination when there are more unread messages than the caps allow.

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?

Two short sentences, zero filler, with the scope constraint (main list, not Archive) and the key side-effect disclaimer front-loaded. Nothing redundant.

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?

An output schema exists, so return shape need not be described, and the read-only contract is covered. However, for a tool with three limit-style parameters, the absence of any explanation of truncation behavior or muted-chat filtering leaves an agent unable to predict results at the boundaries.

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

Parameters2/5

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

Schema description coverage is only 33%: per_chat is documented in the schema, while max_chats and include_muted have no description anywhere. "Grouped by chat" gestures at per-chat limits but the description never explains chat-count caps or what include_muted toggles, so it fails to compensate for the coverage gap.

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?

States a specific resource and grouping: "Unread messages grouped by chat (main list, not Archive)" — the agent knows exactly what comes back and that Archive items are excluded. It does not name a sibling (e.g. get_messages) to contrast with, so it stops short of a 5.

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

Usage Guidelines3/5

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

Usage is only implied by the name and the "unread" qualifier; there is no explicit statement of when to call this versus get_messages, search_messages, or list_chats. The Archive exclusion is the one routing hint given.

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