Skip to main content
Glama
kunwarVivek

mcp-github-project-manager

get_pull_request

Retrieve detailed information about a specific GitHub pull request by providing its number to support project management and code review workflows.

Instructions

Get details of a specific pull request

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pullNumberYes

Implementation Reference

  • Core implementation of get_pull_request tool: fetches detailed pull request information using GitHub REST API via Octokit
    async getPullRequest(data: {
      pullNumber: number;
    }): Promise<{ number: number; title: string; body: string; state: string; user: string; createdAt: string; updatedAt: string; mergeable: boolean | null }> {
      try {
        const octokit = this.factory.getOctokit();
        const config = this.factory.getConfig();
    
        const response = await octokit.rest.pulls.get({
          owner: config.owner,
          repo: config.repo,
          pull_number: data.pullNumber
        });
    
        return {
          number: response.data.number,
          title: response.data.title,
          body: response.data.body || '',
          state: response.data.state,
          user: response.data.user?.login || 'unknown',
          createdAt: response.data.created_at,
          updatedAt: response.data.updated_at,
          mergeable: response.data.mergeable
        };
      } catch (error) {
        throw this.mapErrorToMCPError(error);
      }
    }
  • Tool definition including schema, description, and examples for get_pull_request
    export const getPullRequestTool: ToolDefinition<GetPullRequestArgs> = {
      name: "get_pull_request",
      description: "Get details of a specific pull request",
      schema: getPullRequestSchema as unknown as ToolSchema<GetPullRequestArgs>,
      examples: [
        {
          name: "Get PR details",
          description: "Retrieve information about PR #42",
          args: {
            pullNumber: 42
          }
        }
      ]
    };
  • Registration of getPullRequestTool in the central ToolRegistry during built-in tools initialization
    this.registerTool(createPullRequestTool);
    this.registerTool(getPullRequestTool);
    this.registerTool(listPullRequestsTool);
    this.registerTool(updatePullRequestTool);
    this.registerTool(mergePullRequestTool);
    this.registerTool(listPullRequestReviewsTool);
    this.registerTool(createPullRequestReviewTool);
  • MCP server dispatch handler that routes get_pull_request calls to ProjectManagementService.getPullRequest
    case "get_pull_request":
      return await this.service.getPullRequest(args);
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool 'Get details', implying a read-only operation, but doesn't specify whether it requires authentication, rate limits, error conditions, or what details are returned. For a tool with zero annotation coverage, this is a significant gap in transparency.

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 appropriately sized and front-loaded with a single, clear sentence: 'Get details of a specific pull request'. There is zero waste, and every word contributes to the core purpose without unnecessary elaboration.

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?

Given the complexity (a read operation with one parameter), lack of annotations, and no output schema, the description is incomplete. It doesn't cover parameter semantics, behavioral traits like authentication needs, or return values. For a tool in this context, it should provide more guidance to be fully helpful.

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?

The description adds no meaning beyond the input schema. Schema description coverage is 0%, with one parameter 'pullNumber' undocumented. The description doesn't explain what 'pullNumber' is (e.g., an integer identifier), its format, or where to find it. It fails to compensate for the low schema coverage.

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 clearly states the tool's purpose: 'Get details of a specific pull request'. It uses a specific verb ('Get') and resource ('pull request'), and the qualifier 'specific' implies it retrieves one item by identifier. However, it doesn't explicitly differentiate from sibling tools like 'list_pull_requests' or 'update_pull_request', which would require 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 Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus alternatives. The description doesn't mention sibling tools like 'list_pull_requests' for multiple pull requests or 'update_pull_request' for modifications. It also lacks context on prerequisites, such as needing an existing pull request number.

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/kunwarVivek/mcp-github-project-manager'

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