Skip to main content
Glama

upsert_data_table_record

Idempotent

Full replace of record data by recordKey (creates if missing). Last-write-wins with no version check. Use for idempotent imports; prefer update_data_table_record when concurrent writers must not overwrite each other.

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>"
    },
    "name": "upsert_data_table_record"
  }
}

Input Schema

NameRequiredDescriptionDefault
dataYesFull field object (replaces existing data)
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

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false and idempotentHint=true, and the description adds meaningful context beyond them: last-write-wins with no version check, and that data is fully replaced rather than merged. It doesn't describe the response payload or failure modes on missing tables, keeping it short of a 5.

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 tight clauses: operation, concurrency semantics, then usage guidance — front-loaded and waste-free, though telegraphic phrasing ('Full replace of record data by recordKey') slightly compresses clarity.

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?

Covers the two high-risk facts an agent needs for a mutating upsert: full replacement of existing data and no version check. No output schema exists, so return-shape guidance would be additive but is not essential for correct invocation.

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 baseline is 3; the description reinforces that 'data' is replaced wholesale and that recordKey is a business key, but adds no format or constraint detail beyond 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 ('Full replace of record data by recordKey') and clarifies create-if-missing semantics, which distinguishes it from the sibling create/update tools.

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 names when to use it ('Use for idempotent imports') and names the alternative plus the condition that selects it ('prefer update_data_table_record when concurrent writers must not overwrite each other').

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