Skip to main content
Glama

rename_data_table_field

Rename a field on a Persistent Data Table. Rewrites matching JSON keys on every record and increments each record version. Refuses reserved queue fields on tables with queueConfig. Use when changing a column name without deleting data.

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

Input Schema

NameRequiredDescriptionDefault
idYesData table id
nameYesNew field name (identifier)
fieldIdYesField id from get_data_table

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.4/5.0
Behavior5/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 well beyond that by disclosing the real side effects — matching JSON keys are rewritten on every record and each record version is incremented. It also discloses a validation constraint ('Refuses reserved queue fields on tables with queueConfig'), which is exactly the kind of failure mode an agent needs to anticipate. Nothing here contradicts the annotations: the mutation is non-destructive in that no data is deleted.

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?

Four short sentences: identity first, then side effects, then the refusal constraint, then the usage cue. Every sentence carries distinct information and none restates the title or schema.

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 three-parameter mutation tool with no output schema, the description covers the important unknowns: bulk record rewrites, version bumps, and the queueConfig rejection. It stops short of stating what the response returns or how name collisions are handled, which is a modest remaining gap.

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% and all three required parameters are documented in the schema, including that fieldId comes from get_data_table. The description adds no per-parameter detail such as name format restrictions (reserved names, identifier rules), so it sits at the baseline for schema-documented tools.

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 and resource ('Rename a field on a Persistent Data Table') and immediately scopes the operation to a single field, which separates it from table-level siblings like update_data_table. An agent can tell exactly what is being changed 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives an explicit use condition: 'Use when changing a column name without deleting data.' That implicitly contrasts with a delete-and-recreate path, but it does not name a sibling alternative or state when not to use it (e.g., queue-backed tables being rejected).

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