Skip to main content
Glama

List stack profiles

list_stack_profiles
Read-only

List reusable stack profiles (versioned stack templates) available to the organisation, including public profiles shared by other organisations, one compact page at a time. Returns: count, matching_count, page, next_page (null on the last page), note, and profiles [{name, category, visibility, latest_version, description abridged to ~90 characters with description_abridged: true when cut}]. Call again with page=next_page until it is null to see every profile; call get_stack_profile(profile_name) for the full description, id, tags, versions and parameters. ALWAYS check this before hand-building a stack with design_stack when the user asks for a 'standard', 'usual', or previously saved setup - instantiating an existing profile is preferred over rebuilding from charts.

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

Input Schema

NameRequiredDescriptionDefault
pageNoPage number, starting at 1; pass the previous result's next_page.
limitNoProfiles per page (1-12).
searchNoFilter profiles by name (case-insensitive substring match).
categoryNoFilter profiles by category (e.g. 'monitoring', 'general').

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only supply readOnlyHint=true, and the description carries the rest: pagination contract (next_page null on last page), the exact return envelope (count, matching_count, page, note, profiles[]), and the non-obvious truncation behavior ('description abridged to ~90 characters with description_abridged: true when cut'). It also discloses cross-organisation visibility of public profiles, which affects what the agent will see in results.

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?

Purpose is front-loaded and the dense bracketed return-field spec is justified because there is no output schema. The paragraph is long and packs three distinct concerns (return shape, pagination, sibling routing) into one block, which slightly hurts scannability but wastes little.

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?

Given no output schema, the description compensates by enumerating every returned field and the truncation flag, and it closes the loop on iteration and on the follow-up tool. An agent can call this correctly and knows exactly what to do with the result without consulting anything else.

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%, so all four parameters are already documented, and the description's page=next_page advice largely restates the schema's own wording. It adds nothing about the search/category filter interaction or about the fact that the schema declares limit default 15 while its description caps the range at 1-12 — an internal inconsistency the prose does not resolve.

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 plus scope: 'List reusable stack profiles (versioned stack templates) available to the organisation, including public profiles shared by other organisations'. It also defines the parenthetical concept so an agent unfamiliar with 'stack profile' understands the object, and it implicitly separates itself from get_stack_profile (detail) and design_stack (hand-building).

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 routing rules: call again with page=next_page until null, call get_stack_profile(profile_name) for full detail, and 'ALWAYS check this before hand-building a stack with design_stack when the user asks for a standard, usual, or previously saved setup'. Both the alternative tool and the triggering condition are named, plus a preference ordering (instantiate over rebuild).

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.