Skip to main content
Glama

Export cluster IaC

export_cluster_iac
Read-only

Export the cluster's stacks as an Infrastructure-as-Code YAML document (the same export the cluster's IaC view serves). Use this to show, back up, or migrate the cluster's declarative configuration. Read-only.

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": {
      "cluster_id": "<cluster_id>"
    },
    "name": "export_cluster_iac"
  }
}

Input Schema

NameRequiredDescriptionDefault
cluster_idYesAnkra cluster id (UUID) the call targets. Discover ids with list_clusters.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

readOnlyHint=true already tells the agent this is a safe read, and the description's closing "Read-only." largely repeats that annotation. What it genuinely adds is the output shape (a YAML IaC document identical to the one the cluster IaC view serves), but it says nothing about size limits, whether secrets are redacted, or how large clusters are handled.

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?

Two sentences, front-loaded with the verb and resource, then the use cases. "Read-only" is a one-word near-duplicate of the annotation, but nothing else is wasted.

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?

For a one-parameter read-only exporter this covers purpose, output format, and intended scenarios; the mention of the YAML document compensates for the absence of an output schema. Redaction behavior and export size limits are the notable remaining gaps.

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% and the single cluster_id parameter is documented in the schema, including a pointer to list_clusters for discovery. The description adds no syntax, format, or constraint detail beyond the schema, so the baseline of 3 applies.

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 (export) and resource (the cluster's stacks), and clarifies the output is an IaC YAML document matching the cluster IaC view. This implicitly separates it from the sibling export_stack_profile_iac (profile vs cluster), though it never names that sibling explicitly.

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?

"Use this to show, back up, or migrate the cluster's declarative configuration" gives concrete use cases, which is more than most definitions offer. It stops short of stating when to prefer export_stack_profile_iac or what the caller should do instead if the export is too large, so there is no explicit exclusion.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.