Skip to main content
Glama
MCP-OpenStack-Ops

MCP-OpenStack-Ops

by call518

Get Secrets

get_secrets

List or show Barbican secrets of the current project (metadata only).

Instructions

List or show Barbican secrets of the current project (metadata only).

Never returns a secret payload; payload retrieval is intentionally not provided so key material cannot reach the LLM. Use the secret_ref from this tool as a reference, for example in set_load_balancer_listener.

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

Input Schema

NameRequiredDescriptionDefault
nameNoSecret name, ID or href to show one secret with its consumers. Empty lists secrets.
limitNoMaximum number of secrets to list (1-1000).
secret_typeNoFilter for the list, e.g. opaque, certificate, private, symmetric, public, passphrase.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.9.2

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the metadata-only constraint, the deliberate absence of payload retrieval, and the security rationale. It omits pagination/ordering behavior and any permission requirements, which keeps it from 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?

Three short sentences, front-loaded with the core capability, then the key constraint, then the actionable follow-up. No filler or repetition.

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?

An output schema exists, so return values need not be explained, and the description covers the critical behavioral constraint. Minor gap: nothing about result volume or how limit interacts with listing, which matters for a list tool.

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 description coverage is 100%, so name, limit, and secret_type are already fully documented in the schema. The description adds no parameter-level meaning beyond that, so the baseline 3 applies.

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?

States a specific verb pair (list/show) and resource (Barbican secrets) scoped to the current project, and immediately qualifies the output as metadata only. An agent can tell exactly what this returns and what it does not.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives concrete downstream usage: take the secret_ref and pass it to set_load_balancer_listener. It also rules out payload retrieval, which is the main misuse risk. It stops short of stating when to prefer listing versus showing a single secret, though the name parameter's schema description covers that.

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