Skip to main content
Glama
MCP-OpenStack-Ops

MCP-OpenStack-Ops

by call518

Get Heat Stacks

get_heat_stacks

Get list of Heat orchestration stacks.

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.

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
all_projectsNoIf True, list stacks of every project (like 'openstack stack list --all-projects'); rows carry project_id and project_name. Requires ALLOW_CROSS_PROJECT_READ=true on the server. Heat's default policy denies this even to administrators, so a policy-denial error is the usual result unless the operator allows stacks:global_index.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv3.9.2
    • addedInput schema / properties / all_projects
      Added value: +{
      +  "default": false,
      +  "description": "If True, list stacks of every project (like 'openstack\nstack list --all-projects'); rows carry project_id and\nproject_name. Requires ALLOW_CROSS_PROJECT_READ=true on the server.\nHeat's default policy denies this even to administrators, so a\npolicy-denial error is the usual result unless the operator allows\nstacks:global_index.",
      +  "type": "boolean"
      +}
  2. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It discloses that results include status and timestamps, but says nothing about default project scoping (the tool lists only the current project unless all_projects is set), permission requirements, result limits/paging, or ordering — the cross-project caveat lives only in the parameter schema, not the description.

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?

The opening line and trigger line are well front-loaded, but the 'Functions:' bullet list is partly redundant with the opening sentence, and 'Provide orchestration deployment information' is vague filler that restates the purpose without adding detail.

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?

An output schema exists, so return-value description is unnecessary, and the tool's single optional parameter is fully documented in the schema. What remains thin is behavioral context an agent would want for a no-annotation read tool — chiefly that the default scope is the current project only.

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% and the single parameter's schema entry already explains the cross-project behavior, the ALLOW_CROSS_PROJECT_READ requirement, and the typical policy-denial outcome. The description adds no meaning beyond that, so the baseline of 3 applies.

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 first sentence names a specific verb and resource ('Get list of Heat orchestration stacks'), and the bullet list scopes it to status plus creation/update timestamps. It explicitly names the sibling 'get_heat_stack_details' as the tool for templates, resources, events, and outputs, so an agent can separate 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?

The final line gives concrete trigger conditions ('stack information, orchestration queries, or infrastructure-as-code status'), and the third bullet supplies the explicit alternative with the condition that selects it (details/templates/resources/events/outputs). Both when-to-use and where-to-go-instead are stated, not inferred.

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