Skip to main content
Glama
MCP-OpenStack-Ops

MCP-OpenStack-Ops

by call518

Get Load Balancer L7 Policies

get_load_balancer_l7_policies

Retrieves OpenStack Load Balancer Layer 7 policies for a specified listener, or lists all policies when no listener is provided.

Instructions

Get L7 policies for a listener or all L7 policies.

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

Input Schema

NameRequiredDescriptionDefault
listener_name_or_idNoOptional listener name or ID to filter policies. If empty, shows all policies.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv3.5.8
    • addedInput schema / properties / listener_name_or_id / description
      Added value: +"Optional listener name or ID to filter policies. If empty, shows all policies."
  2. First observedv0.1.0

TDQS

A3.6/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" plus the presence of an output schema makes the read-only nature clear, and the filtered/unfiltered scope is disclosed, but there is no mention of pagination, permissions, or response size for the unfiltered case.

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

Conciseness5/5

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

A single sentence with the resource and both scope modes front-loaded and no redundant or filler wording. Nothing could be removed without losing information.

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?

This is a low-complexity read tool with one optional parameter and an output schema that explains the return values, so the description covers the essential call semantics. Only the relationship to the similarly named l7_rules tool and any pagination behavior are left unstated.

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 listener_name_or_id parameter is already fully documented in the schema. The description restates the same empty-means-all behavior without adding format, ID-vs-name resolution hints, or error conditions.

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 description names a specific verb and resource ("Get L7 policies") and states its two scopes: a single listener or all policies. It implicitly distinguishes policies from the sibling get_load_balancer_l7_rules, though it never names that sibling or explains the difference.

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 phrase "for a listener or all L7 policies" implies that omitting the filter returns everything, but the description gives no explicit when-to-use guidance, no prerequisites, and no routing away from adjacent tools like get_load_balancer_l7_rules or get_load_balancer_listeners.

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