Skip to main content
Glama

Export stack profile IaC

export_stack_profile_iac
Read-only

Export one published version of a stack profile as a ClusterInfrastructureAsCode YAML document (the twin of ankra stack-profiles export-iac), with the parameters it declares. Use this to read a profile's full definition, to copy it into another organisation with import_stack_profile, or to keep it in Git. 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": {
      "profile_id": "<profile_id>",
      "version": "<version>"
    },
    "name": "export_stack_profile_iac"
  }
}

Input Schema

NameRequiredDescriptionDefault
versionYesThe published version number (from get_stack_profile).
profile_idYesThe stack profile id (UUID) from list_stack_profiles.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, and the description reinforces this with 'Read-only' while adding real context: only a *published* version can be exported (implying drafts are out of scope), and the result is a YAML document rather than a structured object. It stops short of describing size limits, error behavior for unpublished versions, or the response envelope.

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?

Two sentences, front-loaded with the action and output format, followed by concrete use cases. The CLI-twin parenthetical is the only discretionary element, and it earns its place for agents that reason in terms of the underlying CLI.

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 no output schema, the description correctly communicates that the return value is a YAML document for a single version, which is enough to call it correctly. It could note whether the YAML is returned inline versus written to a workspace file, but nothing essential is missing for a two-parameter read-only 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?

Schema description coverage is 100%, so both profile_id and version are documented in the schema, including where to source each value (list_stack_profiles, get_stack_profile). The phrase 'with the parameters it declares' is about content of the export rather than the tool's inputs and adds little meaning 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 (export), a specific resource (one published version of a stack profile), and the output format (ClusterInfrastructureAsCode YAML), and ties itself to the equivalent CLI command. This cleanly distinguishes it from siblings such as get_stack_profile, get_stack_profile_draft, export_cluster_iac, and import_stack_profile.

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 description gives three concrete usage contexts: reading a profile's full definition, copying it to another organisation via import_stack_profile, and archiving in Git. It does not explicitly say when to prefer get_stack_profile or how to handle drafts, but the pairing with import_stack_profile is a genuinely useful routing cue.

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.