Databar MCP Server

Official

by databar-ai

Overview Schema Source Related Servers Discussions Admin

TypeScript

Remote

delete_rows

Delete specific rows from a table by their row IDs. Remove unwanted data entries to clean up your database.

Instructions

Delete specific rows from a table by their row IDs.

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_uuid": "<table_uuid>",
      "row_ids": "<row_ids>"
    },
    "name": "delete_rows"
  }
}

Input Schema

Name	Required	Description	Default
`table_uuid`	Yes	The UUID of the table
`row_ids`	Yes	Array of row IDs to delete

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.4.0May 29, 2026

TDQS

B3.3/5.0

Behavior2/5

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

No annotations exist, and the description fails to disclose side effects, permanence, error handling for missing IDs, or authorization needs. For a destructive operation, this is insufficient.

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?

Single sentence, no fluff, directly communicates the essential function. Concisely structured.

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

Completeness3/5

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

Adequate for a simple tool with two parameters and no output schema, but lacks behavioral context that would help an agent understand implications of deletion.

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 the description adds little beyond the schema. The schema already explains the parameters; the description only echoes the purpose.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action (delete), the resource (specific rows), and the method (by their row IDs). It distinguishes from sibling tools like delete_table and delete_column.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool versus alternatives like patch_rows or upsert_rows. No prerequisites or conditions provided.

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