Skip to main content
Glama

drop_table

Destructive

Permanently delete a database table only after explicit confirmation; use dry-run to preview the destructive action before execution.

Instructions

Permanently drop a table. Requires confirm=true; use dry_run=true to preview.

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": {
      "table": "<table>"
    },
    "name": "drop_table"
  }
}

Input Schema

NameRequiredDescriptionDefault
tableYes
confirmNoMust be true to execute this destructive operation.
dry_runNoPreview what would happen without changing anything.
workspaceNoNamed workspace. Omit to use the default workspace.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/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; the description adds that the effect is permanent and that a confirm token is required, which goes beyond the annotation set. It does not mention what happens to dependent objects, permissions, or whether the operation is recoverable.

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 compact clauses, zero filler, with the destructive nature and the safety gate front-loaded ahead of the preview option.

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 destructive four-parameter tool with annotations covering the safety profile, the description covers the essential gating and preview behavior. Missing details (effect on dependents, workspace scoping) are secondary given the annotation coverage.

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 75% and the schema itself documents confirm, dry_run, and workspace. The description only restates the two flags already described in the schema and adds nothing about `table` (the required, undescribed parameter) or workspace scoping, 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?

'Permanently drop a table' names a specific verb and resource, and the adverb 'Permanently' signals irreversibility. It is clearly distinct from list_tables/describe_table siblings, though it does not explicitly differentiate itself from them.

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?

States the mandatory prerequisite (confirm=true) and offers the dry_run=true preview path, which is real when-to-use guidance. It stops short of saying when not to use it or which sibling to reach for instead (e.g., truncate-style alternatives, if any).

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.