Skip to main content
Glama

list_milestones

Retrieve GitHub project milestones to track progress and manage deadlines. Filter by status and customize sorting for project oversight.

Instructions

List milestones

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
statusYes
sortNo
directionNo

Implementation Reference

  • Main handler function that executes the list_milestones tool: fetches milestones from repository, applies status filter, sorts by specified criteria (due_date, title, created_at), and returns the list.
    async listMilestones(
      status: string = 'open',
      sort: string = 'created_at',
      direction: string = 'asc'
    ): Promise<Milestone[]> {
      try {
        // Get all milestones
        const milestones = await this.milestoneRepo.findAll();
    
        // Filter by status if needed
        let filteredMilestones = milestones;
        if (status !== 'all') {
          const resourceStatus = status === 'open' ? ResourceStatus.ACTIVE : ResourceStatus.CLOSED;
          filteredMilestones = milestones.filter(milestone => milestone.status === resourceStatus);
        }
    
        // Sort the milestones
        filteredMilestones.sort((a, b) => {
          let valueA, valueB;
    
          switch(sort) {
            case 'due_date':
              valueA = a.dueDate || '';
              valueB = b.dueDate || '';
              break;
            case 'title':
              valueA = a.title;
              valueB = b.title;
              break;
            case 'created_at':
            default:
              valueA = a.createdAt;
              valueB = b.createdAt;
          }
    
          const comparison = valueA.localeCompare(valueB);
          return direction === 'asc' ? comparison : -comparison;
        });
    
        return filteredMilestones;
      } catch (error) {
        throw this.mapErrorToMCPError(error);
      }
    }
  • Zod schema defining the input arguments for the list_milestones tool: status (open/closed/all), sort (due_date/title/created_at), direction (asc/desc).
    // Schema for list_milestones tool
    export const listMilestonesSchema = z.object({
      status: z.enum(["open", "closed", "all"]).default("open"),
      sort: z.enum(["due_date", "title", "created_at"]).default("created_at").optional(),
      direction: z.enum(["asc", "desc"]).default("asc").optional(),
    });
    
    export type ListMilestonesArgs = z.infer<typeof listMilestonesSchema>;
  • Registers the listMilestonesTool as part of the milestone tools in the central ToolRegistry singleton.
    // Register milestone tools
    this.registerTool(createMilestoneTool);
    this.registerTool(listMilestonesTool);
    this.registerTool(updateMilestoneTool);
    this.registerTool(deleteMilestoneTool);
  • Repository method that executes GraphQL query to fetch all milestones from GitHub and maps them to domain Milestone objects.
    async findAll(): Promise<Milestone[]> {
      const query = `
        query($owner: String!, $repo: String!) {
          repository(owner: $owner, name: $repo) {
            milestones(first: 100) {
              nodes {
                id
                number
                title
                description
                dueOn
                state
                createdAt
                updatedAt
              }
            }
          }
        }
      `;
    
      const response = await this.graphql<ListMilestonesResponse>(query, {
        owner: this.owner,
        repo: this.repo,
      });
    
      return response.repository.milestones.nodes.map(milestone => 
        this.mapGitHubMilestoneToMilestone(milestone)
      );
    }
  • MCP tool dispatch handler that routes list_milestones calls to the ProjectManagementService.
    case "list_milestones":
      return await this.service.listMilestones(args.status, args.sort, args.direction);
Behavior1/5

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

No annotations are provided, so the description must fully disclose behavioral traits. 'List milestones' implies a read-only operation but offers no details on permissions, rate limits, pagination, error handling, or what the output contains. For a tool with parameters and no output schema, this lack of behavioral context is inadequate and leaves critical operational aspects unspecified.

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

Conciseness5/5

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

The description is extremely concise with only two words, making it front-loaded and free of unnecessary verbiage. While under-specified, it does not waste space on redundant or irrelevant information, adhering strictly to a minimalistic structure.

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

Completeness1/5

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

Given the tool's complexity (3 parameters, 1 required, no schema descriptions, no output schema, and no annotations), the description is severely incomplete. It does not address parameter meanings, behavioral expectations, output format, or differentiation from siblings. For a listing tool with filtering capabilities, this minimal description fails to provide the necessary context for effective use.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema description coverage is 0%, meaning none of the three parameters (status, sort, direction) are documented in the schema. The description 'List milestones' adds no information about these parameters—it does not explain what 'status' represents, what sorting options exist, or how 'direction' affects results. This fails to compensate for the complete lack of schema documentation.

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 description 'List milestones' is a tautology that restates the tool name without adding meaningful context. It specifies the verb 'list' and resource 'milestones' but lacks any distinguishing details about scope, filtering, or how it differs from sibling tools like 'get_milestone_metrics', 'get_overdue_milestones', or 'get_upcoming_milestones'. This minimal statement fails to clarify what specific aspect of milestones is being listed.

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?

The description provides no guidance on when to use this tool versus alternatives. It does not mention any context, prerequisites, or exclusions, nor does it reference sibling tools that might serve similar purposes (e.g., 'get_overdue_milestones' for filtered lists). Without such information, an agent cannot determine appropriate usage scenarios.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/HarshKumarSharma/MCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server