Skip to main content
Glama
Sign In

Opsphere — DevOps & SRE Intelligence

by io.opsphere.mcp-cursor
OverviewDiscussionsAdmin

GHE: PR Changed Files

ghe_pr_files
Read-only

Get the COMPLETE list of files modified in a Pull Request with added/removed line statistics. Returns ALL files in the "files" array — always iterate over all elements.

Input Schema

NameRequiredDescriptionDefault
repoYesRepository name or full owner/name slug. Prefer owner/name when known so routing never depends on a workspace default.
ownerNoOptional GitHub org/user. A full repo slug (owner/name) takes precedence; otherwise the active workspace default org is used.
context_idNoOptional explicit Connection Hub work context (ctx_*). Omit to use the conversation's active workspace; global Hub tools ignore it.
pull_numberYesPull Request number

Output Schema

NameRequiredDescriptionDefault
okYes
dataYes
contractVersionYes
dataSchemaVersionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed19 schema fields changed
    • 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 / files
      Added value: +{
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "additions": {
+        "type": "integer"
+      },
+      "deletions": {
+        "type": "integer"
+      },
+      "path": {
+        "type": "string"
+      },
+      "status": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "path"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}
    • 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 / partial
      Added value: +{
+  "type": "boolean"
+}
    • addedOutput schema / properties / data / properties / pullNumber
      Added value: +{
+  "type": "integer"
+}
    • 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",
+  "pullNumber",
+  "files",
+  "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"
+]
  2. First observed

TDQS

B3.2/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 one genuinely useful behavioral fact — that the files array is not a truncated page and every element must be iterated — but says nothing about large-PR limits, renamed/deleted files, or ordering.

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, front-loaded with the verb and resource, with no filler. Minor redundancy in restating completeness twice ('COMPLETE list' / 'ALL files'), but both serve to prevent an early-exit mistake.

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?

An output schema exists, so return values need no explanation, and all four params are documented. For a read-only listing tool this is close to sufficient; only edge-case behavior on very large PRs or non-paginated result limits is left unstated.

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% across all four parameters, including the repo vs owner precedence and context_id semantics, so the schema does the heavy lifting. The description adds no parameter-level meaning beyond that, which is the correct baseline.

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 — get files modified in a Pull Request — plus what the payload contains (added/removed line statistics). It implicitly separates itself from ghe_pr_diff (patches) and ghe_pr_detail (metadata), but never names those siblings, so differentiation is left to inference.

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

Usage Guidelines2/5

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

There is no when-to-use statement, no prerequisite (e.g. pull_number must be resolved first) and no routing to alternatives such as ghe_pr_diff or ghe_pr_detail. The 'always iterate over all elements' line governs result consumption, not tool selection.

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 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