Skip to main content
Glama
Sign In

OrionBI

by ai.orionbi
OverviewDiscussionsAdmin

List GitHub pull requests

github_list_pull_requests
Read-only

List pull requests in a repository you can access (your own or a shared GitHub connection). Returns up to 50 PRs. Filter by state (open, closed, all).

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": {
      "repo": "<repo>"
    },
    "name": "github_list_pull_requests"
  }
}

Input Schema

NameRequiredDescriptionDefault
repoYesRepository in "owner/repo" form, e.g. octocat/Hello-World. The owner is the GitHub LOGIN exactly as it appears in the repository URL (github.com/<owner>/<repo>) — not a display name, and not the connection's name.
stateNoPull request state filter (default open).
connectionNoWhich GitHub connection to use, by its name from github_list_connections. This is a local label for the connection, NOT a GitHub username — for anything GitHub has to resolve, use that connection's login instead. Optional when you have exactly one.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds two facts beyond them: the result cap ("Returns up to 50 PRs") and the connection-access scoping, both of which affect how an agent plans a call. It stops short of saying whether the 50 cap is a hard limit or whether pagination exists to get beyond it.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences with the core action front-loaded and no filler. The third sentence largely repeats the schema's state enum, which is mild redundancy but not damaging.

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?

For a simple read-only list tool with full schema coverage and clear annotations, the description supplies the essentials: resource, access scope, and result cap. The remaining gap is pagination or how to retrieve results past the 50-item cap, which an agent would need to know for large repositories.

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 description coverage is 100%, so repo, state, and connection are already well documented in the schema, including the owner/login caveats. The description only restates the state values (open, closed, all), which duplicates the enum rather than adding meaning. Baseline 3 applies when the schema carries the parameter burden.

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 opens with a specific verb and resource ("List pull requests in a repository") plus the access scope (own or shared connection), so an agent can tell it apart from github_get_issue or github_list_issues by resource type. It does not explicitly name a sibling, which keeps it from 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 Guidelines3/5

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

Usage context is implied by "in a repository you can access (your own or a shared GitHub connection)" and the state filter hint, but there is no explicit when-to-use or when-not-to-use guidance versus github_get_issue (single PR) or github_search_code. An agent must infer that this is the enumeration path rather than the lookup path.

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

All OrionBI toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources