Skip to main content
Glama

get_pull_request_comment

Retrieve specific pull request comment details from AtomGit repositories to review feedback and track discussion threads.

Instructions

Get details of a specific pull request comment

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ownerYes
repoYes
pull_numberYes
comment_idYes

Implementation Reference

  • The core handler function that executes the tool logic by making an HTTP GET request to the AtomGit API to retrieve the specified pull request comment.
    export async function getPullRequestComment(owner: string, repo: string, pull_number: number, comment_id: number) {
      return atomGitRequest(
        `https://api.atomgit.com/repos/${encodeURIComponent(owner)}/${encodeURIComponent(repo)}/pulls/${encodeURIComponent(pull_number)}/comments/${encodeURIComponent(comment_id)}`,
        {
          method: "GET",
        }
      );
    }
  • Zod schema defining the input parameters for the get_pull_request_comment tool: owner, repo, pull_number, and comment_id.
    export const GetPullRequestCommentSchema = z.object({
      owner: z.string(),
      repo: z.string(),
      pull_number: z.number(),
      comment_id: z.number(),
    });
  • index.ts:152-156 (registration)
    Tool registration in the MCP server's listTools response, specifying name, description, and input schema.
    {
      name: "get_pull_request_comment",
      description: "Get details of a specific pull request comment",
      inputSchema: zodToJsonSchema(pull.GetPullRequestCommentSchema),
    },
  • MCP server request handler case that parses arguments, calls the core handler, and formats the response.
    case "get_pull_request_comment": {
      const args = pull.GetPullRequestCommentSchema.parse(request.params.arguments);
      const result = await pull.getPullRequestComment(args.owner, args.repo, args.pull_number, args.comment_id);
      return {
        content: [{ type: "text", text: JSON.stringify(result, null, 2) }],
      };
    }
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. It states it 'gets details' but doesn't disclose behavioral traits like whether it's a read-only operation, what permissions are required, error handling, or the format of returned details. This leaves significant gaps for a tool with 4 parameters.

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 a single, efficient sentence with no wasted words. It's front-loaded with the core purpose, making it easy to parse quickly.

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 4 parameters with 0% schema coverage, no annotations, and no output schema, the description is incomplete. It lacks details on usage context, parameter meanings, behavioral expectations, and return values, making it inadequate for effective tool selection and invocation.

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 0%, so the description must compensate, but it adds no parameter information. It doesn't explain what 'owner', 'repo', 'pull_number', or 'comment_id' mean or how to obtain them, leaving all 4 parameters undocumented beyond their types 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?

The description clearly states the verb 'Get' and the resource 'details of a specific pull request comment', making the purpose understandable. However, it doesn't differentiate from sibling tools like 'get_pull_request_details' or 'get_issue_details', which follow similar patterns for different resources.

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 description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites like needing a specific comment ID or how it differs from other 'get' tools in the sibling list, such as 'get_pull_request_details' for broader pull request information.

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/kaiyuanxiaobing/atomgit-mcp-server'

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