Skip to main content
Glama

Create stack profile draft

create_stack_profile_draft
Destructive

Start a stack profile BUILDER draft - the organisation-level reusable template composed on the Stack Profiles pages. Works without a selected cluster. Two modes: pass name (plus optional description/category/tags) to start a NEW profile from scratch, or pass profile_id to edit an EXISTING profile (resumes that profile's open draft when one exists; for a profile owned by another organisation this seeds a suggestion draft). Compose the draft with add_addon_to_stack_profile_draft / add_manifest_to_stack_profile_draft, inspect it with get_stack_profile_draft, then publish_stack_profile_draft. Nothing deploys.

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": "create_stack_profile_draft"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoName for the NEW profile draft. Must be unique among the organisation's open new-profile drafts and published profiles. Omit when editing an existing profile.
tagsNoTags for discovery (new profiles only; applied at publish).
categoryNoProfile category (e.g. 'monitoring', 'database'). Defaults to 'general' at publish.
profile_idNoUUID of the EXISTING profile to edit (alternative to name).
descriptionNoWhat this profile deploys and when to use it (new profiles only; applied at publish).

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 declare destructiveHint=true, and the description adds genuinely non-obvious behaviour: resuming a profile's open draft, cross-organisation calls seeding a suggestion draft rather than mutating the source, and "Nothing deploys." That last line slightly softens the destructive framing without contradicting it, though the description never explains what makes the call destructive.

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 and dense with actionable detail; the mode split is stated before the workflow chain. Minor waste in framing prose like "the organisation-level reusable template composed on the Stack Profiles pages," which adds little for an agent.

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

Completeness5/5

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

For a five-parameter, all-optional tool with no output schema, the description covers entry conditions, both invocation modes, follow-up steps, and the no-deploy guarantee. An agent has everything needed to call this correctly and continue the workflow.

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, and the description largely restates the schema's own name-vs-profile_id split rather than adding syntax, formats, or failure conditions. It confirms the mutual-exclusivity intent but contributes little the schema does not already say.

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 ("Start a stack profile BUILDER draft") and immediately qualifies it as an organisation-level reusable template distinct from a deployed stack. The workflow chain naming add_addon_to_stack_profile_draft, get_stack_profile_draft and publish_stack_profile_draft lets an agent place it in the sibling set without opening any schema.

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?

Explicitly defines the two modes: pass name for a NEW profile, or profile_id to edit an EXISTING one, and notes it works without a selected cluster. The gap is that it never contrasts this draft-based path with the non-draft create_stack_profile sibling, so the agent must infer when a draft is preferable to direct creation.

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.