Skip to main content
Glama

Get stack profile

get_stack_profile
Read-only

Get a stack profile's details: metadata, version history, and the contents of both the current (pinned) version and the latest version (addon names/charts/versions, manifest names, and the parameters each requires). Call this before instantiate_stack_profile and read the current_version entry - instantiation defaults to the current version, which can be older than latest after a rollback.

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

Input Schema

NameRequiredDescriptionDefault
profile_idNoUUID of the stack profile. Alternative to profile_name.
profile_nameNoName of the stack profile. Alternative to profile_id.

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 already declare readOnlyHint=true, so the safety profile is covered. The description adds real behavioral context beyond that: it returns two version snapshots rather than one, and it warns that current can be older than latest after a rollback, which materially affects how the agent interprets the result.

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?

Two sentences, both dense with information. The return contents are front-loaded and the workflow caveat follows immediately, with no filler or restatement of the title.

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?

There is no output schema, so the description carries the burden of describing return values, and it does so thoroughly (metadata, version history, per-version addon/manifest/parameter contents). Combined with the instantiation caveat, an agent has everything needed to call it and use the result correctly.

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 both parameters (profile_id, profile_name) are documented as alternatives in the schema itself. The description adds no lookup syntax, precedence rule for supplying both, or error behavior, so it neither compensates nor detracts; baseline 3 applies.

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?

The description names a specific verb and resource and enumerates exactly what is returned: metadata, version history, and the contents of both the current (pinned) and latest versions, including addon names/charts/versions, manifest names, and required parameters. That scope implicitly separates it from get_stack_profile_draft and list_stack_profiles, though no sibling is named explicitly.

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?

It states an explicit precondition ('Call this before instantiate_stack_profile') and tells the agent which field to read (current_version) and why: instantiation defaults to the current version, which can lag latest after a rollback. That is a concrete when-to-use rule plus a non-obvious caveat, not just implied context.

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.