Skip to main content
Glama
MCP-OpenStack-Ops

MCP-OpenStack-Ops

by call518

Get Load Balancer L7 Rules

get_load_balancer_l7_rules

Retrieve the Layer 7 rules configured for a specific load balancer L7 policy by name or ID, helping you inspect traffic routing conditions in OpenStack.

Instructions

Get L7 rules for a specific L7 policy.

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": {
      "policy_name_or_id": "<policy_name_or_id>"
    },
    "name": "get_load_balancer_l7_rules"
  }
}

Input Schema

NameRequiredDescriptionDefault
policy_name_or_idYesL7 policy name or ID (required)

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv3.5.8
    • addedInput schema / properties / policy_name_or_id / description
      Added value: +"L7 policy name or ID (required)"
  2. First observedv0.1.0

TDQS

C2.9/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, yet it says nothing about whether the call is read-only, what happens if the policy name/ID is unknown or ambiguous, whether results are paginated, or how rules are ordered. It only restates the read intent already implied by 'Get'.

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 scoping condition front-loaded and no filler. It is efficient, though its brevity edges toward under-specification rather than polished conciseness.

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

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is simple (one required parameter) and an output schema exists, so return values need not be explained. However, with zero annotations the description should still cover failure behavior and the prerequisite that the policy must exist, which it omits.

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 coverage is 100% and there is only one parameter whose description already states 'L7 policy name or ID (required)'. The description adds no detail on name-vs-ID resolution or format, so the 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 L7 rules') scoped to a parent ('for a specific L7 policy'), which implicitly separates it from get_load_balancer_l7_policies. It stops short of explicitly naming that sibling or contrasting the two, so it is clear but not maximally differentiated.

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 explicit when-to-use, when-not-to-use, or alternative guidance. The phrase 'for a specific L7 policy' hints that a policy identifier is a prerequisite, but the agent must infer that the policy must already exist and that sibling tools list policies rather than rules.

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