Skip to main content
Glama
MCP-OpenStack-Ops

MCP-OpenStack-Ops

by call518

Get Load Balancer Flavors

get_load_balancer_flavors

Retrieve available load balancer flavors to select the right capacity and configuration for OpenStack load balancers.

Instructions

Get load balancer flavors.

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

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 burden and discloses nothing: not that this is a read-only catalog fetch, not whether results are cached or paginated, not whether authentication or a specific project scope is required. The only behavioral hint is the verb 'Get'.

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?

The description is a single short sentence with no filler, so it is not bloated. However, brevity here comes from under-specification rather than disciplined editing, leaving no front-loaded context for the agent.

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?

The tool is simple (zero params) and has an output schema, so return values needn't be described. Even so, the agent is never told what a 'flavor' represents, how it relates to providers or availability zones, or what to do with the returned list.

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 about inputs; the baseline for a parameterless tool applies. The empty schema plus the existing output schema means no parameter-level meaning is missing.

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 sentence 'Get load balancer flavors' only restates the tool name and title verbatim, adding no scope or disambiguation. With siblings such as get_load_balancer_providers and get_load_balancer_availability_zones present, the agent gets no help distinguishing flavors from other catalog-like lookups.

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 stated prerequisites, and no mention of any alternative tool. The agent must infer from the name alone that this is a reference-data lookup used before creating or sizing a load balancer.

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