Skip to main content
Glama
Claude Free Code MCP

Claude Free Code MCP

by ImIpscanning

github_pr_list

Read-only

List GitHub pull requests in your current repository using the gh CLI, with an optional limit. Requires gh authentication.

Instructions

List GitHub pull requests in the current repository using gh CLI (requires gh auth).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "github_pr_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo1..40

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is known. The description adds genuinely useful context beyond that: it shells out to gh CLI and requires gh auth. It says nothing about pagination, default ordering, or what happens when unauthenticated, which would matter for an open-world call.

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?

A single front-loaded sentence with no filler; the resource and the auth constraint are stated immediately, and nothing is repeated from structured fields.

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

Completeness5/5

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

For a simple read-only listing tool with full annotation coverage, a fully described single parameter and no output schema, this covers what an agent needs to invoke it correctly; only return-format details are absent, and those are minor here.

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?

Only one optional parameter (limit, default 15, range 1..40) and the schema description coverage is 100%, so the schema carries the semantics. The description adds no meaning about the limit or whether the list is capped/ordered.

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 gives a specific verb and resource ("List GitHub pull requests") plus a scope ("in the current repository"), which clearly separates it from github_pr_create. It stops short of naming a sibling explicitly, so differentiation relies on the verb alone.

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?

Usage is implied by the verb: call this to enumerate PRs, and the auth prerequisite is stated. There is no explicit when-not guidance or pointer to an alternative (e.g. create vs list vs issue_list), leaving routing inference to the agent.

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