Skip to main content
Glama
MCP-OpenStack-Ops

MCP-OpenStack-Ops

by call518

Get Floating Ips

get_floating_ips

Get list of floating IPs with their associations.

Instructions

Get list of floating IPs with their associations.

Functions:

  • Query floating IPs and their current status

  • Display associated fixed IPs and ports

  • Show floating IP pool and router associations

  • Provide floating IP allocation and usage information

Use when user requests floating IP information, external connectivity queries, or IP management tasks.

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

Input Schema

NameRequiredDescriptionDefault
all_projectsNoIf True, list every floating IP Neutron shows the credential in any project (like 'openstack floating ip list' as an administrator). 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 floating IP Neutron shows the\ncredential in any project (like 'openstack floating ip list' as an\nadministrator). 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

B3.1/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 it largely fails to: it never states this is a safe read-only operation, never mentions permission requirements or the ALLOW_CROSS_PROJECT_READ server gate, and never mentions scope.warning. The 'Functions:' bullets restate what data appears in the output rather than disclosing behavior an agent couldn't already infer from 'Get list of floating IPs'.

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 and the usage line is compact, but the four 'Functions:' bullets are near-tautological restatements of the purpose ('Query floating IPs and their current status', 'Provide floating IP allocation and usage information') that burn space without adding information. Trimming them to one line would improve the definition.

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?

An output schema exists, so return-value explanation is not required, and the single parameter is fully covered by the schema. What is missing relative to a zero-annotation tool is any statement of read-only safety and the multi-project permission model, which are the main things an agent needs to call this confidently in an administrator context.

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%, so the single parameter (all_projects) is already fully documented in the schema, including the server flag and the scope.warning caveat. The description adds nothing on top of that, which is the baseline expectation when the schema does the work.

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 opening sentence gives a specific verb and resource — 'Get list of floating IPs with their associations' — which is distinct from the sibling get_floating_ip_pools (pools vs. actual allocated IPs). It does not explicitly name that sibling, so the differentiation is left slightly implicit, but the resource is concrete enough for an agent to act on.

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 final line offers trigger conditions ('floating IP information, external connectivity queries, or IP management tasks'), which is real when-to-use guidance. However, it gives no when-not conditions, no mention of alternatives like the pool-listing sibling, and no hint that the cross-project path is a special mode with a server-side gate.

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