Skip to main content
Glama
MCP-OpenStack-Ops

MCP-OpenStack-Ops

by call518

Get Security Groups

get_security_groups

Get list of security groups with their rules.

Instructions

Get list of security groups with their rules.

Functions:

  • Query security groups and their rule configurations

  • Display ingress and egress rules with protocols and ports

  • Show remote IP prefixes and security group references

  • Provide comprehensive network security information

Use when user requests security group information, firewall rules, or network security queries.

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

Input Schema

NameRequiredDescriptionDefault
all_projectsNoIf True, list every security group Neutron shows the credential in any project (like 'openstack security group list --all-projects'). Requires ALLOW_CROSS_PROJECT_READ=true on the server. Neutron returns only what the credential may see, so 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, list every security group Neutron shows the\ncredential in any project (like 'openstack security group list\n--all-projects'). Requires ALLOW_CROSS_PROJECT_READ=true on the\nserver. Neutron returns only what the credential may see, so check\nscope.warning.",
      +  "type": "boolean"
      +}
  2. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations exist, so the description carries the full disclosure burden. It usefully reveals what the payload contains (ingress/egress rules, protocols, ports, remote IP prefixes, and security group references), but says nothing about permissions, the cross-project read requirement, or the scope.warning caveat—that only appears in the schema.

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 lead sentence is well front-loaded, but the four-bullet 'Functions' list largely restates it, and 'Provide comprehensive network security information' is empty filler. The usage sentence is the only unique value after the opener.

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?

With a single optional parameter fully documented in the schema and an output schema covering return values, the description does not need to explain payload structure. It is complete enough for correct invocation, with only the cross-project caveat left implicit.

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?

There is one optional parameter with 100% schema description coverage, and the schema already fully explains all_projects including the ALLOW_CROSS_PROJECT_READ requirement. The description adds no additional meaning about this flag, so the baseline of 3 applies.

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?

The description opens with a specific verb and resource: 'Get list of security groups with their rules.' That distinguishes it from the similarly named get_identity_groups, get_server_groups, and get_volume_groups by resource domain (network security groups), though it never states that distinction explicitly.

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?

'Use when user requests security group information, firewall rules, or network security queries' gives clear triggering context for invocation. It stops short of exclusions or naming an alternative tool for related queries, so it lacks the when-not guidance that would earn a 5.

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