Skip to main content
Glama
sanyambassi

thales-cdsp-csm-mcp-server

by sanyambassi

manage_roles

List and retrieve roles with permissions, access rules, and policies for security audits, access troubleshooting, and IAM planning.

Instructions

ROLE MANAGEMENT TOOL - Discover and analyze role-based access control

SUPPORTED ACTIONS: • list: Discover all roles with advanced filtering and pagination • get: Retrieve comprehensive role details including permissions, access rules, and policies

ROLE INFORMATION PROVIDED: • Permission sets and access rules • Associated policies and restrictions • User/group assignments and mappings • Resource access configurations • Audit and compliance information

USE CASES: • Security audits and compliance reporting • Access permission troubleshooting • Role-based access control planning • Identity and access management (IAM) integration • Permission inheritance analysis

Example: Check what permissions the 'database-admin' role has

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
jsonNoReturn structured JSON output instead of human-readable format. Use TRUE for programmatic processing or when integrating with other tools
nameNoExact role name or path (REQUIRED for 'get' action). Examples: 'admin-role', '/production/database-admin', 'read-only-secrets'
actionYesRole management action to perform. SUPPORTED ACTIONS: 'list' (discover all roles with filtering and pagination), 'get' (retrieve detailed role information including permissions, access rules, and policies)
filterNoPattern to filter role names (for 'list' action). Supports wildcards and partial matches. Examples: 'admin*', '*database*', 'prod-'
uid_tokenNoUniversal identity authentication token. Only required when using universal_identity authentication method instead of API key authentication
pagination_tokenNoContinuation token for retrieving next page of results when listing large numbers of roles. Returned in previous response's metadata

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

No annotations are provided, so the description carries the burden. It discloses read-only behavior via 'Discover and analyze' and the list/get actions, and details the information returned (permissions, access rules, policies). It does not discuss side effects or auth requirements, but for a list/get tool, this is adequate.

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?

The description is well-structured with clear sections for actions, provided information, and use cases. It is a bit longer than necessary, but every section adds value, especially the example. It is front-loaded with the tool's purpose and supported actions.

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?

For a read-only role management tool with two actions, the description is complete: it lists actions, role information categories, use cases, and an example. It fully prepares the agent to use the tool correctly, even without an output schema.

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?

The input schema has 100% description coverage with detailed parameter docs (e.g., name required for get, filter wildcards). The description adds some context by reinforcing role info and providing an example, but it doesn't go beyond the schema's parameter semantics, so baseline 3 is appropriate.

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?

The description clearly states the tool's purpose: 'Discover and analyze role-based access control' with two specific actions, list and get. This distinguishes it from sibling manage_* tools by focusing on RBAC discovery and analysis.

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 description includes a dedicated USE CASES section and an example, providing clear context for when to use the tool. It does not explicitly mention when not to use it or name alternatives, but the use cases and example are enough for practical guidance.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/sanyambassi/thales-cdsp-csm-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server