Skip to main content
Glama

update_data_table_record

Partial update (merge) of record data. Requires version matching the current record; stale version returns RECORD_CONFLICT with current. Use when safely editing fields under concurrent writers.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "dataTableId": "<dataTableId>",
      "recordKey": "<recordKey>",
      "data": "<data>",
      "version": "<version>"
    },
    "name": "update_data_table_record"
  }
}

Input Schema

NameRequiredDescriptionDefault
dataYesPartial field patch to merge
versionYesCurrent record version (optimistic lock)
recordKeyYesBusiness key unique within the table
dataTableIdYesData table id

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.8/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=false and destructiveHint=false; the description goes further by disclosing optimistic-concurrency behavior, the stale-version failure mode, and the specific RECORD_CONFLICT error that returns the current record. That is real behavioral context an agent cannot get from the annotations. It stops short of saying whether a merge is idempotent or what the success response contains.

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?

Three short sentences, front-loaded with the operation and merge semantics, followed by the failure mode and the usage cue. No filler, though the final "use when" sentence is the vaguest and could be sharper.

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 four-required-parameter mutation with a nested object and no output schema, the description covers the core semantics, the locking contract, and the conflict path. Remaining gaps are modest: what is returned on success, and any permission or rate-limit constraints.

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 coverage is 100%, so the four parameters are already documented, which sets the baseline at 3. The description earns above baseline by explaining the consequence of a stale version and by calling data a partial patch to merge, which clarifies how the nested object behaves under concurrency.

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?

"Partial update (merge) of record data" gives a specific verb (partial update/merge) and resource (record data), and the parenthetical spells out merge semantics rather than replacement. It does not name the sibling upsert_data_table_record or contrast with a full-record update, so the sibling differentiation is implied rather than stated.

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 clause "Use when safely editing fields under concurrent writers" does supply a usage condition tied to concurrency, which is more than nothing. However, it offers no alternatives (e.g., upsert vs. create), no when-not guidance, and no prerequisites such as how to obtain the current version before calling.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources