huly-mcp-selfhost

create_milestone

Create a new project milestone with a target date and optional status to track planned work and deadlines.

Instructions

Create a new milestone in a project with a target date

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>",
      "projectIdentifier": "<projectIdentifier>",
      "label": "<label>",
      "targetDate": "<targetDate>"
    },
    "name": "create_milestone"
  }
}

Input Schema

Name	Required	Description	Default
`label`	Yes
`status`	No		Planned
`workspace`	Yes
`targetDate`	Yes	ISO date
`projectIdentifier`	Yes	Project key

Schema Changelog

Changes observed during successful MCP inspections.

First observedv3.5.1Nov 12, 2026

TDQS

C2.8/5.0

Behavior2/5

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

Annotations only supply destructiveHint=false and a title, leaving the description to carry nearly the full behavioral burden. It does not disclose whether the milestone is returned, whether duplicate labels are rejected, what permissions or workspace state are required, or what the default Planned status means in practice — all relevant 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.

Conciseness4/5

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

One front-loaded sentence with no filler or repetition; the resource and the distinguishing input are stated immediately. It is efficient but so terse that conciseness shades into under-specification.

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?

With five parameters, four required, 40% schema coverage, one enum with a default, and no output schema, the definition leaves meaningful gaps — notably workspace/projectIdentifier semantics and the status default. As a creation tool with no results documented, an agent can still plausibly invoke it, but must guess at several input meanings.

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?

Schema description coverage is only 40%, so the description needs to compensate, but it says nothing about workspace, projectIdentifier (beyond the schema's 'Project key'), label constraints, or the status enum and its Planned default. The single mention of a target date simply restates the schema's 'ISO date' entry.

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 states a specific verb and resource ('Create a new milestone in a project') plus the key required input ('with a target date'), which is enough to separate it from read/update siblings like get_milestone and update_milestone. It stops short of naming any sibling explicitly, so differentiation comes from the resource noun rather than explicit routing.

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 update_milestone or get_milestone, no preconditions (e.g., the project must already exist, or whether a milestone with the same label is rejected), and no exclusions. Usage is only implied by the verb 'Create'.

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

Deploy Server