Skip to main content
Glama
MCP-OpenStack-Ops

MCP-OpenStack-Ops

by call518

Get Network Details

get_network_details

Provides detailed information for OpenStack networks, subnets, routers, and security groups.

Instructions

Provides detailed information for OpenStack networks, subnets, routers, and security groups.

Functions:

  • Query configuration information for specified network or all networks

  • Check subnet configuration and IP allocation status per network

  • Collect router connection status and gateway configuration

  • Analyze security group rules and port information

Use when user requests network information, subnet details, router configuration, or network troubleshooting.

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

Input Schema

NameRequiredDescriptionDefault
all_projectsNoIf True, list every network Neutron shows the credential in any project (like 'openstack network list' as an administrator); use only with network_name "all". Requires ALLOW_CROSS_PROJECT_READ=true on the server. Neutron returns only what the credential may see, so check scope.warning.
network_nameNoName of network to query or "all" for all networks (default: "all")all

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 network Neutron shows the credential\nin any project (like 'openstack network list' as an administrator);\nuse only with network_name \"all\". Requires\nALLOW_CROSS_PROJECT_READ=true on the server. Neutron returns only\nwhat the credential may see, so check scope.warning.",
      +  "type": "boolean"
      +}
  2. Changed1 schema field changedv3.5.8
    • addedInput schema / properties / network_name / description
      Added value: +"Name of network to query or \"all\" for all networks (default: \"all\")"
  3. 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 are supplied, so the description carries the burden. The verbs 'Query', 'Check', 'Collect', and 'Analyze' strongly imply a read-only diagnostic tool, which is useful, but no statement of read-only behavior, permission scope, or what happens with cross-project reads appears here. The critical ALLOW_CROSS_PROJECT_READ and scope.warning caveats live only in the 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.

Conciseness4/5

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

Front-loaded purpose sentence followed by a scannable bulleted function list and a single usage sentence. The bullets partly restate the opening resource enumeration, but overall it is tight and well-ordered with little wasted text.

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 only two optional parameters and an output schema present, the description need not explain return values. It conveys what categories of network data are retrieved and when to call it. The main omission, cross-project read requirements, is already handled in the schema.

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%, with both all_projects and network_name fully documented including the 'all' coupling and the server-side flag requirement. The description adds nothing about parameter behavior, which is acceptable given the schema does the work, so the baseline 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?

States a specific verb ('Provides detailed information') and enumerates the exact resources covered: networks, subnets, routers, and security groups. The four-item function list makes the scope concrete, allowing an agent to distinguish it from narrow siblings like get_network_qos_policies or get_floating_ips, though it is a multi-resource grab-bag rather than a single crisp operation.

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?

Ends with an explicit when-to-use trigger: user requests network information, subnet details, router configuration, or network troubleshooting. That is clear context for selection. It stops short of naming exclusions or pointing to narrower siblings, so it is clear but not fully routing.

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