Skip to main content
Glama
MCP OpenStack Operations Server

MCP OpenStack Operations Server

by E1i2e1122

get_heat_stack_details

Query a Heat stack’s resources, events, template, or outputs by stack name to inspect deployment details and troubleshoot operations.

Instructions

Query resources, events, template, or outputs for a Heat stack.

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": {
      "stack_name": "<stack_name>"
    },
    "name": "get_heat_stack_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
sectionNoDetail section to return: resources, events, template, or outputs.resources
stack_nameYesStack name or ID.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden and largely does not meet it. 'Query' implies read-only, but nothing states permission requirements, whether events or template output can be large/paginated, or what happens if the requested section is unavailable for the stack's current status.

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?

A single, front-loaded sentence that enumerates the selectable sections and names the target resource. Nothing is redundant or padded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is simple (2 parameters), the schema is fully documented, and an output schema exists, so return values need no explanation. However, for a detail tool sitting next to get_heat_stacks with no annotations, a sentence on section-specific behavior or the list-vs-detail relationship would make it complete.

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% — both parameters are fully described, including the section default of 'resources' and the accepted values. The description only restates the section list already present in the schema, adding no extra meaning such as format or behavior differences between sections.

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?

States a specific verb ('Query') and resource ('resources, events, template, or outputs for a Heat stack'), so an agent knows exactly what data comes back. It does not explicitly contrast itself with the sibling get_heat_stacks, which lists stacks rather than returning a stack's detail sections, so the distinction is inferable but not stated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

Usage is implied by 'for a Heat stack' — this is the per-stack detail tool, while get_heat_stacks is the listing tool — but the description never says when to choose one over the other or what prerequisites exist (e.g. stack must be in a settled state for template/outputs).

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