Skip to main content
Glama
MarioDeFelipe

SAP Datasphere MCP Server

reset_database_user_password

Reset a database user's password in SAP Datasphere, generating a new secure password and terminating active sessions to resolve forgotten or compromised credentials.

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.
database_user_idYesDatabase user name suffix whose password will be reset (e.g., 'JEFF', 'ANALYST').
output_fileNoOptional: Path to save new credentials JSON (e.g., 'jeff_new.json'). HIGHLY RECOMMENDED for security!
Behavior5/5

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

No annotations provided, so description fully discloses impacts: old password invalidated immediately, new password auto-generated, user must change on next login, sessions terminated, action logged. This exceeds typical transparency.

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?

Well-structured with sections, front-loaded key sentence, and appropriate detail for a high-risk tool. While slightly verbose with examples and best practices, every section adds value.

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?

No output schema, but description fully explains behavior (invalidation, auto-generation, forced change, termination, logging) and security considerations. Complete for the intended action.

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?

Schema coverage is 100% with descriptions for all parameters. The description restates required params with context and highlights output_file security, but adds minimal value beyond the schema. 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 'Reset the password for an existing database user in SAP Datasphere.' This verb+resource specification is precise and distinguishes the tool from siblings like create_database_user, delete_database_user, and update_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?

Explicitly lists scenarios for use (password forgotten, rotation, locked account) and includes security warnings. However, it does not explicitly contrast with sibling tool update_database_user or provide negative usage examples.

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