Skip to main content
Glama
Sign In
vish288

mcp-coda

by vish288
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Coda Update Row

coda_update_row
Idempotent

Update specific column values in a single Coda table row, leaving other columns unchanged; returns a request ID to track the async change.

Instructions

Update a single row in a Coda table.

Updates specific column values for one row. Only the specified columns are changed — other columns are left unchanged. Use column names (not IDs). For bulk updates, use coda_insert_rows with key_columns (upsert) instead. Returns a requestId for async mutation tracking.

Input Schema

NameRequiredDescriptionDefault
cellsYesColumn values to update. List of {column: name, value: val} objects. Example: [{'column': 'Status', 'value': 'Done'}]
doc_idYesThe doc ID containing the table
row_id_or_nameYesRow ID or name to update
table_id_or_nameYesTable ID or name

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.12.1
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "result": {
-      "type": "string"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "type": "object",
-  "x-fastmcp-wrap-result": true
-}New value: +null
  2. First observedv0.4.14

TDQS

A4.4/5.0
Behavior4/5

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

Annotations cover the safety profile (readOnlyHint=false, idempotentHint=true, openWorldHint=true), and the description adds real context beyond them: partial-update semantics ('only specified columns changed — others left unchanged'), the column-name requirement, and that it returns a requestId for async tracking. It does not state permission requirements, but the async-return disclosure is substantive.

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?

Front-loaded with the core operation, then quickly layers scope, caveat, alternative, and return behavior. Every sentence adds information with no filler.

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

Completeness4/5

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

For a mutation tool with no output schema, the description covers partial-update behavior and the async return value. It omits error/failure modes and any permission prerequisites, but is otherwise complete enough to call correctly.

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?

Schema description coverage is 100%, so all four parameters are documented in the schema, making 3 the baseline. The description adds only one useful bit ('use column names, not IDs'), which the schema's own example already implies, so it doesn't meaningfully exceed 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?

States a specific verb and resource ('Update a single row in a Coda table') and scopes it with 'single row,' which distinguishes it from bulk-update siblings. An agent can identify the operation without opening the schema.

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?

Explicitly routes bulk operations to the alternative: 'For bulk updates, use coda_insert_rows with key_columns (upsert) instead.' This gives both the when (single-row update) and the when-not (bulk) with the named sibling, leaving little to inference.

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