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

Directum RX MCP (rxmcp)

by drxinfra
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Hybrid

rx_get_assignment

Read-only

Fetch a full assignment or notification by ID from my assignments, including subject, author, due date, task, attachments, and thread messages, to understand what the user must act on. Read-only.

Instructions

Одно задание или уведомление целиком: тема, автор, срок, задача, вложенные документы и вся переписка по нитке. Используйте, чтобы понять, что именно требуется от пользователя. Id берётся из rx_my_assignments. Ход всей задачи с остальными исполнителями показывает rx_get_task. Только чтение.

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_get_assignment"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesId задания или уведомления: число после # в строке rx_my_assignments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.5.2
    • changedInput schema / properties / id / description
      Previous value: -"Id объекта в RX (число из #123)"New value: +"Id задания или уведомления: число после # в строке rx_my_assignments"
  2. First observedv0.1.0

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, and the description reinforces that with 'Только чтение', so there is no contradiction. It adds real value by disclosing the returned content (full thread, attachments), but says nothing about size limits or truncation for long threads, which is the remaining unknown for a full-object fetch.

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 with no filler, front-loading what the tool returns before the routing and provenance sentences. Every sentence carries a distinct piece of information.

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 no output schema, the description compensates by enumerating the returned fields, plus the id source and the sibling boundary. An agent has everything needed to decide and invoke 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 100%, so the id parameter is already documented, giving a baseline of 3. The description adds provenance beyond the schema by telling the agent the id is taken from rx_my_assignments, which is the concrete step the agent needs to obtain a valid value.

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 verb+resource (retrieve a single assignment or notification in full) and enumerates the payload: subject, author, due date, task, attached documents, and the whole correspondence thread. It explicitly distinguishes itself from the sibling rx_get_task, which shows the task's progress with other executors.

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 the when ('use it to understand what is actually being asked of the user'), the input provenance ('the id comes from rx_my_assignments'), and the alternative plus its distinguishing condition (rx_get_task for the task's progress with other executors). Nothing is left to inference.

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