Skip to main content
Glama

Add addon to stack profile draft

add_addon_to_stack_profile_draft
Destructive

Add a Helm chart addon to a stack profile builder draft. This composes the reusable template - nothing deploys and no cluster is needed. Auto-creates the namespace manifest and wires dependency parents. For secret values, never pass a real secret: use the literal string ANKRA_SECRET_PARAMETER as the value; it becomes a required secret input collected when the profile is deployed. Use ${variable_name} references for non-secret values the user should be able to customise per deployment.

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": {
      "chart_name": "<chart_name>"
    },
    "name": "add_addon_to_stack_profile_draft"
  }
}

Input Schema

NameRequiredDescriptionDefault
parentsNoNames of draft resources this addon depends on (deploy-order parents).
draft_idNoUUID of the stack profile builder draft. Defaults to the draft from the current page context, or the organisation's only open draft.
namespaceNoKubernetes namespace for the addon. Defaults to the chart name.
addon_nameNoInstance name for the addon. Defaults to the chart name.
chart_nameYesName of the chart to add (e.g. 'actualbudget', 'postgresql').
values_yamlNoHelm values as a YAML string.
chart_versionNoChart version to pin. Defaults to the latest version in the catalog.

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?

Annotations declare non-read-only and destructive, and the description adds meaningful behavior beyond that: auto-creation of the namespace manifest, wiring of dependency parents, and the fact that nothing actually deploys. The secret-handling contract (ANKRA_SECRET_PARAMETER sentinel) and ${variable} substitution rule are exactly the kind of operational context annotations cannot convey. It stops short of stating what happens on duplicate addon names or whether the operation is idempotent, which is notable given idempotentHint=false.

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?

Five sentences, each carrying a distinct payload: purpose, no-op scope, side effects, secret handling, variable substitution. The most critical constraint is not front-loaded as aggressively as it could be — the secret rule arrives last — but nothing is wasted or redundant.

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 mutation tool with no output schema, the description covers the operation's scope, side effects, and value-syntax rules well enough to call it correctly. The remaining gap is return/identity information — whether the agent gets back a created resource identifier — plus duplication behavior, which matters for a destructiveHint=true write.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description genuinely adds meaning to values_yaml by prescribing the ANKRA_SECRET_PARAMETER sentinel for secrets and ${variable_name} interpolation for customizable values — neither of which appears in the schema. The description also clarifies the indirect effect of 'parents' via auto-wiring, though it does not elaborate on the defaults the schema documents for namespace, addon_name, or chart_version.

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 pair ('Add a Helm chart addon to a stack profile builder draft') and implicitly distinguishes itself from add_manifest_to_stack_profile_draft by naming the addon resource and the Helm chart unit. An agent can tell exactly what object is being created and into what container.

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?

Explains that this is composition rather than deployment ('nothing deploys and no cluster is needed'), which tells the agent the operation is safe to call without a live cluster. It does not explicitly say when to prefer this over update_addon_in_stack_profile_draft or remove_addon_from_stack_profile_draft, so the alternative-selection guidance is only implied by the resource naming.

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.