Skip to main content
Glama
uk-kd

operbots-mcp

by uk-kd
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

История переписки

dialogs_history
Read-onlyIdempotent

Retrieve dialog messages from oldest to newest without marking them as read. Use before and before_id to fetch earlier messages when multiple messages share the same timestamp.

Instructions

Сообщения диалога от старых к новым. По умолчанию ничего не помечает прочитанным — счётчики в панели остаются как были. За ранними сообщениями передайте before и before_id самого раннего сообщения: время бывает одинаковым у нескольких сообщений. Пометить прочитанным — отдельный write-инструмент dialogs_mark_read.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
caseNoДело: название или идентификатор. Если не указать, берётся дело по умолчанию, иначе последнее открытое в панели.
limitNoСколько записей вернуть, максимум 300. По умолчанию 80.
beforeNoПоказать сообщения раньше этого момента (ISO 8601).
dialogYesДиалог: имя собеседника, @username, номер чата или идентификатор.
before_idNoID самого раннего сообщения вместе с before: порядок при одинаковом времени.
mark_readNoТолько false. Изменяет счётчик отдельный dialogs_mark_read.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.2.0
    • addedInput schema / properties / before / pattern
      Added value: +"^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d:[0-5]\\d(?:\\.\\d+)?(?:Z|([+-](?:[01]\\d|2[0-3]):[0-5]\\d))|(?:[01]\\d|2[0-3]):[0-5]\\d(?::[0-5]\\d(?:\\.\\d+)?)?)$"
    • addedInput schema / properties / before_id
      Added value: +{
+  "description": "ID самого раннего сообщения вместе с before: порядок при одинаковом времени.",
+  "format": "uuid",
+  "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$",
+  "type": "string"
+}
    • addedInput schema / properties / mark_read / const
      Added value: +false
    • changedInput schema / properties / mark_read / description
      Previous value: -"Пометить входящие прочитанными и обнулить счётчик. По умолчанию нет."New value: +"Только false. Изменяет счётчик отдельный dialogs_mark_read."
  2. First observedv0.1.1

TDQS

A4.3/5.0
Behavior5/5

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

Adds key behavioral context beyond the readOnlyHint annotation: the tool does not mark messages as read by default and leaves counters unchanged. It also clarifies that marking read is handled by a separate write tool.

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?

Four short sentences, front-loaded with the core behavior, then pagination and read-marking guidance. Every sentence serves a distinct purpose with no redundancy.

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?

For a read-only history tool with rich annotations and full schema coverage, the description covers ordering, default non-mutation, pagination, and the read-marking alternative. Return values are not described, but no output schema exists and the description sufficiently indicates what is returned.

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 description coverage is 100%, so the schema already documents all parameters. The description restates the before/before_id tie-breaking guidance and the mark_read constraint, but adds no meaningful semantics beyond what the schema provides.

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?

States the resource (dialog messages) and ordering (old to new), which is specific. It distinguishes from the write-oriented sibling dialogs_mark_read, but does not differentiate from other read siblings like dialogs_list, dialogs_get, or dialogs_export.

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 routes marking messages as read to the separate write tool dialogs_mark_read and describes when to pass before/before_id for pagination. It lacks guidance on when to choose this tool over other dialog-reading 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