Skip to main content
Glama
Sign In
huly-mcp-selfhost

huly-mcp-selfhost

by JoKeks2023
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

list_milestones

Read-only

Retrieve milestones for a project using its project key to track delivery dates, progress, and status.

Instructions

List milestones for a project

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

Input Schema

NameRequiredDescriptionDefault
workspaceNo
projectIdentifierYesProject key

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.5.1

TDQS

C2.8/5.0
Behavior2/5

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

The readOnlyHint annotation already declares this is a safe read, so the description's only added information is that results are scoped to a project — which the required projectIdentifier parameter already implies. Nothing is said about pagination, ordering, result volume, or what happens with an invalid/unknown project key.

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 no filler or repetition. It is efficient, though the brevity tips into under-specification rather than true conciseness.

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, read-only, two-parameter list tool with no output schema or nesting, the definition covers the essential purpose. However, with half the parameters undocumented and no return-value or pagination context, an agent cannot fully predict inputs or result shape from the description.

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 coverage is only 50%: projectIdentifier is documented as 'Project key', but workspace is completely undescribed in both schema and description. The description does not compensate at all — it never mentions workspace (is it a slug? a GUID? does it override the project's workspace?) nor adds any format detail for projectIdentifier beyond 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 ('List') and resource ('milestones') with the scoping qualifier 'for a project', which is enough to tell it apart from resource siblings like list_issues or list_labels. It stops short of naming a same-resource alternative or noting what differentiates it from other project-scoped listers.

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 guidance, no prerequisites, and no mention of alternatives despite a large catalog of list_* siblings. The agent must infer from the tool name alone that this is the milestones-only lister.

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

Deploy Server

Other Tools