Skip to main content
Glama

List Milestones

list_milestones

Show all project milestones and their current status for a given project root, so you can check progress and identify what is pending or complete.

Instructions

Show all milestones and their status.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_milestones"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathNoProject root directory..

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden and does little: it never states that this is a read-only operation, whether it reads from the project-root files, what happens when no milestones exist, or whether the list is scoped/paginated. "Show all" hints at a full read but is not an explicit safety or behavior statement.

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 short, front-loaded sentence with zero filler, which is appropriate for a simple list tool. Its brevity is efficient, though it borders on under-specification rather than being optimally informative.

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?

An output schema exists, so return values need not be explained, and the sole parameter is schema-documented. However, for a tool in a project-management family with no annotations, the description omits where milestones come from, error behavior, and how it relates to add_milestone or the phase tools, leaving meaningful gaps.

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?

The single parameter (path, defaulting to ".") is fully documented in the schema, so baseline 3 applies. The description adds nothing about path resolution or what happens when a different root is supplied.

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?

"Show all milestones and their status" gives a clear verb (show/list) and resource (milestones) plus the extra detail that status is included, which goes slightly beyond the title. It does not differentiate from siblings such as add_milestone, list_phases, or list_tasks, so an agent gets a clear purpose but no routing signal.

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 guidance on when to call this versus alternatives like list_phases or list_tasks, and no mention of prerequisites such as an initialized project brain. The only implied usage is "want to see milestones," which the agent could infer from the name alone.

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