Skip to main content
Glama
Sign In
spinnaker-mcp

spinnaker-mcp

by GeiserX
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Remote

List subnets

list_subnets
Read-onlyIdempotent

Discover available subnets by cloud provider across Spinnaker accounts to configure server groups or deployment targets, returning CIDR, availability zone, and VPC association.

Instructions

List all subnets for a given cloud provider across Spinnaker accounts. Use this to discover available subnets when configuring server groups or deployment targets. Returns JSON array of subnet objects with CIDR, availability zone, and VPC association.

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": {
      "cloud_provider": "<cloud_provider>"
    },
    "name": "list_subnets"
  }
}

Input Schema

NameRequiredDescriptionDefault
cloud_providerYesCloud provider (e.g. aws, gce, kubernetes)

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. First observedv0.1.0

TDQS

A4.3/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 behavior is covered. The description adds useful context by noting cross-account scope and the JSON array return shape with CIDR, AZ, and VPC fields, though it does not discuss pagination or limits.

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 tight sentences with no wasted language. Purpose is front-loaded, followed by usage context and return shape.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter read-only list tool with rich annotations and an output schema, the description supplies everything needed: scope, use case, and return contents. No material gaps remain.

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?

The input schema has 100% description coverage and already documents cloud_provider with examples like aws, gce, and kubernetes. The description reinforces the parameter's role but adds no syntax or constraints beyond the schema.

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 subnets') and scopes it to a cloud provider across Spinnaker accounts. An agent can distinguish it from sibling list tools such as list_networks or list_firewalls by the resource named.

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?

Provides clear usage context: 'Use this to discover available subnets when configuring server groups or deployment targets.' It does not explicitly name alternatives or exclusions, but the intended situation is unambiguous.

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