Skip to main content
Glama
MCP-OpenStack-Ops

MCP-OpenStack-Ops

by call518

Get Secret Containers

get_secret_containers

List or show Barbican secret containers of the current project.

Instructions

List or show Barbican secret containers of the current project.

A container groups secret hrefs, e.g. a certificate container with certificate, private_key and intermediates entries. Payloads are never returned.

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

Input Schema

NameRequiredDescriptionDefault
nameNoContainer name, ID or href to show one container. Empty lists containers.
limitNoMaximum number of containers to list (1-1000).

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.9.2

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden; it usefully discloses that payloads are never returned, which signals a safe metadata-only read. It omits other behavioral facts an agent would want: whether it is strictly read-only, any permission/ownership requirements, and behavior when a name matches nothing.

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?

Two short paragraphs, front-loaded with the action and scope, followed by a compact definition of a container and the payload caveat. No filler; the only slight looseness is that the container explanation could be one clause shorter.

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 structure need not be explained, and the payload caveat covers the main semantic risk. However, for a completely unannotated tool, the description leaves gaps around read-only guarantees, permissions, and pagination behavior that an agent might need before calling it.

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%, so both parameters (name, limit) are already fully documented, including the empty-name list convention and the 1-1000 range. The description adds conceptual meaning about containers but no parameter detail beyond the schema, 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?

States a specific verb and resource ("List or show Barbican secret containers") and scopes it to "the current project," plus explains what a container is (grouping of secret hrefs). It does not explicitly name a sibling to contrast with (e.g., secret stores or orders), but the resource is distinct enough that an agent can identify it from the name and first sentence.

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 dual list/show mode is described, and the schema reinforces it via the empty-name convention, but the description gives no guidance on when to reach for this tool versus other Barbican reads (orders, stores, ACLs) or what to do on a miss. Usage context is implied rather than stated.

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