Skip to main content
Glama
oborchers

tablestakes

by oborchers
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

update_cells

Batch-update cells in a Markdown table using row, column, and value. Requires a current version hash to prevent stale writes; retry after re-reading on conflict.

Instructions

Batch-update cells. Requires version hash from read_table.

Each update is {row, column, value} where:

  • row: 0-based data row index (header row is NOT counted)

  • column: letter ("A"), name ("Priority"), or composite ("B:Priority")

  • value: new cell content (Markdown inline formatting supported)

On success returns ONLY v:{new_hash}. On error returns JSON: {"error": "STALE_READ"|"EDIT_ERROR"|..., "message": "..."}. If STALE_READ: call read_table again for current version, then retry.

Args: file_path: Absolute path to the Markdown file. table_index: 0-based table index from list_tables. version: 12-char hex hash from read_table (after "v:", e.g. "a1b2c3d4e5f6"). updates: List of {row: int, column: str, value: str} objects.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
updatesYes
versionYes
file_pathYes
table_indexYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.8/5.0
Behavior5/5

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

With no annotations, the description carries full behavioral disclosure. It specifies the exact success return format, the error JSON shape, the STALE_READ recovery workflow, row indexing semantics, and accepted column formats.

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 structured with a short summary followed by bullet point format definitions, return behavior, and per-argument explanations. Every section adds necessary operational detail without redundancy.

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 no annotations and no output schema, the description covers the full calling context: prerequisites, argument semantics, success and error responses, retry logic, and data indexing rules. An agent can invoke and recover from failures without external knowledge.

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

Parameters5/5

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

Schema description coverage is 0%, and the description compensates fully. It explains every parameter in Args, adds semantic detail absent from the schema, and precisely documents version as a 12-char hex hash and column as letter/name/composite.

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 opens with 'Batch-update cells,' a specific verb and resource that clearly states the operation. It also names the prerequisite version hash and the update object shape, distinguishing it from sibling tools like insert_row and replace_table.

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 clearly conveys when to use this tool: after reading a table to obtain a version hash. It includes explicit retry guidance for STALE_READ errors but does not explicitly contrast the tool with siblings or state when not to use it.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools