Skip to main content
Glama
openl-tablets

OpenL MCP Server

Official
by openl-tablets
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

Merge Table Cells (raw)

openl_merge_table_cells
Idempotent

Merge a rectangular range of cells into one in a table's raw source, preserving the top-left cell's value. Works on raw source for any table type, with 0-based positioning.

Instructions

Merge a rectangular range of cells into one in a table's raw source, keeping the value of the top-left cell at ('row','column'). The range ('rowspan'×'colspan') must cover more than one cell and stay within the table. Operates on the table's RAW source, so it works for any table type. Positions are 0-based (row 0 is the header row, column 0 carries the leading labels). An edit that relocates the table (it had no room to grow in place) CHANGES its location-derived id; the response always returns the table's CURRENT id as 'tableId' (plus previousTableId when it changed) — use it for subsequent calls. Note: the studio does not auto-compile after an edit; this tool reads the table back to trigger the recompile, so a subsequent openl_project_status reflects the change.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
rowYes0-based row index of the top-left cell of the range (0..height-1).
columnYes0-based column index of the top-left cell of the range (0..width-1).
colspanYesNumber of columns the merged cell spans (>= 1).
rowspanYesNumber of rows the merged cell spans (>= 1).
tableIdYesTable identifier - unique ID assigned by OpenL Studio (e.g., 'calculatePremium_1234'). VOLATILE: derived from the table's location, so it changes when an edit relocates the table (it had no room to grow in place) — use the 'tableId' returned by the latest openl_update_table/openl_append_table response, or refresh via openl_list_tables().
projectIdYesProject ID returned by backend. Use the exact 'projectId' value from openl_list_projects() response without modification or reformatting.
response_formatNoResponse format: 'json' for structured data, 'markdown' for human-readable (default), 'markdown_concise' for brief summary (1-2 paragraphs), 'markdown_detailed' for full details with contextmarkdown

Tool Definition Quality

A4.5/5.0
Behavior5/5

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

Goes beyond annotations by disclosing that the edit may relocate the table (changing its id), that it reads the table back to trigger recompile, and that the top-left cell's value is preserved. Annotations (openWorldHint, idempotentHint) are consistent with this behavior.

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 moderately long but each sentence adds value. Information is front-loaded with purpose, then constraints and side effects. Could be slightly more concise by grouping related details, but it is well-structured.

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 7 parameters and no output schema, the description covers all essential aspects: what the tool does, constraints (range must be >1 cell, within table), coordinate system, id volatility, recompile trigger, and response contents. Provides a complete mental model for correct usage.

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 description coverage is 100%, and the description adds useful context: coordinate system details, tableId volatility explanation, and response_format options. It enhances understanding beyond the schema alone.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it merges a rectangular range of cells into one, keeping the top-left cell's value, and operates on the table's raw source. It implicitly distinguishes from unmerge via sibling name, but does not explicitly contrast with other table editing tools.

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?

Provides explicit guidance: positions are 0-based, row 0 is header, column 0 is labels; warns that the table's id may change upon relocation; instructs to use the returned 'tableId' for subsequent calls; notes the tool triggers a recompile. This helps the agent decide when and how to use the tool.

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/openl-tablets/openl-mcp'

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