Skip to main content
Glama
MCP-OpenStack-Ops

MCP-OpenStack-Ops

by call518

Get Load Balancer List

get_load_balancer_list

Lists OpenStack load balancers with VIP, status, listener details, and pagination to inspect availability and troubleshoot load balancing.

Instructions

Retrieve comprehensive list of OpenStack load balancers with detailed information.

Functions:

  • Lists all load balancers in the OpenStack cluster

  • Provides detailed load balancer information including VIP, status, listeners

  • Supports pagination for large environments (limit/offset)

  • Shows listener count and basic listener information for each load balancer

  • Displays provisioning and operating status for troubleshooting

Use when user requests:

  • "Show me all load balancers"

  • "List load balancers with details"

  • "What load balancers are available?"

  • "Show load balancer 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_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum load balancers to return (default: 50; capped by the server LIST_MAX_LIMIT setting, default 100)
offsetNoNumber of load balancers to skip for pagination (default: 0)
include_allNoReturn all load balancers ignoring limit/offset (default: False)
all_projectsNoIf True, include every project the credential's Octavia policy allows (like 'openstack loadbalancer list' as an administrator); rows carry project_id and project_name. Requires ALLOW_CROSS_PROJECT_READ=true on the server. Octavia narrows an unauthorized request to the current project, so check result.scope.warning.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv4.0.4
    • changedInput schema / properties / limit / description
      Previous value: -"Maximum load balancers to return (1-200, default: 50)"New value: +"Maximum load balancers to return (default: 50; capped by the server LIST_MAX_LIMIT setting, default 100)"
  2. Changed1 schema field changedv3.9.2
    • addedInput schema / properties / all_projects
      Added value: +{
      +  "default": false,
      +  "description": "If True, include every project the credential's Octavia\npolicy allows (like 'openstack loadbalancer list' as an\nadministrator); rows carry project_id and project_name. Requires\nALLOW_CROSS_PROJECT_READ=true on the server. Octavia narrows an\nunauthorized request to the current project, so check\nresult.scope.warning.",
      +  "type": "boolean"
      +}
  3. Changed3 schema fields changedv3.5.8
    • addedInput schema / properties / include_all / description
      Added value: +"Return all load balancers ignoring limit/offset (default: False)"
    • addedInput schema / properties / limit / description
      Added value: +"Maximum load balancers to return (1-200, default: 50)"
    • addedInput schema / properties / offset / description
      Added value: +"Number of load balancers to skip for pagination (default: 0)  "
  4. First observedv0.1.0

TDQS

A3.8/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 full behavioral burden. It discloses return content and the existence of pagination, but never states that this is a read-only operation, that all_projects requires ALLOW_CROSS_PROJECT_READ and can be silently narrowed by Octavia policy (result.scope.warning), or anything about rate limits or result ordering.

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 opening sentence followed by scannable function and trigger bullet lists. Minor waste: "Lists all load balancers" restates the opening line, and the quoted example utterances are somewhat verbose, but they serve a routing purpose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 shape need not be described, and all four parameters have full schema documentation including the cross-project caveat. For a parameterless-required read tool this covers what an agent needs to invoke it correctly, with only the sibling-overlap ambiguity as a residual gap.

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%, including defaults, server cap behavior, and the cross-project policy caveat, so the schema already does the explanatory work. The description adds only the bare phrase "Supports pagination for large environments (limit/offset)", which is strictly redundant; 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 and resource ("Retrieve comprehensive list of OpenStack load balancers") and enumerates what the payload contains (VIP, status, listeners, listener count, provisioning/operating status). It does not, however, distinguish itself from the sibling get_load_balancer_details, despite claiming "detailed information" — that overlap leaves purpose only mostly clear.

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?

Four quoted user-request triggers ("Show me all load balancers", "What load balancers are available?", etc.) give concrete context for selection. There are no exclusions or explicit routing to alternatives such as get_load_balancer_details or get_load_balancer_listeners, so it stops short of 5.

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