Skip to main content
Glama
MCP OpenStack Operations Server

MCP OpenStack Operations Server

by E1i2e1122

get_heat_stacks

List Heat orchestration stacks with status and creation/update timestamps to check infrastructure-as-code deployments and troubleshoot stack state.

Instructions

Get list of Heat orchestration stacks.

Functions:

  • Query Heat stacks and their current status

  • Display stack creation and update timestamps

  • Use get_heat_stack_details for templates, resources, events, or outputs

  • Provide orchestration deployment information

Use when user requests stack information, orchestration queries, or infrastructure-as-code status.

Returns: List of Heat stacks with detailed information in JSON format.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. 'Get list' implies read-only, and it discloses that status plus creation/update timestamps are included, but it says nothing about scope (all projects vs. current project), result volume, or ordering for a no-filter call that could return a large collection. That ambiguity matters more here because there are zero parameters to narrow the query.

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

Conciseness3/5

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

It is front-loaded with the core purpose in the first sentence, which is good, but the 'Functions:' bullets restate the same idea across four lines and 'Provide orchestration deployment information' is filler. The 'Returns:' block also duplicates information already available in the output schema.

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?

The tool is low complexity with zero parameters and an output schema, so return-value detail is already covered by structured data. What the description supplies — purpose, sibling routing, trigger conditions — is largely sufficient, with only the query scope left implicit.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes no parameters, so the baseline is 4 and there is nothing extra the description could usefully add. It correctly implies an unfiltered list rather than inventing options the schema doesn't support.

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?

The opening line names a specific verb and resource ('Get list of Heat orchestration stacks'), and the bullet list adds that it reports status and creation/update timestamps. Crucially, it names the sibling get_heat_stack_details as the tool for templates/resources/events/outputs, 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives an explicit trigger ('Use when user requests stack information, orchestration queries, or infrastructure-as-code status') and an explicit alternative for the detail case. What's missing is any exclusion for the no-argument nature of the call — e.g., whether it returns all stacks or only the caller's project.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.