Databar MCP Server

Official

by databar-ai

Overview Schema Source Related Servers Discussions Admin

TypeScript

Remote

create_column

Add a new column to an existing table by providing the table UUID, column name, and optional type.

Instructions

Add a new column to an existing 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": {
      "table_uuid": "<table_uuid>",
      "name": "<name>"
    },
    "name": "create_column"
  }
}

Input Schema

Name	Required	Description	Default
`table_uuid`	Yes	The UUID of the table
`name`	Yes	Column display name
`type`	No	Column type (default: 'text')	text

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.4.0May 29, 2026

TDQS

B3.1/5.0

Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits. It only states the action without mentioning side effects (e.g., default values, nullable restrictions), permissions required, or whether the operation is reversible.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, concise sentence. However, for a mutation tool, it may be too brief, lacking necessary behavioral context. Front-loading is acceptable but could benefit from additional details.

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

Completeness2/5

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

Given the tool modifies table schema (a potentially impactful operation), with no output schema or annotations, the description is incomplete. It does not explain return values, error scenarios, or permissions, leaving gaps for the agent.

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 schema already defines parameters clearly. The description adds no further meaning beyond what the schema provides, such as explaining the 'type' parameter options or naming constraints.

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 'Add a new column to an existing table,' specifying the verb (add), the resource (column), and the context (existing table). This distinguishes it from sibling tools like 'delete_column' or 'rename_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?

The description provides no guidance on when to use this tool versus alternatives such as 'rename_column', 'delete_column', or other table-modifying tools. It lacks prerequisites or context about the table state.

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