Skip to main content
Glama

Update addon in stack profile draft

update_addon_in_stack_profile_draft
Destructive

Update an addon inside a stack profile builder draft: Helm values (deep-merged by default, replace_values=true to replace), chart_version, namespace, or parents. Secrets rule: use ANKRA_SECRET_PARAMETER as the value for anything sensitive.

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": {
      "addon_name": "<addon_name>"
    },
    "name": "update_addon_in_stack_profile_draft"
  }
}

Input Schema

NameRequiredDescriptionDefault
parentsNoReplacement list of 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.
namespaceNoNew Kubernetes namespace; the namespace manifest is re-wired automatically.
addon_nameYesName of the addon to update.
values_yamlNoHelm values as a YAML string. Deep-merged over the current values unless replace_values is true.
chart_versionNoNew chart version to pin.
replace_valuesNoReplace the addon's values with values_yaml instead of deep-merging.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false and destructiveHint=true; the description adds real behavioral context beyond that by explaining the default deep-merge versus replace_values=true replacement semantics, that namespace changes re-wire the manifest automatically, and the secret-handling convention. It still does not explain what happens to fields omitted from the call or what the destructive path actually risks.

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?

A single dense sentence that front-loads the action and then enumerates fields, with the secrets rule appended as a clearly separable clause. It reads efficiently, though the parenthetical and colon-list packing make it slightly hard to scan.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Adequate for a 7-parameter mutation tool whose schema documents every parameter and whose annotations flag destructiveness. Gaps remain around draft lifecycle prerequisites, whether the addon must already exist in the draft, and error behavior for a destructive operation with no output schema.

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 baseline is 3; the description nonetheless reinforces the merge-vs-replace contract and adds a naming convention for sensitive values that the schema does not state. The remaining parameters (chart_version, namespace, parents) get no extra meaning beyond their schema text.

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?

Names a specific verb and resource ('Update an addon inside a stack profile builder draft') and enumerates the mutable fields (values, chart_version, namespace, parents), so the agent knows exactly what scope of change this covers. It does not differentiate itself from similarly named siblings such as update_addon_configuration or update_addon_settings, leaving that inference to the agent.

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

Usage Guidelines3/5

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

Provides one concrete usage rule ('use ANKRA_SECRET_PARAMETER as the value for anything sensitive'), which is genuinely actionable. However, it gives no guidance on when to choose this tool over update_addon_configuration/update_addon_settings, nor any prerequisite about draft state (e.g., must the draft be unpublished).

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.