Skip to main content
Glama
emilabd247

Jedox MCP Server

by emilabd247

Set Jedox Cell Value

jedox_set_cell_value

Write a value to any cell in a Jedox cube with immediate persistence. Choose between SET, ADD, or ALLOCATE modes for handling consolidated parent cells.

Instructions

Write a value to a cell in a Jedox cube.

Cell writes are persisted immediately — no need to call jedox_save_database.

Args:

  • database_id: Numeric ID of the database

  • cube_id: Numeric ID of the cube

  • path: Array of element names, one per dimension in cube order

  • value: The value to write (number or string)

  • splash_mode: How to handle writes to consolidated/parent elements:

    • "SET" (default): Direct write; for base elements this always works

    • "ADD": Adds to existing value

    • "ALLOCATE": Proportionally distributes value to base-level cells

Returns: { success: true, path, value }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
database_idYes
cube_idYes
pathYesOne element name per cube dimension in order. Use jedox_get_cube to confirm dimension order.
valueYesThe value to write. Use a number for numeric cells, string for string cells.
splash_modeNoHow to write to consolidated/parent cells: SET=overwrite (may fail for locked consolidated cells), ADD=add to existing value, ALLOCATE=distribute value proportionally down to base elements. For base-level elements always use SET.SET
Behavior4/5

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

Detailed explanation of persistence and splash_mode behaviors (SET, ADD, ALLOCATE), including potential failure for locked consolidated cells. Annotations only provide hints, so description adds substantial behavioral context.

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?

Two sentences plus an Args block, all essential information. Front-loaded with purpose, then persistence note, then parameter descriptions. No redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers key aspects: write behavior, persistence, splash modes, path, and return format. Lacks details on error handling or permissions, but overall adequate for a simple write tool with no output schema.

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?

Adds practical context beyond schema: explains path ordering and suggests confirming with jedox_get_cube, clarifies splash_mode options for different cell types. Schema already has some descriptions, but description enhances usability.

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?

Explicitly states 'Write a value to a cell in a Jedox cube,' clearly specifying the action and resource. Differentiates from sibling tools like jedox_get_cell_value (read) and bulk operations.

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

Usage Guidelines3/5

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

Provides guidance on splash_mode for consolidated cells and notes that writes persist immediately, avoiding need for save. However, lacks explicit comparison with alternative write tools or scenarios to avoid.

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/emilabd247/work-jedox-mcp-server'

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