Skip to main content
Glama
MCP-OpenStack-Ops

MCP-OpenStack-Ops

by call518

Get Load Balancer Details

get_load_balancer_details

Retrieve detailed OpenStack load balancer configuration, including VIP, listeners, pools, members, health monitors, and provisioning status by name or ID.

Instructions

Get detailed information about a specific OpenStack load balancer.

Functions:

  • Shows comprehensive load balancer details including VIP configuration

  • Lists all listeners with their protocols and ports

  • Shows pools and members for each listener

  • Displays health monitor information if configured

  • Provides provisioning and operating status

Use when user requests:

  • "Show details for load balancer [name/id]"

  • "Get load balancer configuration"

  • "Show load balancer listeners and pools"

  • "What's the status of load balancer [name]?"

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": {
      "lb_name_or_id": "<lb_name_or_id>"
    },
    "name": "get_load_balancer_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
lb_name_or_idYesLoad balancer name or ID to query

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv3.5.8
    • addedInput schema / properties / lb_name_or_id / description
      Added value: +"Load balancer name or ID to query"
  2. First observedv0.1.0

TDQS

A3.8/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 behavioral burden. It discloses what the response contains (listeners, pools, members, health monitors, status), which is useful, but never states that this is a non-mutating read, how it behaves on a missing or ambiguous name/ID, or whether the call is heavy/slow given the nested data it assembles.

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 bulleted 'Functions' and 'Use when user requests' sections are front-loaded and scannable, and each bullet adds distinct content. The verbatim example phrases are slightly redundant with the function list and could be trimmed, but nothing is materially wasteful.

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 a full output schema and complete schema coverage, the definition supplies more than enough to call it correctly. The enumeration of returned fields is partly duplicative given the output schema, and error/ambiguity handling is absent, keeping it just under top marks.

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?

Schema coverage is 100% for the single parameter, whose description ('Load balancer name or ID to query') already covers the accepted identifier forms. The description reinforces this with the '[name/id]' examples but adds no new semantics such as whether partial names are matched or which ID format (UUID vs name) is preferred, so it sits at the baseline rather than above it.

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 ('Get detailed information about a specific OpenStack load balancer') and enumerates the contents returned: VIP configuration, listeners, pools, members, health monitors, and provisioning/operating status. It stops short of distinguishing this aggregate view from sibling sub-resource tools like get_load_balancer_listeners or get_load_balancer_pools, so an agent could be unsure which overlap.

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?

Provides four concrete trigger phrases ('Show details for load balancer [name/id]', 'Get load balancer configuration', etc.), which is clear positive guidance for when to invoke it. However, it gives no exclusions or pointers to the sibling tools that fetch listeners or pools individually, leaving the when-not condition unaddressed.

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