Skip to main content
Glama
emilabd247

Jedox MCP Server

by emilabd247

Get Jedox Cell Range

jedox_get_cell_range
Read-onlyIdempotent

Retrieve multiple cells from a Jedox cube by specifying dimension filter arrays. Builds a Cartesian product of filters to fetch specific cell values.

Instructions

Read multiple cells from a Jedox cube using dimension filters.

The tool builds a Cartesian product of your dimension filters to determine which cells to fetch. Keep filter arrays small to avoid exceeding max_cells.

Args:

  • database_id: Numeric ID of the database

  • cube_id: Numeric ID of the cube

  • dimension_filters: Array of arrays, one per dimension (in cube dimension order). Each inner array is the list of element names you want for that dimension. Example: [["Revenue","Cost","Profit"], ["Jan","Feb","Mar"], ["Total"]] → fetches 3 accounts × 3 months × 1 region = 9 cells

  • max_cells: Cap on total cells to return (default 1000, max 10000)

Returns: { cells: [{ path, value, type }], total }

Use jedox_get_cube first to confirm dimension order.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
database_idYes
cube_idYes
dimension_filtersYesArray of element name arrays, one per dimension in cube order. The Cartesian product of all arrays defines which cells to retrieve. Example: [['Jan','Feb'],['Revenue','Cost']] fetches 4 cells. Keep the total cell count under max_cells.
max_cellsNoMaximum cells to return. The Cartesian product of all dimension filters must not exceed this. Default: 1000.
Behavior4/5

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

The description explains the Cartesian product behavior and the max_cells constraint, adding value beyond annotations (readOnlyHint, idempotentHint, openWorldHint). It does not contradict annotations.

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 concise and well-structured, with a brief overview, behavioral explanation, parameter details, and return format. It uses bullet points effectively without extraneous text.

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 tool's complexity (Cartesian product, multiple dimensions), the description provides complete guidance: how to specify filters, cap cells, interpret results, and a prerequisite. No output schema exists, but the return format is described.

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?

Schema coverage is 50% (database_id and cube_id lack descriptions), but the description compensates by explaining the Cartesian product with an example and clarifying max_cells usage. It adds clear semantic meaning beyond the schema.

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 it reads multiple cells from a Jedox cube using dimension filters, distinguishing it from sibling tools like jedox_get_cell_value (single cell) and other write/update tools.

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?

It advises to use jedox_get_cube first to confirm dimension order, providing helpful context. However, it does not explicitly state when not to use this tool or mention alternatives.

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