Skip to main content
Glama
mcp-github-project-manager

mcp-github-project-manager

by kunwarVivek

Manage Milestones

manage_milestones
Destructive

Create, list, update, and delete GitHub milestones while tracking metrics, overdue items, and upcoming deadlines to keep project schedules on target.

Instructions

Manage Milestones: create, list, update, delete milestones; get metrics; find overdue and upcoming milestones. Use the action field to select the operation.

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": {
      "action": "<action>"
    },
    "name": "manage_milestones"
  }
}

Input Schema

NameRequiredDescriptionDefault
sortNo
limitNo
stateNo
titleNo
actionYesThe milestone operation to perform
statusNo
dueDateNo
daysAheadNo
directionNo
descriptionNo
milestoneIdNo
includeIssuesNo
idempotencyKeyNoIdempotency key (1-128 chars) for create actions: retrying with the same key and arguments returns the first result instead of creating a duplicate; reusing it with different arguments is an error. Kept for 24 hours.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv4.0.0
    • addedInput schema / properties / idempotencyKey
      Added value: +{
      +  "description": "Idempotency key (1-128 chars) for create actions: retrying with the same key and arguments returns the first result instead of creating a duplicate; reusing it with different arguments is an error. Kept for 24 hours.",
      +  "maxLength": 128,
      +  "minLength": 1,
      +  "type": "string"
      +}
  2. Addedv3.0.0

TDQS

C2.9/5.0
Behavior2/5

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

The annotations already declare destructiveHint=true and readOnlyHint=false, so the agent knows writes and deletions are possible. The description adds nothing beyond that: it does not say which of the seven actions mutate or destroy data, whether deletes cascade to linked issues, or what permissions are required. For a multi-action mutation tool this leaves the behavioral picture thin.

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?

Two compact sentences, operation list front-loaded, no filler or repetition of the title. It is arguably too terse for its complexity, but nothing present is wasteful.

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

Completeness2/5

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

This is a 13-parameter, seven-action dispatcher with no output schema and no per-action documentation, which puts a heavy burden on the description. The description does not tell the agent which parameters belong to which action, what each action returns, or how pagination via limit/sort/direction works. It is far from complete for a tool of this complexity.

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 only 15%, well under the 50% threshold, so the description must carry the load and does not. It identifies `action` as the selector but says nothing about the other 12 parameters — notably the redundant-looking `state` vs `status` enums, `daysAhead`, `includeIssues`, or which params are required per action. An agent must guess parameter applicability from enum names alone.

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 names the specific resource (milestones) and enumerates the concrete operations: create, list, update, delete, get metrics, get overdue, get upcoming. An agent immediately knows the tool's scope. It does not explicitly differentiate from siblings such as manage_iterations or manage_sprints, which keeps it from a 5.

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?

"Use the `action` field to select the operation" gives basic dispatcher guidance and the enumerated action list implies when each mode applies. However, there is no guidance on when to pick this tool over a sibling, no prerequisites, and no explanation of which parameters apply to which action (e.g., daysAhead only makes sense for get_upcoming).

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