Skip to main content
Glama
Sign In
Directum RX MCP (rxmcp)

Directum RX MCP (rxmcp)

by drxinfra
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Hybrid

rx_ticket_file

Read-only

Read an attachment or image from an agile board ticket by its file number, or list all files when no number is given. Handles documents, archives, and PDF scans with paging, offset, and grep options.

Instructions

Прочитать вложение или картинку карточки agile-доски по номеру из блока «Вложения и картинки» в rx_ticket. Файл из хранилища доски: docx, xlsx, pptx, pdf (скан страницами-картинками), txt, md, csv, json, xml, html, rtf, картинки; у zip, tar и tar.gz список файлов внутри, файл изнутри читается с path; одиночный .gz распаковывается. Ссылка на документ RX читается как rx_get_document_text, внешние ссылки не открываются. Без item вернёт список файлов карточки. Длинный текст обрезается по max_chars, продолжение через offset; в логах ищите строки через grep. Только чтение.

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": {
      "id": "<id>"
    },
    "name": "rx_ticket_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesчисловой Id карточки (из rx_tickets или rx_board)
grepNoпоказать только строки с этой подстрокой (регистр не важен) и их номера; для логов, например ERROR
itemNoномер файла из блока «Вложения и картинки» в rx_ticket; без номера вернётся список
pathNoдля zip, tar, tar.gz: путь файла внутри архива из списка, который вернёт вызов без path
pagesNoдля скана pdf и as_images: сколько страниц картинками, по умолчанию 3, максимум 10
offsetNoс какого символа продолжить, если текст обрезан
as_imagesNotrue = страницы pdf картинками, даже если текстовый слой есть
max_charsNoлимит символов текста, по умолчанию из настроек сервера
page_fromNoдля скана pdf и as_images: с какой страницы показывать картинки, с 1

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.17.0

TDQS

A4.8/5.0
Behavior5/5

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

Beyond readOnlyHint/openWorldHint, the description discloses concrete runtime traits: archive listings for zip/tar/tar.gz, single .gz unpacking, pdf scans rendered as page images with page limits, truncation via max_chars/offset, and grep-style line filtering for logs. The 'Только чтение' line merely confirms the annotation; the rest is genuine added 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?

Front-loaded with the core action and format coverage, then boundaries, then parameter behaviors; nearly every clause carries information. It is dense and long for a single paragraph, and the format enumeration could be tightened, but nothing is truly wasteful.

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 nine-parameter read tool with no output schema, the description covers what is returned (file list without item), how large results are truncated and continued, and how archives and document links are handled. An agent has enough to call it correctly on first try.

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%, so the schema already defines all nine params; the description mostly restates them (item, path, max_chars/offset, grep). It does add a little semantics not in the schema — that omitting item yields a file listing and that the path must come from a prior list call — but the gap over baseline is small.

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?

The description gives a precise verb and resource (read an attachment/image of an agile-board card by its item number from the «Вложения и картинки» block in rx_ticket) and enumerates the supported file types. It also explicitly distinguishes itself from the sibling rx_get_document_text for RX document links, so an agent can route without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It states the precondition (item number taken from rx_ticket's attachment block), the no-item case (returns the card's file list), and the alternative path for RX document links. It also explicitly excludes external links from being opened, which is a when-not condition.

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