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

mcp-github-project-manager

by kunwarVivek

Manage Status Updates

manage_status_updates

Create, list, and retrieve GitHub project status updates to track progress, risks, and completion across projects and report current status clearly.

Instructions

Manage project Status Updates: create, list, and get status updates. 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_status_updates"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyNo
afterNo
firstNo
actionYesThe status update operation to perform
cursorNoCursor from a previous page's `nextCursor`; omit for the first page
statusNo
projectIdNo
startDateNo
targetDateNo
statusUpdateIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv4.0.0
    • addedInput schema / properties / cursor
      Added value: +{
      +  "description": "Cursor from a previous page's `nextCursor`; omit for the first page",
      +  "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?

Annotations already declare that this is mutating (readOnlyHint=false), open-world, non-idempotent, and non-destructive, but the description adds no behavioral context beyond that. It does not mention permissions, side effects of create, or how list pagination behaves.

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 short sentences with no filler, and the operation list is front-loaded. The extreme brevity leaves gaps, but the wording itself is efficient and easy to parse.

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 10-parameter tool with three distinct actions and no output schema, this definition is far too thin. An agent cannot infer required parameters per action or what a successful response will contain.

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 20%, and the description explains only the already-documented `action` field. It does not clarify the roles of body, status, projectId, startDate, targetDate, statusUpdateId, first, or after, nor which parameters apply to which action.

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 resource (project Status Updates) and enumerates create, list, and get, so an agent can tell what the tool does. It does not distinguish this tool from related siblings or clarify the scope of 'project'.

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 description only says to use the `action` field to select the operation, which is an invocation instruction rather than guidance on when to choose this tool over alternatives. No when-not conditions, prerequisites, or sibling comparisons are given.

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