fast-mcp-telegram

by io.github.leshchenko1979

Search messages globally

search_messages_globally

Read-onlyIdempotent

Search all Telegram chats at once (not scoped to one chat). Comma-separated query terms; optional filters by date, chat kind, and public username. Results are ordered by ascending date-time (oldest first); limit selects the newest N. Success: message list and metadata dict. Global search ignores include_total_count. Full documentation: https://github.com/leshchenko1979/fast-mcp-telegram/blob/main/docs/Tools-Reference.md

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": {
      "query": "<query>"
    },
    "name": "search_messages_globally"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Maximum messages to return (recommended 50 or less).
`query`	Yes	Search terms, comma-separated for multiple terms (OR-style global search). Required.
`public`	No	If true, prefer chats with a public username; if false, without. Does not apply to private DMs. Omit to skip this filter.
`max_date`	No	Inclusive maximum date filter (ISO 8601 date or datetime). Omit for no upper bound.
`min_date`	No	Inclusive minimum date filter (ISO 8601 date or datetime). Omit for no lower bound.
`chat_type`	No	Comma-separated chat kinds: private, bot, group, channel. Case-insensitive; extra spaces allowed.
`auto_expand_batches`	No	Extra search batches to run when filters narrow results. Higher values may return more matches at the cost of latency.
`include_total_count`	No	If true, response may include total_count where supported (per-chat search; ignored for global search).

Output Schema

Name	Required	Description	Default
`ok`	No
`code`	No
`error`	No
`action`	No
`params`	No
`_warning`	No
`has_more`	No
`messages`	No
`exception`	No
`operation`	No
`error_code`	No
`total_count`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedJun 18, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, open-world), so the description's real value is the behavioral details it adds: result ordering is ascending by date-time (oldest first) and limit selects the newest N, which is non-obvious and materially affects pagination strategy. It also states the success shape (message list plus metadata dict), though it says nothing about rate limits or failure modes.

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 most important constraints (global scope, ordering, limit semantics) are front-loaded in the first three sentences. It is slightly dense with a trailing documentation URL, but no sentence is filler and the structure is easy to parse.

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?

For an eight-parameter search tool with full schema coverage and an output schema, the description covers scope, ordering, limit interplay, and the include_total_count caveat, which is enough to call it correctly. The one residual gap is the auto_expand_batches latency trade-off, which lives only in the schema.

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 coverage is 100%, so all eight parameters are already documented in the schema, including dates, chat_type, public, and auto_expand_batches. The description restates the query format (comma-separated, OR-style) and the available filter categories but adds no syntax or edge-case detail beyond the schema, so the baseline of 3 applies.

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 opens with a specific verb+resource and an explicit scope qualifier: "Search all Telegram chats at once (not scoped to one chat)." That immediately separates it from the sibling get_messages, which is chat-scoped, so an agent can choose without opening either schema.

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?

It gives a clear condition for when to use this tool (searching across chats rather than within one) and notes that global search ignores include_total_count. It stops short of naming the concrete alternative tool for per-chat searching, so the agent must infer the sibling rather than being routed to it explicitly.

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

All fast-mcp-telegram 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.