Skip to main content
Glama

get-milestone-list

Read-onlyIdempotent

Retrieve a project's milestones to organize and track tasks by release or sprint, with optional filtering by open or closed status.

Instructions

Get list of milestones for a project.

Milestones are used to organize and track tasks by release or sprint. This tool retrieves all milestones in a project.

Note: Returns compact response with essential fields only.

URL Pattern Recognition: When given a Dooray URL like "https://nhnent.dooray.com/task/PROJECT_ID", extract the PROJECT_ID (the first numeric ID after "/task/") and use it as the projectId parameter.

Examples:

  • Get all milestones: {"projectId": "123456"}

  • Get only open milestones: {"projectId": "123456", "status": "open"}

  • Get only closed milestones: {"projectId": "123456", "status": "closed"}

Returns an array of milestones with id, name, and status. Use milestone IDs when creating or updating tasks.

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": {
      "projectId": "<projectId>"
    },
    "name": "get-milestone-list"
  }
}

Input Schema

NameRequiredDescriptionDefault
statusNoFilter by milestone status (open or closed)
projectIdYesProject ID to get milestones from

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, and idempotentHint, and the description adds genuinely new behavioral context: the response is a 'compact' projection with essential fields only, and the returned milestone IDs are what feed into task creation/update. It omits pagination/size limits, which keeps it short of a 5 for a list 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?

It is front-loaded with the core purpose, and the bold section headers ('Note', 'URL Pattern Recognition') make it scannable. There is mild redundancy — the compact-response note and the return-field sentence overlap, and the three examples largely mirror the status enum — but no sentence is purely filler.

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

Completeness5/5

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

With no output schema, the description compensates by stating the return shape (array of objects with id, name, status) and how those IDs are consumed downstream. For a two-parameter read-only list tool that is everything an agent needs to call it correctly.

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 description coverage is 100%, so both projectId and status are already documented, and the enum is spelled out in the schema; that sets the baseline at 3. The URL pattern section does add real value by explaining how to derive projectId from a Dooray task URL, but the enumerated examples otherwise restate the schema's enum without adding syntax or format detail.

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

Purpose5/5

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

The first sentence gives a specific verb and resource ('Get list of milestones for a project') and the second sentence adds scope by defining what milestones are used for. An agent can immediately distinguish this from the many sibling list tools (get-task-list, get-tag-list, etc.) because the returned resource and its containing scope are unambiguous.

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

Usage Guidelines4/5

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

Usage context is clear: fetch all milestones, or filter by open/closed, with three concrete call examples that map directly to the two parameters. It does not name an alternative tool to prefer in any situation, so it falls short of full when/when-not guidance, but the intended context is explicit.

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