Skip to main content
Glama

Import stack profile

import_stack_profile
Destructive

Create a stack profile from a ClusterInfrastructureAsCode YAML document (the twin of ankra stack-profiles import), publishing its first version - or, with as_draft, opening it as a builder draft a human reviews and publishes (the twin of ankra stack-profiles import --as-draft). Use this to bring a profile exported elsewhere into this organisation, or to stage a file-authored candidate for review; create_stack_profile builds one from a running stack instead.

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": {
      "iac_yaml_base64": "<iac_yaml_base64>"
    },
    "name": "import_stack_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoProfile name; defaults to the document's.
tagsNoTags for the profile.
as_draftNoOpen the document as a builder draft instead of publishing. When the organisation already has a profile with this name the draft attaches to it as the next-version candidate; otherwise it opens as a new-profile draft. The human then reviews, validates and publishes it (publish_stack_profile_draft). Defaults to false.
categoryNoProfile category.
changelogNoChangelog for the first published version. Ignored with as_draft: the changelog belongs to the publish the human makes after review.
descriptionNoProfile description.
iac_yaml_base64YesThe ClusterInfrastructureAsCode YAML (kind: ImportCluster, as export_stack_profile_iac produces), base64-encoded, at most 2 MiB.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Beyond the annotations it discloses real state effects: a first version is published, or with as_draft a draft is opened that a human must validate and publish via publish_stack_profile_draft, and an existing same-named profile causes the draft to attach as a next-version candidate. It also notes changelog is ignored in draft mode. It does not address the destructiveHint flag, i.e. what existing data a same-name import or publish could affect.

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?

Purpose and the publish-vs-draft fork are front-loaded, and the CLI-twin parentheticals help an agent map to known behavior. The single long first sentence is dense with nested clauses, which costs a bit of readability.

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 7-parameter mutating tool with full schema coverage and annotations, the description covers source format, both outcome modes, the human-review handoff, and the key alternative tool. It omits the return value and error conditions, but with no output schema that gap is modest rather than blocking.

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%, so all seven parameters are already documented in the schema, including as_draft's attach-vs-new behavior and the 2 MiB limit. The description reinforces the as_draft branching but adds little parameter-level meaning beyond what the schema states; baseline 3 applies.

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 ('Create a stack profile from a ClusterInfrastructureAsCode YAML document') plus the two outcome modes (publish first version vs. open a builder draft). It explicitly names the sibling it is not ('create_stack_profile builds one from a running stack instead'), so an agent can distinguish it without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives concrete when-to-use conditions: bringing a profile exported elsewhere into the organisation, or staging a file-authored candidate for review. It names the alternative (create_stack_profile) and the condition that selects it, and the schema links the source format to export_stack_profile_iac.

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.