Skip to main content
Glama

update_data_table

Update a Persistent Data Table: rename, addFields, fieldOrder, updateFields (description only), and/or queueConfig. Type change is not supported. Use rename_data_table_field / delete_data_table_field for column rename and delete. At least one of name, addFields, fieldOrder, updateFields, or queueConfig is required. Setting queueConfig on an empty non-queue table seeds reserved queue fields; refused if the table already has rows.

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": {
      "id": "<id>"
    },
    "name": "update_data_table"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesData table id
nameNoOptional new display name
addFieldsNoFields to add: { name, type, required?, description? }
fieldOrderNoExisting field ids in display order (every current field exactly once)
queueConfigNoMarks the table as a Queue Table. Seeds reserved fields status, priority, claimedAt, pausedAt, attempts, lastError (those names cannot be renamed or deleted while set).
updateFieldsNoDescription-only patches: { id, description }. null or "" clears. Identify Fields by id.

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the mutation profile is known; the description adds real value beyond that by disclosing refusal conditions (queueConfig on a table with rows), side effects (seeding reserved fields status/priority/claimedAt/etc.), and a hard limitation (no type change). It stops short of describing outcomes such as rename collisions or what the response returns, which keeps it at a 4 rather than 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?

Content is front-loaded: the operation list comes first, then constraints, then the edge case. Every sentence carries information, though the opening list is dense and the parenthetical '(description only)' plus the trailing queueConfig sentence make it slightly hard to scan for an agent skimming.

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 6-parameter mutation tool with nested objects and no output schema, the description covers all supported operations, the required 'at least one' rule, and the one genuinely surprising behavior (queue seeding). Gaps remain around failure modes (duplicate names, invalid field ids in fieldOrder) and whether the caller gets the updated table back, but nothing essential for correct invocation is missing.

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 the baseline is 3; the description raises it by clarifying intent the schema does not state, notably that updateFields is 'description only' and that type changes are rejected. The clause about reserved field names being unrenamable while queueConfig is set further constrains how fieldOrder and updateFields may be used.

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 a specific verb+resource ('Update a Persistent Data Table') and immediately enumerates the exact operations supported (rename, addFields, fieldOrder, updateFields, queueConfig). It explicitly carves out what is NOT this tool ('Type change is not supported') and names the siblings that handle column rename/delete, so an agent can distinguish it from rename_data_table_field and delete_data_table_field without opening schemas.

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?

It states the preconditions ('At least one of name, addFields, fieldOrder, updateFields, or queueConfig is required') and routes column rename/delete to the dedicated siblings by name. The queueConfig edge case ('seeds reserved queue fields; refused if the table already has rows') tells the agent precisely when that operation will and will not work.

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