Skip to main content
Glama
conarti

yandex-messenger-mcp

by conarti
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

List chats

list_chats
Read-only

Fetch a sorted list of chats with metadata like unread flags and last message info. Optionally filter for unread only or include full last message text.

Instructions

Список чатов с метаданными (последнее сообщение, флаг непрочитанных), отсортированный по свежести. Текст последнего сообщения по умолчанию НЕ отдаётся (только метаданные) - включите include_last_message_text, если он действительно нужен.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoМаксимум чатов (по умолчанию 50)
unread_onlyNoВернуть только чаты с непрочитанными сообщениями
include_last_message_textNoВернуть полный текст последнего сообщения каждого чата. По умолчанию false: отдаются только метаданные (без текста, цитат и имён файлов), чтобы не тащить содержимое чужих переписок в контекст модели.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.1

TDQS

A4/5.0
Behavior4/5

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

No contradiction with readOnlyHint annotation. Adds behavioral detail about excluding message text by default for privacy, which is beyond what annotations provide.

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 sentences, front-loaded with purpose, no wasted words.

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?

Describes metadata returned (last message, unread flag) but lacks full output structure details. Given no output schema, more explicit fields would help completeness.

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

Parameters4/5

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

Schema coverage is 100%, but the description adds context for include_last_message_text (privacy rationale) and implies defaults for limit. This adds value beyond the schema.

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?

The description clearly states it lists chats with metadata and sort order. It distinguishes from siblings by specifying the resource and scope, but doesn't explicitly contrast with tools like search or get_history.

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?

Explains default behavior (no last message text) and when to enable include_last_message_text. Lacks explicit when-not-to-use or alternatives among siblings.

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