Skip to main content
Glama

delete_data_table_record

Destructive

Permanently delete one record by recordKey. Use when removing a row the user no longer needs.

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

Input Schema

NameRequiredDescriptionDefault
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 already declare destructiveHint=true and readOnlyHint=false, so the bar is lower. The description adds the meaningful qualifier 'Permanently', making clear there is no undo/soft-delete path — a real behavioral fact beyond the annotation. It stops short of saying what happens when recordKey does not exist or whether related data is affected.

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?

Two short sentences with zero filler; the destructive, key-based nature is front-loaded and the usage hint follows. Nothing repeats the title or restates the obvious.

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 two-parameter deletion tool with full schema coverage, annotations, and no output schema, the definition covers purpose, target, and irreversibility adequately. Only edge-case behavior (missing key, permission requirements, error/response shape) is unaddressed, which is a minor 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 coverage is 100%, so both dataTableId and recordKey are documented in the schema, and the description only echoes that targeting is by recordKey ('Business key unique within the table'). No additional format, scope, or lookup semantics are added beyond the schema, 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?

Specific verb+resource: 'Permanently delete one record by recordKey' states the operation, the unit of deletion (one record), and the key used to target it. The contrast with delete_data_table is implied by 'one record' rather than a whole table, so an agent can distinguish them, though no sibling is named explicitly.

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?

'Use when removing a row the user no longer needs' gives a usage condition, but it offers no exclusions or alternatives — e.g. whether to prefer update_data_table_record when the row should be retained, or when delete_data_table is the right call. Guidance is implied rather than explicit.

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