Skip to main content
Glama
MCP-OpenStack-Ops

MCP-OpenStack-Ops

by call518

Get Secret Stores

get_secret_stores

List Barbican secret store backends. Only clouds that enable multiple secret store backends serve this API; others return an error.

Instructions

List Barbican secret store backends. Only clouds that enable multiple secret store backends serve this API; others return an error.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.9.2

TDQS

A3.6/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 disclosure burden. It usefully discloses a failure mode (the API errors on clouds without multiple backends), which is exactly the kind of context annotations cannot provide. It does not state read-only status, auth requirements, or response shape, though the presence of an output schema relieves the need to explain return values.

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 sentences, with the primary action front-loaded and the availability caveat placed second. Both sentences carry information that changes agent behavior. The only minor friction is the unexplained 'Barbican' jargon, which a general agent may not recognize.

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 zero-parameter read tool with an output schema, this is nearly complete: the action, the resource, and the key precondition are all present. What is missing is a hint about what a 'secret store backend' represents or how the results relate to sibling secret tools, but that is a modest gap given the tool's simplicity.

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 schema imposes no semantics to explain and the baseline is 4. The description correctly spends no words on parameter behavior.

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 Barbican secret store backends'. That clearly distinguishes it from sibling tools that deal with secrets, ACLs, or containers, though it never explicitly names an alternative. The scope (backends, not secrets) is unambiguous.

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?

Implied usage only: an agent must infer that this tool answers 'which secret store backends exist'. The description does add one real usage condition—only clouds with multiple backends serve this API and others error—which helps prevent wasted calls. However, it names no alternatives and gives no guidance on when to prefer a different tool.

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