Skip to main content
Glama
Sign In

Opsphere — DevOps & SRE Intelligence

by io.opsphere.mcp-cursor
OverviewDiscussionsAdmin

GHE Actions: Latest Run

ghe_actions_latest
Read-only

Get the latest workflow run of a repo (optionally filter by workflow/branch/event).

Input Schema

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

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 / 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 / repository
      Added value: +{
+  "type": "string"
+}
    • removedOutput schema / properties / data / properties / results
      Removed value: -{
-  "$ref": "#/properties/data/properties/items"
-}
    • addedOutput schema / properties / data / properties / run
      Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "conclusion": {
+      "type": "string"
+    },
+    "createdAt": {
+      "format": "date-time",
+      "type": "string"
+    },
+    "headBranch": {
+      "type": "string"
+    },
+    "headSha": {
+      "type": "string"
+    },
+    "id": {
+      "type": "integer"
+    },
+    "name": {
+      "type": "string"
+    },
+    "status": {
+      "type": "string"
+    },
+    "url": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "id"
+  ],
+  "type": "object"
+}
    • removedOutput schema / properties / data / properties / startAt
      Removed value: -{
-  "type": "number"
-}
    • addedOutput schema / properties / data / properties / status
      Added value: +{
+  "enum": [
+    "no_runs",
+    "found"
+  ],
+  "type": "string"
+}
    • 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",
+  "status",
+  "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.3/5.0
Behavior2/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 fully covered by structured data. The description adds nothing behavioral on top of that – no note on what 'latest' resolves to when multiple branches or events exist, and no failure behavior for repos with no runs. It largely restates the name and schema.

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?

One sentence, front-loaded with the action and resource, with the optionality qualifier immediately after. Nothing wasted.

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?

With an output schema present and annotations carrying the safety profile, the core is in place. However, the ambiguity of 'latest' (most recent across all branches vs. per-branch, tie-breaking, behavior with zero runs) is unaddressed, and that matters for an agent deciding whether to call this or the runs-list sibling.

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 67%, and the schema already documents repo, owner, workflow, and context_id with more detail than the description. The description only echoes the three filter parameters, adding no semantics (e.g., whether workflow accepts a filename path or a display name, or how event values map to GitHub event names). Baseline 3 is appropriate.

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 states a specific verb and resource ('Get the latest workflow run of a repo') with the scope qualifier 'latest' plus optional filter dimensions. That is enough to separate it from ghe_workflow_runs_list in spirit, but it never names that sibling explicitly, so the differentiation is left implicit.

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?

'Optionally filter by workflow/branch/event' implies the common usage pattern, but there is no statement of when to pick this over ghe_workflow_runs_list, ghe_actions_latest_jobs, or ghe_actions_diagnose. The agent must infer the routing from the word 'latest' alone.

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