Skip to main content
Glama

Update stack profile

update_stack_profile
Destructive

Update a stack profile's metadata: name, description, category, tags, or withdraw it from the marketplace. Does NOT change the profile's contents (use save_stack_profile_version for that). Visibility may only be NARROWED here: visibility='organisation' unpublishes a public profile. Publishing one is deliberately not offered - that widens cross-organisation exposure and stays with the admin-gated publish flow.

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": {
      "cluster_id": "<cluster_id>"
    },
    "name": "update_stack_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagsNoReplacement tag list.
categoryNoNew category.
new_nameNoNew name for the profile.
cluster_idYesAnkra cluster id (UUID) the call targets. Discover ids with list_clusters.
profile_idNoUUID of the profile to update. Alternative to profile_name.
visibilityNoSet to 'organisation' to withdraw a public profile from the marketplace. Reduces exposure only; this tool cannot make a profile public.
descriptionNoNew description.
profile_nameNoCurrent name of the profile to update. Alternative to profile_id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and readOnlyHint=false, but the description adds what is actually destroyed or changed: metadata only, with visibility restricted to narrowing so that visibility='organisation' unpublishes a public profile. It also explains why publishing is withheld, which prevents an agent from assuming a symmetric operation exists. It does not address confirmation requirements or side effects on existing shares, keeping it just short of a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three tight sentences, front-loaded with the scope, then the exclusion, then the exception rationale. Every clause carries information an agent needs to avoid a wrong call.

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 mutation tool with 8 parameters, full schema coverage, and no output schema, the description covers scope, exclusions, and the safety-relevant visibility restriction. Nothing needed to invoke it correctly is missing.

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% and each parameter already carries a description, so the baseline is 3. The description roughly restates the field list and reiterates the visibility narrowing semantics that the enum's schema description already provides, adding little new per-parameter meaning.

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 ('Update a stack profile's metadata') and enumerates the mutable fields: name, description, category, tags, and withdrawal from the marketplace. It explicitly separates itself from save_stack_profile_version, which handles contents, so an agent can distinguish the two 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 explicit when-not guidance ('Does NOT change the profile's contents - use save_stack_profile_version for that') and names the excluded capability (publishing) with the reason it is out of scope. The visibility constraint is spelled out as a rule rather than left to inference.

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.