Skip to main content
Glama

Get stack profile draft

get_stack_profile_draft
Read-only

Read a stack profile BUILDER draft (the org-level template being composed on the Stack Profiles pages). Returns the draft's stack contents (addons with their Helm values, manifests, variables), its parameters, the publish validation verdict, and the builder path. Works without a selected cluster. Defaults to the organisation's only open draft; pass draft_id when several exist (the page context carries the open draft's id when the user is in the builder). Call this first when the user is on a stack profile page, and again after draft edits to verify them.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_stack_profile_draft"
  }
}

Input Schema

NameRequiredDescriptionDefault
draft_idNoUUID of the stack profile builder draft. Defaults to the draft from the current page context, or the organisation's only open draft.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered; the description adds genuinely new context: it works without a selected cluster, how the default draft is resolved, and what the payload contains (addons with Helm values, manifests, variables, parameters, publish validation verdict, builder path). It stops short of saying whether drafts are auto-created or what happens when no open draft exists.

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?

Front-loaded with the core purpose, then return contents, then usage triggers; no filler sentences. Slightly dense, with two parenthetical asides that could be trimmed, but every sentence contributes information.

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?

There is no output schema, so the description carries the burden of enumerating return fields, which it does explicitly. For a single-optional-parameter read tool with annotations present, this is nearly complete; only edge cases (no open draft, unpublished/invalid state) are unaddressed.

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 the baseline is 3. The description restates the same default-resolution behavior already documented in the schema ('defaults to the organisation's only open draft') and only modestly extends it with the when-to-supply condition ('pass draft_id when several exist'), so it adds little beyond structured data.

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 ('Read a stack profile BUILDER draft') and immediately qualifies it as the org-level template being composed, which distinguishes it from the published-profile siblings (get_stack_profile, list_stack_profiles). The parenthetical 'the org-level template being composed' removes ambiguity about which artifact is returned.

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?

Gives concrete trigger conditions: 'Call this first when the user is on a stack profile page' and 'again after draft edits to verify them', plus the rule for passing draft_id when several drafts exist. It does not explicitly name a sibling to avoid (e.g. get_stack_profile for published profiles), leaving a small inference gap.

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.