Skip to main content
Glama
MCP-OpenStack-Ops

MCP-OpenStack-Ops

by call518

Get Load Balancer Availability Zones

get_load_balancer_availability_zones

Retrieve the availability zones available for load balancers in an OpenStack project, helping you plan deployment and placement.

Instructions

Get load balancer availability zones.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.4/5.0
Behavior2/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 and discloses essentially nothing. It does not confirm this is a read-only lookup, whether it requires authentication or a project/region context, or whether results vary per load balancer; only the name hints at read-only semantics.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single short sentence with no filler and the resource front-loaded, so structure is fine. However, the brevity here reflects under-specification rather than tight editing — the same sentence count could have carried real scope information.

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

Completeness2/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 values need not be described, and the tool has no inputs to document. What remains missing is the one thing the description should supply: what set of availability zones this returns and how it differs from the plain availability-zones sibling. For a parameterless discovery tool the definition is barely minimal.

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?

The tool takes zero parameters, so there is nothing for the description to explain at the parameter level. Baseline 4 applies; no parameter meaning is lost.

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

Purpose2/5

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

The description "Get load balancer availability zones." is a verbatim restatement of the tool title, adding no information beyond the name. An agent can infer the resource is load-balancer-scoped availability zones, but nothing in the sentence distinguishes it from the sibling get_availability_zones or clarifies whether it returns supported AZs for LB creation versus AZs in use by a specific balancer.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance, no exclusions, and no mention of the closely related get_availability_zones sibling that an agent would plausibly confuse this with. Usage context is entirely implied by the tool name.

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