Skip to main content
Glama

delete_data_table_field

Destructive

Delete a field from a Persistent Data Table. Strips that key from every record and increments each record version. Refuses to delete the last field or reserved queue fields. Use when removing a column permanently.

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": "delete_data_table_field"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesData table id
fieldIdYesField id from get_data_table

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.3/5.0
Behavior5/5

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

Annotations only declare destructiveHint=true and readOnlyHint=false, but the description goes well beyond that: it discloses the mutation pattern (strips the key from every record, increments each record version) and the guardrails (refuses on the last field or reserved queue fields). That is exactly the side-effect and failure-mode context an agent needs before a destructive call.

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?

Three short sentences, front-loaded with the action, followed by consequences and then constraints. No filler and nothing repeated from the schema.

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

Completeness5/5

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

For a two-parameter destructive tool with full schema coverage and annotations, this covers the missing pieces: what happens to existing records, the version bump, and the cases where the call is refused. Nothing an agent needs in order to invoke it correctly is absent.

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 the schema already explains both 'id' and 'fieldId', including that fieldId comes from get_data_table. The description adds no additional parameter meaning, so the baseline 3 applies.

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?

States a specific verb plus a precisely scoped resource ('Delete a field from a Persistent Data Table'), which naturally separates it from delete_data_table and delete_data_table_record. It stops short of naming those siblings explicitly, so the distinction relies on the noun rather than on routing language.

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?

'Use when removing a column permanently' gives a clear trigger condition and signals irreversibility. It does not state when NOT to use it or point to alternatives such as delete_data_table for dropping the whole table, so the guidance is clear but not exhaustive.

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