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

mcp-github-project-manager

by kunwarVivek

AI Generation

ai_generate

Generate and enhance PRDs, parse requirements, expand features into tasks, analyze complexity, and build traceability matrices through an action-based AI workflow.

Instructions

AI-powered generation: generate/enhance/parse PRDs, add features, get next tasks, analyze complexity, expand tasks, create traceability matrices. 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": "ai_generate"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
tasksNo
actionYesThe AI generation operation to perform
authorNo
agentIdNo
assigneeNo
featuresNo
maxDepthNo
maxTasksNo
timelineNo
featureIdNo
projectIdNo
taskTitleNo
complexityNo
focusAreasNo
prdContentNo
teamSkillsNo
autoApproveNo
descriptionNo
featureIdeaNo
labelPrefixNoLabel prefix for materialized issues (e.g. "ai-generated")
maxSubtasksNo
projectIdeaNo
projectNameNo
projectTypeNo
requestedByNo
targetUsersNo
addToProjectNoWhether to add created issues to the specified projectId
autoEstimateNo
contextLevelNo
currentPhaseNo
includeRisksNo
stakeholdersNo
expandToTasksNo
maxComplexityNo
targetProjectNo
autoPrioritizeNo
excludeBlockedNo
projectContextNo
sprintCapacityNo
targetAudienceNo
teamExperienceNo
createLifecycleNo
currentEstimateNo
enhancementTypeNo
improveExistingNo
includeAnalysisNo
includeResearchNo
includeSubtasksNo
includeUseCasesNo
industryContextNo
taskDescriptionNo
validateQualityNo
includeBreakdownNo
includeEstimatesNo
targetComplexityNo
currentComplexityNo
addMissingElementsNo
enhancedGenerationNo
includeDependenciesNo
validateCompletenessNo
businessJustificationNo
autoDetectDependenciesNo
includeBusinessContextNo
includeRecommendationsNo
includeCoverageAnalysisNo
includeTechnicalContextNo
createTraceabilityMatrixNo
includeTraceabilityLinksNo
includeAcceptanceCriteriaNo
includeImplementationGuidanceNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv4.0.0
    • removedInput schema / properties / targetPRD
      Removed value: -{
      -  "type": "string"
      -}
  2. Addedv3.0.0

TDQS

C2.4/5.0
Behavior2/5

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

Annotations already disclose that the tool is not read-only, is open-world, is not idempotent, and is not destructive. The description adds no behavioral context beyond listing operation names; it does not explain which actions mutate data, what side effects occur, whether generated artifacts are persisted, or what authorization is required. For a nine-action mutation-capable tool, this is a significant gap.

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?

The description is a single front-loaded sentence with no filler, but the long comma-separated operation list is dense and provides no structure for routing between actions. It is concise to the point of being under-specified for a tool of this complexity.

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 71 parameters, nine distinct actions, no output schema, and mutation-capable behavior, the description is far too sparse. It lacks per-action guidance, parameter-to-action mapping, return expectations, and safety context, leaving the agent with almost no information beyond the action names.

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?

There are 71 parameters with only 4% schema description coverage, so the description must compensate heavily but does not. It only points at the `action` field, whose enum is already fully documented in the schema, and says nothing about how the dozens of other parameters map to specific actions. An agent cannot infer parameter meaning from this description.

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 a specific AI-generation resource and enumerates the supported operations (PRD generation/enhancement/parsing, feature addition, task selection, complexity analysis, task expansion, traceability matrices). This makes the tool's broad function clear. However, it does not differentiate this tool from siblings such as ai_plan or ai_analyze, which likely overlap in scope.

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?

The only usage instruction is to use the `action` field to select the operation, which is already evident from the schema. It provides no guidance on when to choose this tool over sibling AI tools, no prerequisites for individual actions, and no indication of which action fits which scenario beyond the action names themselves.

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