Databar MCP Server

Official

Overview Schema Source Related Servers Discussions Admin

delete_folder

Delete a folder in Databar without removing the tables it contains. Provide the folder ID to remove the folder structure.

Instructions

Delete a folder. Tables inside the folder are NOT deleted.

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": {
      "folder_id": "<folder_id>"
    },
    "name": "delete_folder"
  }
}

Input Schema

Name	Required	Description	Default
`folder_id`	Yes	The folder ID to delete

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.4.0May 29, 2026

TDQS

A3.8/5.0

Behavior3/5

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

With no annotations, the description carries full burden. It discloses that tables are not deleted, which is a non-obvious behavior. However, it omits details like required permissions, reversibility, or error states.

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 sentences, front-loaded with the main action. Every word is informative with no redundancy.

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 simple delete tool with one parameter, the description is fairly complete. It explains the behavior regarding tables inside. Could mention if folder must be non-empty or what happens to the tables, but overall sufficient.

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% and folder_id is described. The description adds no additional parameter details beyond the schema, so a baseline score of 3 is appropriate.

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) and the resource (folder), and distinguishes itself by noting that tables inside the folder are not deleted, which contrasts with potential misunderstandings.

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?

The description provides no explicit guidance on when to use this tool versus siblings like delete_table or delete_rows. However, it implicitly clarifies a key behavioral difference (tables inside not deleted), offering some context.

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