Skip to main content
Glama
conarti

yandex-messenger-mcp

by conarti
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

Get poll

get_poll
Read-only

Retrieve poll details by chat and message ID to get the question, answer options with vote counts, limiter, your selections, anonymity status, and results, or detect that the message is not a poll.

Instructions

Читает опрос по chat + message_id (message_id = timestamp в микросекундах), без confirm. Возвращает вопрос (title), варианты (answers, с title/votes и, для не-анонимного опроса, voters - кто голосовал), лимит выбора (max_choices), мой выбор (my_choices), признак анонимности (is_anonymous), число проголосовавших (voted_count) и результаты (results). У анонимного опроса сервер скрывает список голосующих даже по явному запросу - voters_hidden:true, доступен только агрегат и свой выбор. Признак «это опрос» виден полем is_poll (в обычной выдаче сообщения - kind:poll). Если сообщение не опрос - статус not_a_poll.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
chatYesChatId либо поисковый запрос для резолва чата
message_idYesTimestamp сообщения-опроса в микросекундах (строка)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.1

TDQS

A4.6/5.0
Behavior5/5

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

Detailed explanation of anonymous poll behavior (voters_hidden: true) and error case 'not_a_poll'. Annotations already declare readOnlyHint=true, and description adds valuable behavioral context.

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?

Description is somewhat lengthy but every sentence adds value, front-loading purpose. Could be slightly more concise.

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

Completeness5/5

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

No output schema, but description fully enumerates return fields and explains behavior for anonymous polls. Complete for a read-only tool with clear input.

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% and description adds meaning: chat can be a ChatId or search query, message_id is a timestamp in microseconds as a string. Adds value beyond schema.

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?

Description clearly states 'Reads a poll by chat + message_id' and lists all return fields. Distinguishes from siblings like get_message or vote_in_poll by being specific to polls.

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?

States 'без confirm' (without confirmation) indicating a read operation. Implicitly contrasts with vote_in_poll but lacks explicit 'when not to use' guidance.

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