Skip to main content
Glama
MCP-OpenStack-Ops

MCP-OpenStack-Ops

by call518

Get User List

get_user_list

Retrieve OpenStack users in the current domain to inspect account status, email, domain, and creation or modification timestamps for identity and user administration tasks.

Instructions

Get list of OpenStack users in the current domain.

Functions:

  • Query user accounts and their basic information

  • Display user status (enabled/disabled)

  • Show user email and domain information

  • Provide user creation and modification timestamps

Use when user requests user management information, identity queries, or user administration tasks.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/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 does disclose the shape of the result (status, email, domain, timestamps) and that the domain scope is implicit. However, it says nothing about permissions required to list users, pagination or result caps, or whether disabled users are included — gaps that matter for an identity-listing call.

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?

Purpose is front-loaded in the first sentence and the supporting detail is organized as a short bullet list. The bullets partly restate what the output schema already exposes, which is mild padding, but nothing is confusing or out of order.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

A zero-parameter read tool with an output schema needs little more than a clear statement of what is listed and at what scope, both of which are present. Return value details are covered by the output schema, so no further description is required.

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 there is nothing for the description to disambiguate; the implicit domain scoping is at least consistent with the empty schema. Baseline for a no-parameter tool.

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 ("Get list of OpenStack users") plus a meaningful scope ("in the current domain"). It does not name or distinguish itself from nearby identity siblings such as get_identity_groups or get_domains, but the object being listed 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?

The final sentence gives implied usage context ("user management information, identity queries, or user administration tasks"), but these are generic triggers that would also describe group or domain lookups. No when-not conditions or alternative tools are named.

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