Skip to main content
Glama
Sign In
telegram-mcp

telegram-mcp

by jgalea
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

sync_messages

Sync Telegram messages from all chats or a specific chat into a local SQLite cache to enable fast offline search and analytics.

Instructions

Sync messages from all chats (or a specific chat) into the local SQLite cache for fast offline search and analytics

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": "sync_messages"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax messages per chat (default 1000, max 5000)
chat_idNoOptional: sync only this chat. Omit to sync all.
max_chatsNoMax chats to sync when syncing all (default 50)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A4/5.0
Behavior3/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 discloses the local SQLite cache side effect and intended purpose, which is helpful, but it does not mention whether sync is incremental, overwrites existing cache data, or what completion/return behavior looks like.

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?

A single, front-loaded sentence states the action, scope, destination, and purpose. There is no filler or redundant information.

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?

With all parameters documented in the schema and the tool's side effect clearly summarized, an agent has enough to select and invoke it. The main gap is lack of detail about return values, sync semantics, and failure behavior, but those are not critical for invocation.

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%, so the parameters are already fully documented. The description adds little beyond reinforcing the all-chats vs. specific-chat distinction already captured by the chat_id parameter description.

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?

The description uses a specific verb ('Sync') and resource ('messages ... into the local SQLite cache'), clearly distinguishing it from retrieval/search tools like get_message or search_messages. It also clarifies the scope: all chats or a specific chat.

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?

The description communicates when to use the tool: to populate the local cache for offline search and analytics. It also explains the optional chat_id behavior, but it does not explicitly name alternatives or state when not to use it.

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