huly-mcp-selfhost

move_issue

Destructive

Move an issue to another project, carrying sub-issues, comments, files, and time tracking. The issue gets a new ID and its component and milestone are cleared.

Instructions

Move issue (incl. sub-issues, comments, files, time) to another project; gets a new id, component/milestone cleared

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": {
      "workspace": "<workspace>",
      "identifier": "<identifier>",
      "targetProjectIdentifier": "<targetProjectIdentifier>"
    },
    "name": "move_issue"
  }
}

Input Schema

Name	Required	Description
`workspace`	Yes
`identifier`	Yes	Issue id
`statusName`	No	Default: keep current
`targetProjectIdentifier`	Yes	Target project key

Schema Changelog

Changes observed during successful MCP inspections.

First observedv3.5.1Nov 12, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations only flag destructiveHint=true; the description goes further by disclosing the concrete consequences: a new id is assigned, and component/milestone are cleared. It still omits reversibility and whether cross-project side effects (e.g., status mapping, target project permissions) apply.

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?

One compact, front-loaded sentence: operation first, scope in parentheses, consequences last. No filler and nothing redundant with the schema.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive, no-output-schema mutation tool, the description covers what is carried over and what is reset, which is the essential context. Gaps are minor: reversibility, permission requirements, and the optional status override are unstated.

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 75%, so the schema already documents identifier and targetProjectIdentifier and the statusName default of keeping the current status. The description adds no meaning about the optional statusName parameter — an agent would not learn from it that a status can be set during the move.

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?

Specific verb (move) plus resource (issue) and destination (another project), with an explicit scope list of what travels with it (sub-issues, comments, files, time). It does not name a sibling such as update_issue to contrast against, so it stops short of the top score.

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

Usage Guidelines3/5

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

Usage is implied by the operation itself — use this when an issue belongs in a different project. There is no explicit when-not guidance (e.g., use update_issue for field changes within the same project) and no stated prerequisites such as permissions on both projects.

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

Deploy Server