huly-mcp-selfhost

add_blocked_by

Mark an issue as blocked by another issue by specifying the workspace, the blocked issue, and the blocking issue, so dependency chains stay visible to your team.

Instructions

Mark an issue as blocked by another 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>",
      "blockedBy": "<blockedBy>"
    },
    "name": "add_blocked_by"
  }
}

Input Schema

Name	Required	Description
`blockedBy`	Yes	Issue that blocks it, e.g. "PROJ-100"
`workspace`	Yes
`identifier`	Yes	Blocked issue id

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 only supply destructiveHint=false, so the description carries the rest of the burden and does not deliver: it says nothing about idempotency (what happens on a duplicate block), whether the link is reversible, permission requirements, or side effects like notifications. For a relation-mutating tool this is a meaningful gap.

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 front-loaded sentence with zero wasted words. It is efficient but borders on under-specification given the mutation involved.

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 simple three-required-parameter relation tool with no output schema and minimal annotations, the description is minimally adequate. It omits duplicate-handling, permission expectations, and explicit parameter-to-role mapping, which an agent would want before calling it.

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%, with blockedBy carrying an example ('PROJ-100') and identifier labeled 'Blocked issue id', while workspace is undocumented. The description adds no meaning beyond the schema — notably it does not spell out which parameter is the blocking vs blocked issue, leaving the direction to be inferred from the terse schema labels.

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 and resource ('Mark an issue as blocked by another issue') and clarifies the direction of the relation, which the bare name add_blocked_by leaves ambiguous. It falls short of 5 because it does not explicitly contrast itself with remove_blocked_by or the more general add_relation.

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 statement of when to use this versus the inverse tool remove_blocked_by or the sibling add_relation, and no stated prerequisites (e.g., both issues must exist in the given workspace). The agent must infer usage entirely from the name.

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

Deploy Server