Skip to main content
Glama
MCP-OpenStack-Ops

MCP-OpenStack-Ops

by call518

Get Key Manager Quotas

get_key_manager_quotas

Show the effective Barbican quotas (secrets, orders, containers, consumers, CAs) of the current project; -1 means unlimited.

Instructions

Show the effective Barbican quotas (secrets, orders, containers, consumers, CAs) of the current project; -1 means unlimited.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.9.2

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden, and it does disclose two non-obvious behaviors: quotas are 'effective' (i.e., after overrides rather than raw defaults) and -1 is a sentinel meaning unlimited. It does not explicitly state that the call is read-only or what permissions are required, which keeps it short of a 5.

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 that is front-loaded with the resource and verb, then the covered categories, then the sentinel semantics. Every clause adds information; nothing is redundant.

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

Completeness5/5

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

For a zero-parameter read tool with an output schema already documenting the return shape, the description supplies everything else an agent needs: what is returned, its scope, and how to interpret the -1 value.

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 the baseline is 4 and there is no parameter meaning the description could add. The description correctly implies the operation is argument-free by scoping to the current project.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names a specific verb (Show) and a specific resource (effective Barbican quotas), enumerates the five quota categories covered (secrets, orders, containers, consumers, CAs), and scopes the result to 'the current project'. This distinguishes it from the load-balancer quota sibling by naming the Barbican service explicitly.

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 'of the current project' implicitly tells the agent no project argument is needed and that results are scoped to the caller, which is useful context. However, there is no explicit statement of when to prefer this over other quota or service-info tools, nor any precondition or exclusion.

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