Skip to main content
Glama
MCP-OpenStack-Ops

MCP-OpenStack-Ops

by call518

Get Server Groups

get_server_groups

List all server groups with their details

Instructions

List all server groups with their details

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

Input Schema

NameRequiredDescriptionDefault
all_projectsNoIf True, include every project the credential's OpenStack policy allows (like 'openstack server group list --all-projects'); rows carry project_id and project_name. Requires ALLOW_CROSS_PROJECT_READ=true on the server; a disabled or denied request is reported as an error. Check scope.warning.

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, include every project the credential's OpenStack\npolicy allows (like 'openstack server group list --all-projects');\nrows carry project_id and project_name. Requires\nALLOW_CROSS_PROJECT_READ=true on the server; a disabled or denied\nrequest is reported as an error. Check scope.warning.",
      +  "type": "boolean"
      +}
  2. First observedv0.1.0

TDQS

C2.8/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 disclosure burden, and it discloses almost nothing: it does not state that the operation is read-only, does not mention that cross-project results require ALLOW_CROSS_PROJECT_READ=true or that denials surface as errors, and says nothing about result volume or scoping. "with their details" is the only hint about payload shape.

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?

A single short sentence with zero filler and the resource front-loaded. It is efficient, though its brevity shades into under-specification rather than tight precision.

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 values need not be explained, and the sole optional parameter is fully documented in the schema. For a low-complexity list tool this is largely sufficient; the remaining gap is that with no annotations the description should have stated the read-only nature and cross-project caveat itself.

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 all_projects parameter is documented thoroughly there, including the CLI analogue, the extra project_id/project_name columns, the server-side flag requirement, and the scope.warning signal. The description adds no parameter meaning of its own, which is acceptable at full coverage but is the baseline, not a contribution.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description has a specific verb and resource ("List all server groups"), so the basic action is unambiguous. However, "server groups" is never disambiguated from look-alike siblings such as get_security_groups, get_volume_groups, and get_identity_groups, and the agent gets no hint that these are Nova affinity/anti-affinity groups. Nothing distinguishes it from those alternatives.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no prerequisite statement, and no named alternative. The only conditional behavior in the whole definition (cross-project listing) lives in the parameter schema rather than in the description, so the agent must open the schema to learn it.

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