Skip to main content
Glama
MCP-OpenStack-Ops

MCP-OpenStack-Ops

by call518

Get Load Balancer Quotas

get_load_balancer_quotas

Retrieve load balancer quotas for a specific OpenStack project or all projects to monitor capacity and plan resource allocation.

Instructions

Get load balancer quotas for a project or all projects.

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

Input Schema

NameRequiredDescriptionDefault
project_idNoOptional project ID. If empty, shows quotas for all projects.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv3.5.8
    • addedInput schema / properties / project_id / description
      Added value: +"Optional project ID. If empty, shows quotas for all projects."
  2. First observedv0.1.0

TDQS

A3.7/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 disclosure burden. 'Get' implies a read-only, non-destructive operation and the scope behavior is stated, but permission requirements, error behavior for invalid project IDs, and whether all-projects results are paginated or aggregated are not mentioned.

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?

One short sentence with the resource and scope front-loaded and zero filler. It is arguably too terse for a tool with no annotations, but no sentence is wasted.

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?

An output schema exists, so return values need not be explained, and the single parameter is fully covered by the schema. However, for a read tool with no annotations, the description supplies no behavioral context such as permissions or aggregation semantics for the all-projects case, leaving it merely adequate.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the single parameter is fully documented, including the empty-string default. The description's 'for a project or all projects' adds the operational meaning of leaving project_id empty, which is genuinely useful framing on top of the schema.

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 ('Get') and resource ('load balancer quotas') with the scope of the query ('for a project or all projects'). It is clear what the tool returns, though it does not distinguish itself from the many sibling get_load_balancer_* tools beyond the resource noun.

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?

Usage is only implied: an agent can infer this is the quota-retrieval tool and that project_id selects the scope. There is no explicit when-to-use, no when-not-to-use, and no alternative tool named for related load balancer inventory needs.

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