Skip to main content
Glama
DimiDR

SAP Datasphere MCP Server

by DimiDR

update_database_user

Update database user permissions and configuration in SAP Datasphere. Grant schema access, enable audit policies, or change retention periods to manage access and security.

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.
output_fileNoOptional: Path to save updated configuration JSON (e.g., 'jeff_updated.json').
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).
Behavior5/5

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

With no annotations, the description carries full burden and excels: it warns 'HIGH-RISK tool that requires user consent', discloses 'Changes take effect immediately', 'Active sessions may need reconnection', 'All changes are logged', and that complete definitions are needed. This is exceptional transparency about side effects and prerequisites.

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?

The description is well-structured with headers, bullet lists, and code examples. Every section adds necessary context for a high-risk tool, and despite length, it is efficient and scannable. No fluff.

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?

For a mutation tool with no annotations and no output schema, the description covers safety, usage context, parameter details, side effects, and examples. It is fully self-contained for an agent to invoke correctly.

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 coverage is 100%, but the description adds significant value by listing required parameters, emphasizing 'full definition required', and providing two detailed JSON examples for updated_definition. This goes well beyond the schema descriptions and clarifies usage nuances.

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' with specific verb and resource, distinguishing it from sibling tools like create, reset, or delete. It also enumerates exact updateable items (consumption permissions, schema access, audit policies, etc.).

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 provides an explicit 'Use this tool when' list with concrete examples (e.g., 'Grant schema access to JEFF in SALES'), plus example queries. While it doesn't name alternative tools, the context and sibling tool list make it clear, and the guidance is strong enough for an agent to select appropriately.

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