Opsphere — DevOps & SRE Intelligence

GHE: List PRs

ghe_repo_prs

Read-only

List Pull Requests (latest N). Filter by state: open (default), closed, or all.

Input Schema

Name	Required	Description	Default
`repo`	Yes	Repository name or full owner/name slug. Prefer owner/name when known so routing never depends on a workspace default.
`limit`	No
`owner`	No	Optional GitHub org/user. A full repo slug (owner/name) takes precedence; otherwise the active workspace default org is used.
`state`	No		open
`context_id`	No	Optional explicit Connection Hub work context (ctx_*). Omit to use the conversation's active workspace; global Hub tools ignore it.

Output Schema

Name	Required	Description	Default
`ok`	Yes
`data`	Yes
`contractVersion`	Yes
`dataSchemaVersion`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed19 schema fields changedOct 26, 2026

changedOutput schema / properties / data / additionalProperties
```
Previous value: -trueNew value: +false
```
removedOutput schema / properties / data / properties / count
```
Removed value: -{
-  "type": "number"
-}
```

addedOutput schema / properties / data / properties / gaps

Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

removedOutput schema / properties / data / properties / issues

Removed value: -{
-  "$ref": "#/properties/data/properties/items"
-}

removedOutput schema / properties / data / properties / items

Removed value: -{
-  "items": {
-    "additionalProperties": true,
-    "properties": {},
-    "type": "object"
-  },
-  "type": "array"
-}

removedOutput schema / properties / data / properties / maxResults
```
Removed value: -{
-  "type": "number"
-}
```
removedOutput schema / properties / data / properties / nextPageToken
```
Removed value: -{
-  "type": [
-    "string",
-    "null"
-  ]
-}
```

addedOutput schema / properties / data / properties / pageInfo

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "hasMore": {
+      "type": "boolean"
+    },
+    "nextCursor": {
+      "type": "string"
+    },
+    "returned": {
+      "minimum": 0,
+      "type": "integer"
+    },
+    "total": {
+      "minimum": 0,
+      "type": "integer"
+    }
+  },
+  "required": [
+    "returned",
+    "hasMore"
+  ],
+  "type": "object"
+}

addedOutput schema / properties / data / properties / partial
```
Added value: +{
+  "type": "boolean"
+}
```

addedOutput schema / properties / data / properties / pullRequests

Added value: +{
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "author": {
+        "type": "string"
+      },
+      "baseRef": {
+        "type": "string"
+      },
+      "headRef": {
+        "type": "string"
+      },
+      "number": {
+        "type": "integer"
+      },
+      "state": {
+        "type": "string"
+      },
+      "title": {
+        "type": "string"
+      },
+      "url": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "number",
+      "title",
+      "state"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

addedOutput schema / properties / data / properties / repository
```
Added value: +{
+  "type": "string"
+}
```

removedOutput schema / properties / data / properties / results

Removed value: -{
-  "$ref": "#/properties/data/properties/items"
-}

removedOutput schema / properties / data / properties / startAt
```
Removed value: -{
-  "type": "number"
-}
```
removedOutput schema / properties / data / properties / total
```
Removed value: -{
-  "type": "number"
-}
```
addedOutput schema / properties / data / properties / truncated
```
Added value: +{
+  "type": "boolean"
+}
```

addedOutput schema / properties / data / properties / warnings

Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

addedOutput schema / properties / data / required

Added value: +[
+  "repository",
+  "pullRequests",
+  "partial",
+  "truncated",
+  "warnings",
+  "gaps"
+]

addedOutput schema / properties / dataSchemaVersion

Added value: +{
+  "const": 2,
+  "type": "number"
+}

changedOutput schema / required

Previous value: -[
-  "contractVersion",
-  "ok",
-  "data"
-]New value: +[
+  "contractVersion",
+  "dataSchemaVersion",
+  "ok",
+  "data"
+]

First observedOct 15, 2026

TDQS

B3.4/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=false, so the safety profile is covered. The description adds the useful 'latest N' ordering constraint but says nothing about pagination, rate limits, or result scope beyond state filtering.

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?

Two short sentences with no waste; the core capability and the filtering option are front-loaded. Terse but appropriately sized for a simple list tool.

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?

An output schema exists, so return values needn't be described. However, for a tool with 5 parameters and 60% schema coverage, the description leaves the owner/repo routing nuance and pagination behavior unaddressed, making it adequate but not complete.

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 60%, with the important repo and owner parameters already documented in the schema. The description restates the state enum values already present in the schema and hints at limit via 'latest N', adding little meaning beyond structured fields.

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?

States a specific verb and resource ('List Pull Requests') plus scope ('latest N'), which distinguishes it from the single-PR siblings like ghe_pr_detail, ghe_pr_diff, and ghe_pr_files. It doesn't explicitly name those siblings, but the list-vs-single distinction is clear.

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 state filter values and default ('open (default), closed, or all') imply when to use each mode, but there is no explicit guidance about when to prefer this over ghe_pr_detail or how it relates to the other PR tools. Usage is implied rather than stated.

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

All Opsphere — DevOps & SRE Intelligence tools Inspect

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

Need Help?