Directum RX MCP (rxmcp)

Overview Schema Source Related Servers Discussions Admin

rx_ticket_relations

Read-only

Retrieve relationships for up to 50 agile board cards by numeric ID: parent, child, dependency, mandatory, duplicate, and linked cards. Use it to find subtasks, blockers, duplicates, or related cards.

Instructions

Связи карточек agile-доски с другими карточками, как блок «Связи» в карточке: родитель и дочерние, «зависит от» и «обязательна для», дубли, «связана с»; у каждой связанной карточки код, id, статус и доска, если она другая. До 50 карточек за раз. Используйте на вопросы «какие подзадачи у эпика», «что блокирует карточку», «где дубль», «к чему относится карточка». Нужны числовые Id карточек из rx_tickets или rx_board. Для одной карточки связи уже есть в rx_ticket. Только чтение.

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": {
      "ids": "<ids>"
    },
    "name": "rx_ticket_relations"
  }
}

Input Schema

Name	Required	Description	Default
`ids`	Yes	числовые Id карточек (значение id в скобках в строках rx_tickets и rx_board), до 50; коды вида ABC-12 не подходят

Schema Changelog

Changes observed during successful MCP inspections.

Addedv0.15.0Oct 29, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Goes beyond the annotations by disclosing the 50-card batch limit and the shape of each returned relation (code, id, status, board if different). 'Только чтение' merely restates readOnlyHint=true and consumes space, so no credit there, but nothing contradicts the annotations.

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-loads the definition, then relation types, then usage triggers, then prerequisites — a sensible order. It is a semicolon-heavy run-on and the trailing 'Только чтение' is redundant with the annotation, but no sentence is dead weight.

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?

With one parameter and no output schema, the description still names the returned fields and the batch cap, and it points to the sibling that covers the single-card case. An agent has everything needed to select and call it correctly.

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 already 100%, yet the description adds real value about provenance: the Ids are the numeric 'id in parentheses' shown in rx_tickets/rx_board output and codes like ABC-12 are invalid. The 50-item cap is restated, matching the 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?

States a specific resource and scope: relations of agile-board cards, enumerating every relation type (parent/children, depends-on, required-for, duplicates, linked-to) and the fields returned per related card. It is clearly distinguishable from rx_ticket, which it explicitly says already carries relations for a single card.

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?

Gives concrete trigger questions ('какие подзадачи у эпика', 'что блокирует карточку', 'где дубль') plus an explicit exclusion: for one card use rx_ticket. Prerequisites (numeric Ids from rx_tickets or rx_board) are stated too.

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