Skip to main content
Glama
MCP-OpenStack-Ops

MCP-OpenStack-Ops

by call518

Get Load Balancer Pools

get_load_balancer_pools

Lists OpenStack load balancer pools, optionally filtered by listener, and shows protocols, algorithms, members, statuses, and health monitor associations for pool inspection.

Instructions

Get load balancer pools, optionally filtered by listener.

Functions:

  • Lists all pools or pools for a specific listener

  • Shows pool protocols, load balancing algorithms

  • Displays members in each pool with their status

  • Provides health monitor associations

Use when user requests:

  • "Show all load balancer pools"

  • "List pools for listener [name/id]"

  • "What pools are configured on [listener_name]?"

  • "Show pool members and their status"

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

Input Schema

NameRequiredDescriptionDefault
listener_name_or_idNoOptional listener name or ID to filter pools

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv3.5.8
    • addedInput schema / properties / listener_name_or_id / description
      Added value: +"Optional listener name or ID to filter pools"
  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 burden; 'Get'/'Lists'/'Show' makes the read-only nature reasonably evident, and the bullet list previews what the output includes (protocols, algorithms, member status, health monitors). However, it says nothing about permissions, pagination, or the fact that a listener filter with no matches returns an empty list, and since an output schema exists, the return-content bullets add less value than they appear to.

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 with the purpose sentence, then two short labeled lists, which is easy to scan. The enumerated 'Functions' bullets and the four sample utterances contain mild redundancy, but nothing is genuinely wasted.

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 one-optional-parameter read tool with an output schema, the description covers purpose, filter behavior, and expected output facets adequately. The only real gap is disambiguation from the closely related pool-members and listener tools, which the description does not address.

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 single optional parameter is already documented in the schema as 'listener name or ID to filter pools'. The description's 'optionally filtered by listener' merely restates that, adding no format hints (e.g., whether name or UUID is preferred) beyond the schema.

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 load balancer pools') plus the optional listener filter, so an agent can identify the operation immediately. The bullet 'Displays members in each pool with their status' partly overlaps with the sibling get_load_balancer_pool_members, which is not acknowledged, but the core purpose is still unambiguous.

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?

A dedicated 'Use when user requests' block gives four concrete trigger phrasings, including the filtered and unfiltered variants, which is clear positive guidance. It stops short of stating when not to use it or naming alternatives such as the dedicated pool-members tool, so it does not reach a 5.

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