Skip to main content
Glama
openl-tablets

OpenL MCP Server

Official

Update Table Row (raw)

openl_update_table_row
Idempotent

Overwrites cells of an existing row at a specified position in a table, without resizing the table. Returns updated table ID for subsequent calls.

Instructions

Overwrite the cells of an existing row at 'position' (0..height-1) in a table's raw source, left to right. The table is not resized. 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
cellsYesRow cells, left to right. Required and non-empty — provide one cell per column (use { value: null } for a blank cell). A cell may set colspan/rowspan to merge. Must not be wider than the table.
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().
positionYes0-based index of the row to overwrite (0..height-1). The table is not resized.
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
Behavior4/5

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

The description discloses important behaviors beyond annotations: row numbering (row 0 is header), effect on table location-derived ID when relocation occurs, and that the tool triggers a recompile. Annotations provide openWorldHint and idempotentHint, which are consistent with the overwrite operation.

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 a single paragraph that front-loads the primary action and essential context. It is reasonably concise, though it could be slightly shorter by removing some redundant phrasing.

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

Completeness3/5

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

The description covers key behaviors (not resized, ID volatility, recompile trigger) but lacks details about the return structure beyond the tableId. Given no output schema, more information on the response format would improve completeness.

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

Parameters3/5

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

Input schema coverage is 100%, so the schema already documents parameters. The description adds contextual meaning (0-based positions, row 0 as header, column 0 as labels), which is useful but not extensive.

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 specifies the action (overwrite cells of an existing row) and the resource (table row at a 0-based position). It mentions it operates on raw source for any table type. However, it does not explicitly differentiate from sibling tools like openl_update_table_cell or openl_append_table_rows, which serve similar functions.

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?

The description implies when to use the tool (to overwrite a row) but lacks guidance on when not to use it or alternatives. For example, it does not compare with openl_update_table_cell for single-cell edits or openl_insert_table_rows for adding rows.

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