Skip to main content
Glama
Sign In
github-workflow-mcp

github-workflow-mcp

by GHeeJeon
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

get_pr_review_summary

Fetch and summarize all review comments from a GitHub pull request to quickly understand feedback.

Instructions

Fetch and summarise all review comments for a Pull Request.

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": {
      "pr_url": "<pr_url>"
    },
    "name": "get_pr_review_summary"
  }
}

Input Schema

NameRequiredDescriptionDefault
pr_urlYesFull GitHub PR URL (e.g. https://github.com/owner/repo/pull/42)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior2/5

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

No annotations are provided, so the description carries full burden. It does not specify behavior details such as the format of the summary, authentication requirements, rate limits, or handling of empty review comments.

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 sentence with no wasted words. It is front-loaded and efficient.

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

Completeness3/5

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

The tool has only one parameter and no output schema. The description gives a basic overview but lacks details on return format, error handling, or pagination, which would be useful for an agent.

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

Parameters3/5

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

Schema coverage is 100% for the single parameter, and the description repeats the schema's description. No additional semantic value beyond the schema.

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 clearly states the action ('Fetch and summarise') and the resource ('all review comments for a Pull Request'). It is specific and distinct from sibling tools like create_pr or list_labels.

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 implies the tool's purpose but does not explicitly state when to use it or when to avoid it. No alternatives or exclusions are mentioned.

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

Deploy Server

Other Tools