Skip to main content
Glama
subhamyadav580

PR Reviewer MCP Server

get_pull_request_details

Retrieves pull request metadata including title, description, author, changed file count, additions, deletions, and commit count to assess PR scope before reviewing the diff.

Instructions

Get metadata for a specific pull request.

Returns title, description, author, changed file count, additions,
deletions, and commit count — useful for understanding PR scope before
reading the diff.

Args:
    repo_full_name: Full repo identifier in "owner/repo" format.
    pr_number: The pull request number.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
repo_full_nameYes
pr_numberYes
Behavior3/5

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

No annotations provided, so description must carry the burden. It correctly states it returns metadata (read-only) but lacks details on authorization, rate limits, or error conditions.

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 concise with two sentences and a structured args list, no unnecessary information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no output schema, it lists return fields and context. Could include more on error handling, but adequate for a simple metadata tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description adds meaning to both parameters: 'repo_full_name' format and 'pr_number' as the number, which the schema lacks (0% coverage).

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses specific verb 'get metadata' and names the resource 'pull request', listing returned fields. It clearly distinguishes from siblings by focusing on metadata vs diff or listing.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

The description suggests using before reading the diff, providing clear context. However, it does not explicitly state when not to use or compare alternatives.

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/subhamyadav580/pr-reviewer'

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