Skip to main content
Glama
openl-tablets

OpenL MCP Server

Official

Update Table Cell (raw)

openl_update_table_cell
Idempotent

Update any table cell's value by specifying its zero-based row and column index. Pass a value to set or null to clear; the response includes the current table identifier.

Instructions

Update the value of a single existing cell at ('row','column') in a table's raw source. 'value' is required: pass a string/number/boolean to set the cell, or null to clear it. 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 cell (0..height-1).
valueYesNew cell value (string, number, or boolean) to set, or null to clear the cell. Required — pass null explicitly to clear so the intent is unambiguous.
columnYes0-based column index of the cell (0..width-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
Behavior4/5

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

Annotations declare openWorldHint=true and idempotentHint=true. The description adds critical behavioral details: edit may relocate table (changing its ID), response returns current tableId and previousTableId when changed, and the tool triggers a recompile by reading the table back. This goes beyond what annotations provide.

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 five sentences with no fluff. Each sentence adds value: purpose, value explanation, raw source applicability, index conventions, ID volatility, and recompile behavior. It is front-loaded and efficient.

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?

Despite lacking an output schema, the description covers all key aspects: parameter usage, side effects (ID change, recompile), and index conventions. It is complete for an agent to correctly invoke the tool, given the required parameters and behavioral notes.

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%, so baseline is 3. The description adds meaning beyond the schema: it explains that value is required, positions are 0-based, row 0 is header, column 0 is labels, and the volatility of tableId. This provides valuable context.

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 updates a single cell at a given (row, column) in a table's raw source. It specifies the value can be string/number/boolean or null to clear. The title 'Update Table Cell (raw)' matches the description, and it distinguishes from sibling tools that operate on full tables, columns, or rows.

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?

The description provides context on when to use: it works on the raw source for any table type. It mentions 0-based positions and that row 0 is header, column 0 is labels. It does not explicitly contrast with siblings like openl_update_table_range or openl_update_table_row, but the unique purpose is clear.

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