Skip to main content
Glama
MCP-OpenStack-Ops

MCP-OpenStack-Ops

by call518

Get Secret Orders

get_secret_orders

List or show Barbican key-generation orders of the current project.

Instructions

List or show Barbican key-generation orders of the current project.

An ACTIVE order points to the generated secret (key orders) or container (asymmetric orders) through secret_ref or container_ref.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of orders to list (1-1000).
order_idNoOrder ID or href to show one order. Empty lists orders.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.9.2

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It usefully explains the domain semantics of an ACTIVE order and how it links out via secret_ref/container_ref, which is real behavioral context. It says nothing about permissions, pagination across the 1-1000 limit, order state/lifetime, or side effects.

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, front-loaded with purpose, with no filler. The second sentence's line break is slightly awkward but it is informative rather than redundant.

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?

A simple two-parameter read tool with a full output schema, so the description does not need to explain return values. It covers what the resource is and the key state relationship. Minor gaps around ordering limits and error behavior keep it from 5.

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%, with limit and order_id both documented in the schema, so the baseline is 3. The description's "show one order" / list framing roughly restates what the schema already says and adds no format or edge-case detail (e.g., href vs. ID handling).

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?

Specific verb+resource: "List or show Barbican key-generation orders of the current project." It distinguishes the two modes (list vs. show one) and scopes to the current project. It does not name a sibling (e.g., get_secret_containers) as an alternative, so it falls short of a 5.

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: "List or show" plus the schema's default-empty order_id signals when listing vs. fetching one order happens. There is no explicit statement of when to prefer this over sibling tools like get_secret_containers, nor any prerequisites or exclusions.

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