Skip to main content
Glama
MCP-OpenStack-Ops

MCP-OpenStack-Ops

by call518

Get Load Balancer Pool Members

get_load_balancer_pool_members

Lists all members in a specific OpenStack load balancer pool, showing addresses, ports, weights, health, admin/operational status, and monitor configuration for troubleshooting.

Instructions

Get members for a specific OpenStack load balancer pool.

Functions:

  • Lists all members in a specific pool

  • Shows member addresses, ports, weights, and health status

  • Displays member admin state and operational status

  • Provides monitor configuration for each member

Use when user requests:

  • "Show members for pool [name/id]"

  • "List pool members"

  • "What members are in pool [name]?"

  • "Show pool member status"

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "pool_name_or_id": "<pool_name_or_id>"
    },
    "name": "get_load_balancer_pool_members"
  }
}

Input Schema

NameRequiredDescriptionDefault
pool_name_or_idYesPool name or ID to query members for

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv3.5.8
    • addedInput schema / properties / pool_name_or_id / description
      Added value: +"Pool name or ID to query members for"
  2. First observedv0.1.0

TDQS

A3.9/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; the verb 'Get'/'Lists' implies a read-only operation and the Functions block discloses what is returned (addresses, ports, weights, health status, admin state, monitor config). It does not state auth requirements, error behavior for an unknown pool name/ID, or whether results are paginated, so behavioral context is partial.

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?

Purpose is front-loaded in the first line and the example utterances are short and scannable. The 'Functions' bullets repeat return details that the output schema already covers, which is mild redundancy but not harmful.

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-parameter read tool with an output schema, the description covers purpose, trigger phrases, and return contents. Only the failure mode for an invalid pool reference is unaddressed, which is a minor gap given the output schema carries result structure.

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 coverage is 100% and the single parameter already documents that a pool name or ID is accepted. The description adds only that the pool is 'specific', which is no meaning beyond the schema, so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Opens with a specific verb+resource: 'Get members for a specific OpenStack load balancer pool.' The scope (members within one pool) clearly separates it from get_load_balancer_pools and get_load_balancer_listeners without needing to name them.

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?

The 'Use when user requests' block with four concrete phrasings gives an agent a reliable trigger pattern for this tool. It stops short of exclusions or alternatives (e.g., call get_load_balancer_pools first to discover pool IDs), so it is clear context but not full routing guidance.

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