Skip to main content
Glama
DimiDR

SAP Datasphere MCP Server

by DimiDR

reset_database_user_password

Reset a database user's password in SAP Datasphere after forgotten/compromised credentials. Generates a temporary password that must be changed on next login.

Instructions

Reset the password for an existing database user in SAP Datasphere.

IMPORTANT: This is a HIGH-RISK tool that requires user consent before execution.

Use this tool when:

  • User requests "Reset password for database user JEFF"

  • Password forgotten or compromised

  • Regular password rotation policy

  • Account locked due to failed login attempts

What happens:

  • Old password is invalidated immediately

  • New password is auto-generated securely

  • User must change password on next login

  • Action is logged for security audit

Required parameters:

  • space_id: The space containing the database user

  • database_user_id: The user whose password needs reset

Security considerations:

  • New password shown only once - save securely!

  • Recommend using output_file to save credentials

  • Notify user through secure channel

  • Enforce password change on first login

  • All active sessions are terminated

Example queries:

  • "Reset password for JEFF in SALES space"

  • "Generate new password for database user ANALYST"

  • "REPORTING_USER password expired, reset it"

Best practices:

  • Always save output to secure file

  • Communicate new password via secure channel (not email!)

  • Verify user identity before resetting

  • Document password reset in change log

Note: Corresponds to CLI: datasphere dbusers password reset --space --databaseuser

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
space_idYesThe space ID containing the database user (e.g., 'SALES', 'FINANCE'). Must be uppercase.
output_fileNoOptional: Path to save new credentials JSON (e.g., 'jeff_new.json'). HIGHLY RECOMMENDED for security!
database_user_idYesDatabase user name suffix whose password will be reset (e.g., 'JEFF', 'ANALYST').
Behavior5/5

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

With no annotations provided, the description fully carries the burden of behavioral disclosure. It does an excellent job: 'Old password is invalidated immediately', 'New password is auto-generated securely', 'User must change password on next login', 'Action is logged for security audit', 'All active sessions are terminated', and the high-risk warning. This far exceeds typical MCP descriptions.

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 headings and bullet points, making it scannable. It is longer than average, but this is justified for a high-risk mutation tool. There is minor redundancy (e.g., security reminders in both 'Security considerations' and 'Best practices'), but every section serves a purpose.

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?

Despite having no output schema and no annotations, the description covers operational context, security implications, example queries, CLI mapping, and best practices. It is complete enough for an agent to confidently invoke the tool and handle the response correctly.

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%, and the input schema already describes each parameter. The description adds contextual meaning by listing 'Required parameters' and explaining their purpose in the workflow, plus recommending 'output_file' to save credentials. This adds value beyond the bare 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 opens with a clear explanation: 'Reset the password for an existing database user in SAP Datasphere.' This uses specific verb+resource language and distinguishes the tool from sibling tools like create_database_user or update_database_user by focusing specifically on password reset.

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 explicitly lists use cases: 'Use this tool when: User requests "Reset password for database user JEFF" / Password forgotten or compromised / Regular password rotation policy / Account locked due to failed login attempts.' It does not explicitly mention when not to use it or alternative tools, but the examples and best practices provide clear 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/DimiDR/SAP-Datasphere-MCP'

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