Skip to main content
Glama
MCP-OpenStack-Ops

MCP-OpenStack-Ops

by call518

Get Role Assignments

get_role_assignments

Query role assignments for users and groups to review project- and domain-level permissions, scopes, and access control for security auditing.

Instructions

Get role assignments for the current project.

Functions:

  • Query role assignments for users and groups

  • Display project-level and domain-level permissions

  • Show scope of role assignments

  • Provide comprehensive access control information

Use when user requests permission information, access control queries, or security auditing.

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

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?

No annotations are supplied, so the description carries the full disclosure burden. It does disclose that results are scoped to the current project and span both project- and domain-level permissions, which is useful behavioral context. It omits permission/auth requirements, whether results are paginated, and any indication of volume or cost.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The lead sentence is front-loaded and efficient, but the bullet list is padded: 'Query role assignments,' 'Show scope of role assignments,' and 'Provide comprehensive access control information' largely restate each other and the opening sentence. Tightening to two substantive bullets would say the same thing.

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 already describing return values, the description covers purpose, scope, and use cases adequately. Only the absence of any auth or result-volume context keeps it short of full completeness.

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; baseline 4 applies. The description correctly implies no filtering input is required.

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?

Clear specific verb+resource: 'Get role assignments for the current project,' with the heading sentence establishing scope (current project) and the bullets clarifying that both user and group assignments and both project- and domain-level permissions are returned. It doesn't explicitly distinguish itself from identity-related siblings, but the subject matter 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 Guidelines4/5

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

The closing line gives concrete when-to-use triggers: permission information, access control queries, and security auditing. It provides no when-not-to-use guidance or named alternatives, but the affirmative context is clear enough to route an agent.

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