Skip to main content
Glama
MCP-OpenStack-Ops

MCP-OpenStack-Ops

by call518

Get Load Balancer Amphorae

get_load_balancer_amphorae

Retrieve amphora instances for a specified load balancer or list all amphorae when no load balancer is provided.

Instructions

Get amphora instances for a load balancer or all amphorae.

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

Input Schema

NameRequiredDescriptionDefault
lb_name_or_idNoOptional load balancer name or ID. If empty, shows all amphorae.

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: +"Optional load balancer name or ID. If empty, shows all amphorae."
  2. First observedv0.1.0

TDQS

A3.5/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; 'Get' does signal a non-mutating read, which is the main safety signal. However, it says nothing about permissions required, whether the unfiltered mode returns an unbounded list, or pagination behavior — meaningful gaps for an unannotated tool, partially offset by the presence of an output schema.

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?

A single short sentence with the resource and scope front-loaded and no wasted wording. It is arguably too terse rather than verbose, but on the conciseness axis it is well-formed and easy to scan.

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?

An output schema exists, so return values need not be described, and the tool has one optional parameter with full schema documentation. The remaining gap is minor operational context (permissions, list size behavior) that a single sentence omission does not make the definition unusable.

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%, so the single optional parameter's meaning and empty-string default are fully documented in structured data. The description adds no semantics beyond that, so 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 ('Get amphora instances') and the two scopes it supports (one load balancer or all). An agent can distinguish it from siblings like get_load_balancer_listeners or get_load_balancer_pools because 'amphora instances' is a distinct resource, though the definition never explicitly contrasts itself with them.

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

Usage Guidelines3/5

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

The 'or all amphorae' phrasing implies the two usage modes (filtered by load balancer vs. unfiltered), but that same condition is already stated in the schema's parameter description. There is no guidance on when to prefer this tool over other load balancer sub-resource tools, nor on prerequisites such as needing a load balancer ID first.

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