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

mcp-github-project-manager

by kunwarVivek

Manage Sprints

manage_sprints
Destructive

Create, list, update, and delete project sprints; get the current sprint, add or remove issues, and retrieve metrics or planning data through an action-based interface.

Instructions

Manage Sprints: create, list, update, delete sprints (delete requires confirm: true); get current sprint; add/remove issues; get metrics and plan. 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_sprints"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleNo
actionYesThe sprint operation to perform
sprintNo
statusNo
confirmNodelete: must be true. Deleting a sprint removes the iteration from its project and clears it from every assigned item; it cannot be undone
endDateNo
issueIdsNo
sprintIdNo
projectIdNoProject ID (required for create — sprints are iteration fields on a specific project)
startDateNo
descriptionNo
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. Changed3 schema fields changedv4.0.0
    • changedInput schema / properties / action / enum
      Previous value: -[
      -  "create",
      -  "list",
      -  "get_current",
      -  "update",
      -  "add_issues",
      -  "remove_issues",
      -  "get_metrics",
      -  "plan"
      -]New value: +[
      +  "create",
      +  "list",
      +  "get_current",
      +  "update",
      +  "add_issues",
      +  "remove_issues",
      +  "get_metrics",
      +  "plan",
      +  "delete"
      +]
    • addedInput schema / properties / confirm
      Added value: +{
      +  "description": "delete: must be true. Deleting a sprint removes the iteration from its project and clears it from every assigned item; it cannot be undone",
      +  "type": "boolean"
      +}
    • 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

B3.1/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, openWorldHint=true, and idempotentHint=false, so the safety profile is carried structurally. The description's main behavioral note, 'delete requires confirm: true', duplicates the schema's own confirm parameter description, and it says nothing about permissions, per-action side effects, or the effect of idempotencyKey on retries.

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 tight block that is front-loaded with the operation list and ends with the dispatch instruction; nothing is padding. It loses a little by restating the title verbatim ('Manage Sprints:') before saying anything new.

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?

For a destructive multi-action dispatcher with no output schema and a nested object parameter, the description omits the most valuable information: which parameters are required for which action. A caller cannot tell from this text what `create` needs versus what `get_metrics` needs, and no return shape is hinted at.

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?

With 13 parameters, a nested sprint object, and only 31% schema description coverage, the description must compensate and largely does not: sprint, status, startDate/endDate, issueIds, includeIssues, and description are given no meaning at all. It only mirrors the delete-confirm rule and the action enumeration, both already present in the schema.

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?

Names a specific verb set plus resource ('create, list, update, delete sprints') and enumerates the operation surface (get current sprint, add/remove issues, get metrics and plan). An agent knows exactly what the tool covers, but it never distinguishes itself from plausible siblings such as manage_iterations or ai_plan, which likely overlap.

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?

It gives one piece of routing guidance — 'Use the `action` field to select the operation' — which tells the agent how to drive the dispatcher. There is no guidance on when to pick this tool over manage_iterations/ai_plan, and no per-action preconditions are stated.

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