Skip to main content
Glama
MarioDeFelipe

SAP Datasphere MCP Server

list_database_users

List all database users in a specific SAP Datasphere space to audit access, check permissions, and avoid duplicate user creation.

Instructions

List all database users in a specific SAP Datasphere space.

Use this tool when:

  • User asks "What database users exist in SALES space?"

  • Auditing user access and permissions

  • Checking who has database access to a space

  • Before creating a new database user (avoid duplicates)

What you'll get:

  • Database user IDs and full names

  • User status (ACTIVE, INACTIVE)

  • Access permissions and privileges

  • Last login information

  • Audit policy settings

Required parameter:

  • space_id: The space ID (uppercase, e.g., 'SALES', 'FINANCE')

Example queries:

  • "List all database users in SALES space"

  • "Show me who has database access to FINANCE"

  • "What database users are configured?"

Database user access types:

  • Consumption: Read data with/without grant privileges

  • Ingestion: Write/load data into space

  • Schema access: Local and space schema access

  • Script server: Execute advanced analytics

Note: This corresponds to the CLI command: datasphere dbusers list --space

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
space_idYesThe space ID in UPPERCASE format (e.g., 'SALES', 'FINANCE', 'HR'). Must match exactly.
output_fileNoOptional: Path to save output as JSON file (e.g., 'users.json'). If not provided, results display in response.
Behavior3/5

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

No annotations are provided, so the description must carry the full burden. It lists what you get (user IDs, status, etc.) but does not explicitly state read-only nature, authentication requirements, or error handling. Some behavioral context is implied but not confirmed.

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 (overview, when to use, what you'll get, required parameter, examples). It is front-loaded with the purpose. Slightly verbose with access types and CLI note, but each section adds value.

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?

Given no output schema, the description explains the return fields (IDs, names, status, etc.). Input schema is fully covered. Missing details like pagination or error cases, but adequate for a list tool.

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?

Schema coverage is 100%, but the description adds value by specifying the format for space_id (uppercase) and providing examples. The optional output_file parameter is also explained. This goes beyond the schema.

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 'List all database users in a specific SAP Datasphere space' with a specific verb and resource. It distinguishes from sibling tools like create_database_user and delete_database_user.

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?

Explicit use cases are provided (e.g., 'User asks What database users exist in SALES space?') along with example queries. While it doesn't explicitly state when not to use, it clearly implies alternatives exist.

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/MarioDeFelipe/sap-datasphere-mcp'

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