telegram-business-bridge

Overview Schema Source Related Servers Discussions Admin

search_messages

Search Telegram message history with full-text queries. Filter results by chat, sender, or date range.

Instructions

Полнотекстовый поиск по всей истории (FTS, без стемминга — пробуй словоформы). Фильтры: chat_id, sender, from_iso, to_iso.

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

Input Schema

Name	Required	Description	Default
`limit`	No
`query`	Yes
`sender`	No
`to_iso`	No
`chat_id`	No
`from_iso`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 13, 2026

TDQS

A3.9/5.0

Behavior3/5

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

Describes FTS and lack of stemming, which are key behaviors. However, no details on pagination, sorting, case sensitivity, or permissions. Without annotations, more behavioral context would improve agent understanding.

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?

Extremely concise: two front-loaded sentences covering purpose and filters. No redundant or vague language.

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?

Adquate for a search tool with output schema; covers core functionality and available filters. Lacks details on result ordering, pagination (limit is present but not mentioned), and edge cases. Not fully comprehensive.

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?

Adds value by listing filter parameters (chat_id, sender, from_iso, to_iso) beyond the empty schema descriptions. But does not explain their meaning or format (e.g., date format), and omits the limit parameter entirely. Minimal compensation for 0% schema coverage.

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?

Clearly states 'full-text search over entire history' (FTS) which distinguishes it from sibling tools like draft_reply or list_chats. Specific verb+resource with scope and limitations.

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 notes 'no stemming — try word forms', guiding query formulation. Lists available filters. While it doesn't explicitly state when not to use or name alternatives, the context of siblings makes the use case clear.

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

Deploy Server