Skip to main content
Glama

delete_data_table

Destructive

Permanently delete a Persistent Data Table and all of its records. Use when the user no longer needs the table.

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

Input Schema

NameRequiredDescriptionDefault
idYesData table id

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the mutating nature is known. The description does add the key detail that the operation is permanent and cascades to all records, which is genuine context beyond the annotations, but it says nothing about recoverability, permissions, or dependent objects such as panels built on the table.

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, zero filler, with the permanence and cascade scope front-loaded before the usage hint. Every clause carries information an agent needs.

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 one-parameter destructive tool with no output schema and annotations covering the safety profile, this covers what gets destroyed and when to call it. The remaining gaps — recoverability and impact on dependent objects like panels or dashboards — are modest but real for an irreversible operation.

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% with a single documented "id" parameter, so the schema already carries the parameter meaning. The description adds no syntax, format, or lookup hints for the id, leaving this at the baseline level where the schema does all the work.

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 and resource ("Permanently delete a Persistent Data Table") and clarifies scope with "and all of its records", which implicitly separates it from the record-level delete_data_table_record sibling. It stops short of explicitly naming which sibling handles field- or record-level deletion, but the resource is unambiguous.

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 the user no longer needs the table" is a real but thin when-to-use cue that implies the destructive intent threshold. There is no when-not guidance (e.g., to remove records but keep the table, use a record-level tool) and no mention of confirmation or prerequisite checks before a permanent operation.

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