Skip to main content
Glama
MCP-OpenStack-Ops

MCP-OpenStack-Ops

by call518

Get Quota

get_quota

Retrieve per-service quota limits, current usage, and usage percentages for an OpenStack project, defaulting to the current project when no name is provided.

Instructions

Get quota information for projects (similar to 'openstack quota show').

Each service reports limits, usage and usage_percent (percent of each limit in use). A usage value is null when it could not be determined, and usage_percent is null for unlimited (-1), zero or missing limits and for unknown usage.

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

Input Schema

NameRequiredDescriptionDefault
project_nameNoName of the project (optional, defaults to current project if empty)

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv3.5.8
    • addedInput schema / properties / project_name / description
      Added value: +"Name of the project (optional, defaults to current project if empty)"
  2. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the burden and does add real value: it explains that each service reports limits, usage, and usage_percent, and precisely defines when usage and usage_percent are null (-1 unlimited, zero or missing limits, unknown usage). What it does not cover is the access profile (what permissions are needed to read another project's quota) or whether requesting a foreign project fails versus returns empty.

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?

Purpose is front-loaded in the first clause, followed by a compact paragraph on result semantics; there is no filler. The null-handling sentence is dense but each clause encodes a distinct rule an agent would otherwise misinterpret.

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?

For a single-optional-parameter read tool with an output schema, the description supplies the interpretive key to the output (nulls, unlimited = -1) that the schema alone would not convey. Missing only cross-service routing guidance relative to the key manager quota sibling, which is a minor gap.

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 the single optional project_name parameter is fully documented in the schema, including its default-to-current behavior. The description adds no additional parameter semantics beyond that, so the baseline of 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?

The description states a specific verb and resource (get quota information for projects) and anchors it with the analogous CLI command 'openstack quota show', which lets an agent grasp the shape of the result immediately. It does not explicitly distinguish itself from the sibling get_key_manager_quotas, which is a narrower service-specific variant, so it falls short of a 5.

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: 'for projects' plus the schema note that an empty project_name falls back to the current project tells an agent this is a project-scoped read. There is no explicit when-to-use statement, no exclusion, and no pointer to the quota-related sibling for service-specific quotas.

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