TgPilot

list_dialogs

Retrieve recent Telegram chats with type, ID, and unread counters; optionally filter to unread-only conversations.

Instructions

Recent chats with type, id and unread counters.

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

Input Schema

Name	Required	Description	Default
`limit`	No
`unread_only`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 8, 2026

TDQS

C2.2/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 behavioral burden. It discloses recency and some returned fields, but does not state that this is a read-only list operation, whether results are paginated or sorted, what permissions are needed, or how the default limit affects behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The single fragment is concise and front-loaded with no wasted wording. However, it is too terse for a tool with two undocumented parameters and lacks structure that would help an agent understand usage.

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

Completeness2/5

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

The tool is simple and has an output schema, which reduces the need to explain return values. Still, with no annotations and 0% schema description coverage, the description should explain the limit and unread_only parameters and clarify how this differs from related chat-listing tools.

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

Parameters1/5

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

Schema description coverage is 0%, and the description does not explain either parameter. It never mentions 'limit' or the 'unread_only' filter, and 'unread counters' does not clarify that filtering behavior.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The fragment names the resource ('Recent chats') and lists returned fields (type, id, unread counters), but it uses no verb and does not explicitly state that this lists dialogs or how it differs from siblings like search_chats. The purpose is inferable from the tool name but not fully stated in the description itself.

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?

There is no guidance on when to use this tool versus search_chats, get_chat_info, or unread_digest. It also gives no exclusions or context about whether it is intended only for browsing recent conversations.

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