huly-mcp-selfhost

get_milestone

Read-only

Retrieve a project milestone by label to view its progress and open issues. Use it to check milestone status and remaining work for a specific project.

Instructions

Milestone with progress and open issues

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": {
      "projectIdentifier": "<projectIdentifier>",
      "label": "<label>"
    },
    "name": "get_milestone"
  }
}

Input Schema

Name	Required	Description
`label`	Yes
`workspace`	No
`projectIdentifier`	Yes	Project key

Schema Changelog

Changes observed during successful MCP inspections.

First observedv3.5.1Nov 12, 2026

TDQS

D1.8/5.0

Behavior2/5

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

The readOnlyHint annotation already establishes this is a safe read, and the description adds only that progress and open issues are included in the response. It says nothing about permissions, what happens when the label does not match a milestone, or the response shape beyond that phrase.

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 description is a single noun phrase rather than a sentence, so it is under-specified rather than concise. There is no front-loaded verb to anchor the reader and no structure separating purpose from return content.

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?

For a three-parameter lookup with no output schema, the description should at minimum state that it retrieves one milestone identified by project key plus label. Missing that, the agent must guess selector semantics and cannot tell what exactly is returned beyond 'progress and open issues'.

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 33%: only projectIdentifier carries a description ('Project key'), while 'label' and 'workspace' are undocumented. The description does not mention any parameter, so it fails to compensate for the gap and never clarifies the label-vs-title matching semantics or what workspace scoping does.

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

Purpose2/5

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

The text 'Milestone with progress and open issues' is a noun fragment that restates the tool name and adds only a vague hint about returned data. It contains no verb and never says whether this fetches a single milestone by label or list milestones, so an agent cannot distinguish it from get_project or create_milestone with confidence.

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

Usage Guidelines1/5

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

There is no when-to-use guidance, no mention of prerequisites, and no reference to alternatives such as get_issue or get_project for related lookups. The agent is left to infer that a label and project identifier select exactly one milestone.

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

Deploy Server