spinnaker-mcp

Overview Schema Source Related Servers Discussions Admin

List pipeline configs

list_pipelines

Read-onlyIdempotent

Retrieve all pipeline configurations for a Spinnaker application to discover available pipelines before triggering or inspecting one. Returns JSON array with name, stages, triggers, and parameters.

Instructions

List all pipeline configurations for a Spinnaker application. Use this to discover available pipelines before triggering or inspecting a specific one. Returns JSON array of pipeline configuration objects with name, stages, triggers, and parameters.

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": {
      "application": "<application>"
    },
    "name": "list_pipelines"
  }
}

Input Schema

Name	Required	Description	Default
`application`	Yes	Application name as registered in Spinnaker

Output Schema

Name	Required	Description	Default
`count`	No	Number of records in items.
`items`	No	The records, when Gate answered with a list.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.4.1Nov 1, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "description": "The Gate response. A JSON object from Gate comes back as is; a JSON array comes back as {items, count}.",
+  "properties": {
+    "count": {
+      "description": "Number of records in items.",
+      "minimum": 0,
+      "type": "integer"
+    },
+    "items": {
+      "description": "The records, when Gate answered with a list.",
+      "type": "array"
+    }
+  },
+  "type": "object"
+}

First observedv0.1.0Apr 23, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so safety is covered structurally. The description adds that the result is a JSON array of configuration objects containing name, stages, triggers, and parameters, which tells the agent what a pipeline record looks like. It does not address pagination or result-size limits, which is a minor remaining gap.

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?

Three short sentences with zero waste: purpose, when to use, and return shape, in that order. Front-loaded with the verb and resource.

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 full annotation coverage, a fully documented single parameter, and an output schema, the description needs only to explain intent and routing, which it does. The only missing element is any note on result volume or pagination for an open-world listing tool.

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?

There is a single required parameter with 100% schema description coverage ('Application name as registered in Spinnaker'), so the schema carries the load. The description adds nothing about the application parameter's format or resolution beyond what the schema states — baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('List all pipeline configurations') scoped to a Spinnaker application, and implicitly contrasts itself with the singular 'get_pipeline' by framing discovery 'before triggering or inspecting a specific one'. An agent can distinguish it from siblings without opening the schema.

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

Usage Guidelines4/5

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

Explicitly frames the use case as discovery before triggering or inspecting a specific pipeline, which effectively points at get_pipeline as the follow-up alternative. There is no explicit exclusion clause (e.g., when to use list_strategies vs list_pipelines), but the context is clear.

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