Skip to main content
Glama
MCP-OpenStack-Ops

MCP-OpenStack-Ops

by call518

Get Load Balancer Health Monitors

get_load_balancer_health_monitors

Lists load balancer health monitors, optionally filtered by pool, to inspect check types, intervals, timeouts, and retry settings.

Instructions

Get health monitors, optionally filtered by pool.

Functions:

  • Lists all health monitors or monitors for a specific pool

  • Shows monitor types (HTTP, HTTPS, TCP, PING, UDP-CONNECT)

  • Displays health check intervals, timeouts, and retry settings

  • Provides HTTP-specific settings (method, URL path, expected codes)

Use when user requests:

  • "Show all health monitors"

  • "List health monitors for pool [name/id]"

  • "What health checks are configured?"

  • "Show health monitor configuration"

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

Input Schema

NameRequiredDescriptionDefault
pool_name_or_idNoOptional pool name or ID to filter monitors (empty for all)

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: +"Optional pool name or ID to filter monitors (empty for all)"
  2. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations supplied, the description carries the burden and does so reasonably: the 'Functions' list discloses what the response contains, and the parameter note establishes that an empty filter returns everything rather than an error. It does not state read-only nature, pagination, or permission requirements, which is the remaining gap for a no-annotation tool.

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 core action, then organized into two scannable bullet groups with no filler prose. The four example utterances are somewhat padded where two would have conveyed the same intent, but nothing is misleading or out of place.

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 single-optional-parameter read tool with an output schema that already defines return values, the description covers scope, triggers, and returned fields adequately. The only shortfall is the absent behavioral note (read-only, pagination) that annotations would otherwise have supplied.

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?

There is only one optional parameter and the schema already documents it at 100% coverage, including the 'empty for all' behavior. The description's 'optionally filtered by pool' and the dual list-all/list-for-pool phrasing merely restate what the schema says, adding no new semantics such as accepted name formats or partial matching.

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 health monitors) plus its optional scope (filtered by pool), and the Functions list enumerates exactly the attributes returned (types, intervals, timeouts, retries, HTTP settings). It is unambiguous against a generic sibling like get_load_balancer_pools, though it never names a sibling it should be preferred over.

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 gives four concrete trigger utterances, including the filtered variant, which removes most ambiguity about when to call it. It stops short of exclusions or naming the alternative tool to use for related data (e.g. pool members or listener details), so it is clear context without guidance on when not to use it.

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