Skip to main content
Glama
MCP-OpenStack-Ops

MCP-OpenStack-Ops

by call518

Get Secret Acl

get_secret_acl

Show the read ACL of a Barbican secret or container.

Instructions

Show the read ACL of a Barbican secret or container.

The ACL lists users outside the owning project allowed to read it and whether project-wide access (project-access) is enabled.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "name_or_ref": "<name_or_ref>"
    },
    "name": "get_secret_acl"
  }
}

Input Schema

NameRequiredDescriptionDefault
name_or_refYesSecret or container name, ID or href.
target_typeNosecret or container.secret

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.9.2

TDQS

A3.6/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden. It discloses the semantics of the returned ACL (users outside the owning project, project-access flag), which is helpful, but says nothing about permission requirements for reading an ACL, error behavior for a nonexistent secret, or whether containers and secrets behave differently.

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?

Two short sentences, front-loaded with the action and followed by the one concept an agent needs to interpret the output. No filler.

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 what the ACL contains. The remaining gap is auth/prerequisite context for a Key Manager operation with no annotations backing it up.

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 both parameters are already documented and the baseline is 3. The description adds meaningful scope (Barbican, ACL read semantics) but nothing about name-vs-ID-vs-href resolution or how target_type changes the lookup.

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 and resource ("Show the read ACL of a Barbican secret or container") and scopes it to read ACLs only. The sibling list consists of unrelated resource getters, so no ambiguity is introduced.

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 by the word "Show" – an agent can infer this is a read-only inspection call, but there is no explicit when-to-use, prerequisite (ownership or admin rights), or statement about when the ACL is empty.

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