Opsphere — DevOps & SRE Intelligence

Diagnosticar pipeline fallido

bb_pipeline_diagnose

Read-only

Identify which step failed in a pipeline and show its log. Without UUID it automatically finds the last failed pipeline. Returns: pipeline info, list of steps, and logs of the failed steps.

Input Schema

Name	Required	Description
`repo`	Yes	Repo slug
`uuid`	No	UUID del pipeline (omitir para usar el último fallido)
`branch`	No	Filtrar por rama al buscar el último fallido
`tailLines`	No	Líneas de log a mostrar por step fallido
`workspace`	No
`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.

Changed16 schema fields changedOct 26, 2026

changedOutput schema / properties / data / additionalProperties
```
Previous value: -trueNew value: +false
```
removedOutput schema / properties / data / properties / failedSteps / $ref
```
Removed value: -"#/properties/data/properties/steps"
```

addedOutput schema / properties / data / properties / failedSteps / items

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "log": {
+      "type": "string"
+    },
+    "step": {
+      "additionalProperties": false,
+      "properties": {
+        "name": {
+          "type": "string"
+        },
+        "uuid": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "uuid"
+      ],
+      "type": "object"
+    }
+  },
+  "required": [
+    "step",
+    "log"
+  ],
+  "type": "object"
+}

addedOutput schema / properties / data / properties / failedSteps / type
```
Added value: +"array"
```
changedOutput schema / properties / data / properties / pipeline / additionalProperties
```
Previous value: -trueNew value: +false
```
addedOutput schema / properties / data / properties / pipeline / properties / result
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / data / properties / pipeline / properties / state
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / data / properties / pipeline / properties / uuid
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / data / properties / pipeline / required
```
Added value: +[
+  "uuid"
+]
```
removedOutput schema / properties / data / properties / steps / items / $ref
```
Removed value: -"#/properties/data/properties/pipeline"
```
addedOutput schema / properties / data / properties / steps / items / additionalProperties
```
Added value: +false
```

addedOutput schema / properties / data / properties / steps / items / properties

Added value: +{
+  "name": {
+    "type": "string"
+  },
+  "result": {
+    "type": "string"
+  },
+  "uuid": {
+    "type": "string"
+  }
+}

addedOutput schema / properties / data / properties / steps / items / required
```
Added value: +[
+  "uuid"
+]
```
addedOutput schema / properties / data / properties / steps / items / type
```
Added value: +"object"
```

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

A3.5/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds meaningful behavior by disclosing the automatic last-failed-pipeline selection and the shape of the response, but it omits failure cases such as no failed pipeline found and any log truncation behavior.

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, front-loaded with the action and then the default behavior. The return-value sentence is brief and useful, though slightly redundant given an output schema exists.

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?

With an output schema and strong parameter coverage, the description covers the essential behavior: what it finds, the UUID default, and the response contents. It would be stronger with an edge-case note about missing failed pipelines or the branch filter.

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 83%, so the schema already documents most parameters. The description restates the UUID-omission behavior, which the schema also says ('omitir para usar el último fallido'), and adds little beyond that; 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?

States a specific verb and resource: identify the failed step and show its log. That is clearly distinct from bb_pipeline_get (fetch a pipeline) and bb_pipelines_latest (list recent pipelines), even though no sibling is named explicitly.

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?

Gives one useful usage condition: without a UUID it automatically finds the last failed pipeline. It does not say when to prefer this over bb_pipeline_get or bb_pipelines_latest, nor what to do when no failed pipeline exists.

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?