Skip to main content
Glama
MCP-OpenStack-Ops

MCP-OpenStack-Ops

by call518

Get Floating Ip Pools

get_floating_ip_pools

Lists OpenStack external networks that provide floating IPs and shows available and used IP counts, enabling capacity and utilization checks before allocation.

Instructions

Get list of floating IP pools (external networks).

Functions:

  • List all external networks that can provide floating IPs

  • Show available and used IP counts for each pool

  • Display network configuration for floating IP allocation

  • Provide pool capacity and utilization information

Use when user requests:

  • "Show floating IP pools"

  • "List available floating IP networks"

  • "Check floating IP capacity"

  • "What external networks are available?"

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose what information is surfaced: available vs. used IP counts, network configuration, and capacity/utilization. It does not state that the operation is read-only, whether results are paginated, or whether all pools or only authorized ones are returned; and since an output schema exists, return-shape detail is less critical.

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?

The description is front-loaded with the one-line purpose, followed by a scannable functions list and an example-trigger list. There is mild redundancy between "List all external networks that can provide floating IPs" and "Provide pool capacity and utilization information," but no serious padding.

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?

For a zero-parameter read tool with an output schema, this is nearly complete: purpose, contents of the response, and trigger phrasings are all covered. The remaining gap is sibling differentiation, which matters here because get_floating_ips has a very similar name.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is no parameter semantics for the description to compensate for. Baseline 4 applies; nothing is misleading or missing on this dimension.

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 has a specific verb and resource ("Get list of floating IP pools") and disambiguates the term with the parenthetical "(external networks)". It does not, however, contrast itself with the closely named sibling get_floating_ips, so an agent must infer the distinction between listing pools and listing allocated floating IPs.

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?

The "Use when user requests" block gives four concrete example utterances that imply the intended trigger contexts (pool listing, capacity checks, external network availability). It offers no when-not guidance and names no alternative tool, so routing versus get_floating_ips is left to inference.

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