Skip to main content
Glama
Sign In
spinnaker-mcp

spinnaker-mcp

by GeiserX
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Remote

Get cluster

get_cluster
Read-onlyIdempotent

Retrieve details for a specific Spinnaker cluster by application, account, and cluster name, including server groups, load balancers, instance counts, and metadata.

Instructions

Get details for a specific cluster in a Spinnaker application by account and cluster name. Use this to inspect server groups, load balancers, and instance counts within a cluster. Returns JSON with cluster metadata and its constituent server groups.

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>",
      "account": "<account>",
      "cluster_name": "<cluster_name>"
    },
    "name": "get_cluster"
  }
}

Input Schema

NameRequiredDescriptionDefault
accountYesSpinnaker account name
applicationYesApplication name as registered in Spinnaker
cluster_nameYesCluster name as shown in the Spinnaker UI

Output Schema

NameRequiredDescriptionDefault
countNoNumber of records in items.
itemsNoThe records, when Gate answered with a list.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.4.1
    • 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"
+}
  2. Changed1 schema field changedv0.3.4
    • changedInput schema / properties / cluster_name / description
      Previous value: -"Cluster name"New value: +"Cluster name as shown in the Spinnaker UI"
  3. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds the content dimension (cluster metadata, server groups, load balancers, instance counts), but that overlaps with the output schema rather than adding behavioral context like auth requirements or missing-cluster 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 core action and scope, with zero filler. Minor redundancy in restating the return payload that the output schema already defines.

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 annotations, a fully documented schema, and an output schema, the description supplies enough for correct invocation. Only the missing contrast with list_clusters and empty/missing-cluster behavior keep it from a 5.

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 100% with each parameter described, so the schema carries the parameter burden. The phrase 'by account and cluster name' slightly reinforces the composite key but adds no format or edge-case detail (e.g., wildcard or case sensitivity for cluster_name).

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 details for a specific cluster') and scopes it to a Spinnaker application keyed by account and cluster name. It implicitly contrasts with list_clusters via 'specific cluster,' but never names the sibling, so an agent must infer the distinction.

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?

'Use this to inspect server groups, load balancers, and instance counts within a cluster' gives implied usage, but there is no explicit when-not guidance or reference to the obvious alternative (list_clusters) for enumerating clusters.

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

Deploy Server

Other Tools