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

Directum RX MCP (rxmcp)

by drxinfra
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Hybrid

rx_abort_task

Destructive

Aborts a Directum RX task and closes all unfinished assignments irreversibly. Requires task authorship; verify with rx_get_task and confirm before aborting.

Instructions

Прекратить задачу: все незавершённые задания по ней закрываются. Необратимо. Работает только для задач, где пользователь автор, иначе RX вернёт отказ. Сначала проверьте задачу через 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_abort_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesId задачи, которую нужно прекратить; пользователь должен быть её автором

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 задачи, которую нужно прекратить; пользователь должен быть её автором"
  2. First observedv0.1.0

TDQS

A4.7/5.0
Behavior5/5

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

Goes well beyond the destructiveHint=true annotation by disclosing the cascade effect (all unfinished assignments get closed), irreversibility, and the authorization constraint (author-only, refusal otherwise). These are non-obvious behavioral traits an agent must know before calling, not restatements of structured fields.

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 action and cascade effect, then irreversibility, then the auth constraint, then the prerequisite workflow. Every sentence carries an operational fact with no filler.

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 destructive one-parameter mutation with no output schema, the description supplies everything needed: effect scope, reversibility, auth constraint, and precondition checks. Nothing an agent needs to invoke it safely is missing.

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 coverage is 100% with a single parameter, so the schema already documents both the id meaning and the author requirement. The description reinforces the author constraint but adds no syntax or format detail beyond the schema, so baseline 3 applies.

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?

Names a specific verb (abort/terminate) and resource (task), and clarifies the scope by stating that all unfinished assignments under the task are closed. An agent can distinguish it from rx_complete_assignment or rx_delete_tickets without opening any 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?

Explicitly states the condition under which it works (user must be the task author, else RX refuses), the prerequisite check via the named sibling rx_get_task, and the requirement to confirm with the user. This covers when to use it, when it will fail, and the recommended workflow.

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