Skip to main content
Glama
MarioDeFelipe

SAP Datasphere MCP Server

by MarioDeFelipe
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

delete_database_user

Permanently delete a database user from a SAP Datasphere space. This action removes the user and all associated permissions irreversibly.

Instructions

Delete a database user from a SAP Datasphere space.

IMPORTANT: This is a HIGH-RISK tool that requires user consent before execution. WARNING: This action is IRREVERSIBLE. User and all associated permissions are permanently deleted.

Use this tool when:

  • User explicitly requests "Delete database user JEFF from SALES"

  • Decommissioning user accounts

  • Removing unauthorized access

  • Cleaning up test/temporary users

  • User left organization

What happens:

  • User account is permanently deleted

  • All active sessions terminated immediately

  • All granted privileges revoked

  • Cannot be undone - must recreate if needed

  • Deletion is logged for audit

Required parameters:

  • space_id: The space containing the database user

  • database_user_id: The user to delete

  • force: Optional flag to skip confirmation dialog

Safety considerations:

  • PERMANENT deletion - no recovery possible

  • Verify user identity and authorization

  • Check if user owns any objects (may cause errors)

  • Document reason for deletion

  • Consider deactivating instead of deleting

Before deleting:

  1. List user's current permissions (list_database_users)

  2. Verify no applications depend on this user

  3. Check if user owns database objects

  4. Get management approval for production users

  5. Document deletion in change log

Example queries:

  • "Delete database user JEFF from SALES space"

  • "Remove TEMP_USER from FINANCE"

  • "Delete TEST_ANALYST - no longer needed"

Best practices:

  • Always confirm with user before deleting

  • Use force=false for interactive confirmation

  • Keep audit trail of deletions

  • For temporary removal, consider update instead

Note: Corresponds to CLI: datasphere dbusers delete --space --databaseuser [--force]

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 to delete (e.g., 'JEFF', 'TEMP_USER'). WILL BE PERMANENTLY DELETED.
forceNoSkip confirmation dialog. Default: false (ask for confirmation). Set true only if user explicitly confirmed deletion.

Tool Definition Quality

A4.9/5.0
Behavior5/5

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

No annotations provided, so the description carries the full burden. It thoroughly discloses the tool's high-risk nature, irreversibility, immediate termination of sessions, privilege revocation, and audit logging. The warnings are prominent and accurate.

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

Conciseness5/5

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

Although lengthy, the description is well-organized with bold headings, bullet points, and numbered lists. Every section (warnings, when to use, what happens, parameters, safety considerations, before deleting, examples, best practices) serves a clear purpose. No redundant information, and the length is justified by the tool's high risk.

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?

The description covers all necessary aspects: purpose, usage guidelines, behavioral effects, parameter details, safety precautions, prerequisites, and examples. Despite no output schema, it explains what happens post-deletion (no recovery). It is comprehensive for a destructive tool with high potential impact.

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?

Input schema already describes all 3 parameters, but the description adds valuable context beyond the schema. For example, it specifies the default for 'force' as false, reiterates the uppercase requirement for 'space_id', and uses examples to clarify parameter usage. This enhances understanding beyond the schema alone.

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 'Delete a database user from a SAP Datasphere space' with a specific verb and resource. It distinguishes from sibling tools like create_database_user, update_database_user, and list_database_users by emphasizing the irreversible deletion and providing alternative actions like deactivation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

Explicitly lists when to use the tool (e.g., user explicitly requests deletion, decommissioning accounts) and when not to (consider deactivating instead). Provides a step-by-step checklist before deletion and best practices, which guides proper usage.

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