huly-mcp-selfhost

set_parent

Set or clear an issue's parent epic using workspace and child identifier; omit or null the parent identifier to remove the parent link.

Instructions

Set or clear the parent (epic) of an issue

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>"
    },
    "name": "set_parent"
  }
}

Input Schema

Name	Required	Description
`workspace`	Yes
`identifier`	Yes	Child issue identifier, e.g. "PROJ-123"
`parentIdentifier`	No	Parent issue id; null clears

Schema Changelog

Changes observed during successful MCP inspections.

First observedv3.5.1Nov 12, 2026

TDQS

C2.9/5.0

Behavior2/5

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

Annotations supply only destructiveHint=false, so the description carries most of the burden and does not meet it. It never says whether an existing parent is silently replaced, whether cycles or self-parenting are rejected, whether this requires write permission on both issues, or what happens if the parent identifier is invalid.

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?

A single eight-word sentence with no filler and the mutation semantics front-loaded. It is efficient, though the brevity is partly the cause of the gaps flagged in other dimensions.

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

Completeness3/5

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

For a three-parameter, non-nested mutation with no output schema, the definition is minimally adequate: the schema covers the fields and annotations cover the safety flag. Missing are the replacement/overwrite behavior and failure conditions an agent would want before calling a mutation.

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 67% and already documents the identifier example and that parentIdentifier=null clears the parent, so the description adds essentially no parameter meaning beyond the schema. The 'set or clear' phrasing merely restates the null-clears semantics already stated in the schema.

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?

The description gives a specific verb pair (set/clear) and a specific resource (the parent/epic of an issue), and the parenthetical '(epic)' disambiguates what a parent means in this domain. It does not name or contrast any sibling such as add_relation or create_issue_tree, so it stops short of full sibling differentiation.

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

Usage Guidelines2/5

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

There is no guidance on when to use this tool versus related siblings (add_relation, add_blocked_by, create_issue_tree) or on prerequisites such as needing an existing parent issue. The only usage signal is the implied 'set or clear' duality, which is already visible in the schema.

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

Deploy Server