Skip to main content
Glama

list_milestones

Lists a project's milestones in order with goals, acceptance checks, ticket progress, completion status, and failed check details to guide work one milestone at a time and flag tickets to open.

Instructions

The project's milestones in order: name, goal, acceptance checks, check_results (each check's n, for crew or person, and its latest result), how many tickets and how many are done, which are ready, whether the milestone is finished and accepted, and crew_to_run (the crew checks not recorded yet) and crew_failed / person_wrong (failed ones: open a ticket for each, where the project's tickets live). Work one milestone at a time, in this order.

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
projectNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.57.0

TDQS

B3.1/5.0
Behavior3/5

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

With no annotations, the description carries the full burden; it discloses a useful behavioral consequence ('crew_failed / person_wrong ... open a ticket for each'), which is real guidance beyond a bare schema. However it never states that the call is read-only, what the empty `project` default means (all projects vs. a current project), or anything about volume/pagination for large milestone sets.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

There is no filler — every clause conveys return-field semantics or a workflow instruction — but it is delivered as one long run-on sentence dense with backticks and nested parentheticals. Purpose is not front-loaded; the reader has to parse the whole sentence to learn it is a listing call.

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 the lengthy enumeration of return fields is partly redundant, yet the added semantics (crew_to_run = crew checks not recorded yet, crew_failed/person_wrong remediation) are genuine value. What is missing is proportionate to the tool's simplicity: the lone parameter's behavior and any indication that this is a non-mutating read are not stated.

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 0% and the single `project` parameter (optional, default empty string) is never mentioned in the description beyond the possessive phrase 'The project's milestones'. The agent cannot tell whether omitting it lists every project's milestones or scopes to a default project, which is exactly the meaning the description should have 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?

The opening clause identifies the resource and its ordering ('The project's milestones in order') and the rest enumerates what each milestone carries, so an agent knows this is a read that returns ordered milestone records. It is specific to milestones and distinguishable from list_projects/list_tickets, but it opens with a noun phrase rather than a verb, so the purpose must be inferred from the tool name.

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

Usage Guidelines3/5

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

The closing line gives workflow guidance — 'Work one milestone at a time, in this order' — which tells the agent how to sequence work over results. There is no explicit statement of when to call this versus a sibling tool, no prerequisites, and no exclusion conditions, so usage is only implied.

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