Skip to main content
Glama
Sign In
spinnaker-mcp

spinnaker-mcp

by GeiserX
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Remote

Find images

find_images
Read-onlyIdempotent

Search Spinnaker machine images by cloud provider and filter by query, region, or account to locate deployment images or verify available versions.

Instructions

Search for machine images (AMIs, GCE images, Docker images) available in Spinnaker for a given cloud provider. Use this to find images for a deployment or verify which image versions are available. Supports filtering by query string, region, and account. Returns JSON array of matching image objects.

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": {
      "provider": "<provider>"
    },
    "name": "find_images"
  }
}

Input Schema

NameRequiredDescriptionDefault
countNoMaximum number of images to return (default: all Gate finds)
queryNoSearch query to filter images
regionNoCloud region to filter images
accountNoSpinnaker account to filter images
providerYesCloud provider (e.g. aws, gce, docker)

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. Changed2 schema fields changedv0.4.1
    • addedInput schema / properties / count
      Added value: +{
+  "description": "Maximum number of images to return (default: all Gate finds)",
+  "maximum": 1000,
+  "minimum": 1,
+  "type": "integer"
+}
    • 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

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is fully covered. The description adds the return format ('JSON array of matching image objects') and the filterable dimensions, but says nothing about pagination or how 'all Gate finds' limiting behaves when count is omitted.

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?

Four short sentences that front-load the resource definition before the usage hints and return format. Nothing is redundant, though the final sentence on return format is partly wasted 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 a complete input schema, an output schema, and rich annotations, the description only needs to establish purpose and usage, which it does. The gap is minor: no guidance on the closest sibling (get_image_tags) or on result limiting when count is omitted.

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 100%, so every parameter including count, query, region, account, and provider is already documented. The description restates three of the filters without adding syntax, format, or default behavior beyond the schema, which matches the baseline of 3.

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 with concrete examples (AMIs, GCE images, Docker images) scoped to a cloud provider. It is distinguishable from most siblings, though it never mentions the closely related get_image_tags sibling, leaving that boundary implicit.

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?

The sentence 'Use this to find images for a deployment or verify which image versions are available' gives a clear usage context. It stops short of naming when-not-to-use conditions or pointing to get_image_tags as the alternative for tags.

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