Skip to main content
Glama
MarioDeFelipe

SAP Datasphere MCP Server

update_database_user

Update permissions and configuration for an existing database user, including schema access, audit policies, and retention periods. Requires full JSON definition.

Instructions

Update permissions and configuration for an existing database user.

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

Use this tool when:

  • User requests "Grant schema access to JEFF in SALES"

  • Modifying user permissions or access levels

  • Enabling/disabling audit policies

  • Changing retention periods

  • Updating user privileges

What you can update:

  • Consumption permissions (read access, grants)

  • Schema access (space, local, HDI)

  • Script server access

  • Audit policies and retention periods

  • Password policies

Required parameters:

  • space_id: The space containing the database user

  • database_user_id: The user to update

  • updated_definition: JSON with new configuration (full definition required)

Update examples:

Grant schema access:

{
  "consumption": {
    "spaceSchemaAccess": true,
    "consumptionWithGrant": false,
    ...
  },
  "ingestion": {...}
}

Enable audit logging:

{
  "consumption": {...},
  "ingestion": {
    "auditing": {
      "dppRead": {
        "isAuditPolicyActive": true,
        "retentionPeriod": 90
      }
    }
  }
}

Important notes:

  • Must provide complete user definition (not partial updates)

  • Changes take effect immediately

  • Active sessions may need reconnection

  • All changes are logged for audit

Example queries:

  • "Grant space schema access to JEFF"

  • "Enable audit logging for ANALYST with 90 day retention"

  • "Update REPORTING_USER to have consumption with grant"

Note: Corresponds to CLI: datasphere dbusers update --space --databaseuser --file-path <def.json>

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 update (e.g., 'JEFF', 'ANALYST').
updated_definitionYesComplete JSON object with updated permissions. Must include all settings (consumption, ingestion).
output_fileNoOptional: Path to save updated configuration JSON (e.g., 'jeff_updated.json').
Behavior5/5

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

With no annotations, the description fully carries the burden. It explicitly labels the tool as 'HIGH-RISK' requiring user consent, and details behavioral traits: changes take effect immediately, active sessions may need reconnection, all changes are logged, and full definition required (no partial updates). No contradictions.

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 sections, bullet points, and examples. It is front-loaded with the important risk warning. However, it is somewhat lengthy due to multiple examples; could be slightly more concise without losing clarity.

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?

Given the complexity (4 params, nested objects, no output schema), the description is highly complete. It covers all param semantics, use cases, behavioral notes, and update examples. It addresses missing schema details like audit policy and retention periods. No gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, baseline 3. The description adds significant value by explaining each parameter's purpose, providing JSON examples for updated_definition, and noting the full definition requirement. It also introduces the optional output_file parameter with usage example.

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 'Update permissions and configuration for an existing database user.' It uses a specific verb ('update') and resource ('database user'), and distinguishes from sibling tools like create_database_user and delete_database_user by focusing on modification.

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?

The description explicitly provides 'Use this tool when:' scenarios such as granting schema access or modifying permissions, and implies when not to use by contrasting with create/delete/reset siblings. It includes concrete examples of user queries, offering 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/MarioDeFelipe/sap-datasphere-mcp'

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