huly-mcp-selfhost

update_issue

Modify fields on an existing Huly issue such as title, description, status, priority, assignee, due date, component, or milestone; null clears optional values.

Instructions

Update issue fields

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": "update_issue"
  }
}

Input Schema

Name	Required	Description
`title`	No
`dueDate`	No	null clears
`assignee`	No	Person name; null clears
`priority`	No
`workspace`	Yes
`identifier`	Yes	Issue id
`statusName`	No
`description`	No	Markdown, replaces existing
`componentLabel`	No	Component name; null clears
`milestoneLabel`	No	Milestone name; null clears

Schema Changelog

Changes observed during successful MCP inspections.

First observedv3.5.1Nov 12, 2026

TDQS

C2.3/5.0

Behavior2/5

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

Annotations only declare destructiveHint=false, and the description adds no behavioral context about permission requirements, partial-update behavior, or what happens to omitted fields. It also does not mention that null values clear certain fields, even though that behavior is important for a mutation tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The definition is only four words, which is compact but severely under-specified rather than appropriately concise. Nothing is front-loaded beyond the tool name, and the brevity omits information an agent needs to invoke the tool correctly.

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

Completeness2/5

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

This is a 10-parameter mutation tool with no output schema, and the description does little to explain scope or behavior. The schema supplies some field semantics, but the definition remains incomplete for correctly distinguishing update behavior and selecting this tool over alternatives.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description provides no parameter-level meaning. The schema covers only 60% of parameters, with useful details for identifier, dueDate, assignee, description, componentLabel, and milestoneLabel, but the description does not compensate for undocumented parameters such as workspace, statusName, priority, or title.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a verb and resource ("Update issue fields"), so the basic purpose is identifiable. However, "fields" is vague and does not specify whether this is a partial update or a replacement, nor does it distinguish the tool from siblings such as bulk_update_issues or move_issue.

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 when-to-use or when-not-to-use guidance. The description does not mention alternatives like bulk_update_issues for multiple issues or move_issue for status changes, leaving the agent to infer tool selection.

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

Deploy Server