Delete rows from a Turso database table by specifying the table name and a WHERE condition to target specific records.
Deleta dados de uma tabela
| Name | Required | Description | Default |
|---|---|---|---|
| table | Yes | Nome da tabela | |
| where | Yes | Condição WHERE (ex: 'id = 1') |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden of disclosing destructive behavior, but it only restates that data is deleted. It does not warn that deletion is irreversible or explain that rows matching the WHERE condition are permanently removed.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single short sentence with no wasted words, making it easy to parse. Its brevity is reasonable, though it sacrifices behavioral detail.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a destructive tool with no annotations and no output schema, the description is too thin. It should at least note the destructive/irreversible nature and possibly the transaction-related siblings (begin_transaction/rollback_transaction) available for safe usage.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so the table and where parameters are already documented. The description adds no parameter-specific meaning beyond the schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a clear action ('Deleta dados') on a specific resource ('uma tabela'), so an agent can distinguish it from insert/update/select siblings. It is slightly generic, repeating the tool name, but the resource target adds enough meaning.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is provided about when to use delete_data versus update_data, insert_data, or execute_select. The description does not mention relevant contexts such as removing matching rows or whether to wrap the operation in a transaction.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.