Centia MCP Server

Official

Overview Schema Source Related Servers Discussions Admin

postColumn

Add new columns to a database table by specifying schema, table, and column definitions including name, data type, nullability, default values, identity generation, and comment.

Instructions

Create new column(s).

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": {
      "schema": "<schema>",
      "table": "<table>",
      "requestBody": "<requestBody>"
    },
    "name": "postColumn"
  }
}

Input Schema

Name	Required	Description
`schema`	Yes	Schema name
`table`	Yes	Table name
`requestBody`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.9May 26, 2026

TDQS

C2.7/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 bear the full burden of behavioral disclosure. It only states 'Create new column(s)' without mentioning permissions, side effects (schema modification), validation, error handling, or return behavior. The schema details parameter types but not behavioral traits.

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

Conciseness3/5

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

The description is a single short sentence, which is concise. However, it is under-specified for a tool with three required parameters and no annotations. A slightly longer description could add valuable context without sacrificing conciseness.

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

Completeness1/5

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

Given the tool's complexity (3 params, no output schema, no annotations), the description is severely incomplete. It does not explain the tool's effect (modifying table schema), prerequisites, behavior for multiple columns, or any constraints. The agent would lack essential context to use it correctly.

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?

The input schema already provides descriptions for all three parameters (schema, table, and nested requestBody definitions), covering 100% of parameters. The tool description adds no additional parameter context beyond the schema, aligning with the baseline score of 3 for high schema coverage.

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?

The description states 'Create new column(s).' It clearly indicates the verb (create) and resource (column), distinguishing it from siblings like patchColumn (update) and deleteColumn. However, it does not explicitly mention that it adds columns to an existing table, which is implied by the schema parameters.

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. It does not specify prerequisites (e.g., table must exist), when to use multiple columns, or mention any equivalent or alternative tools. The sibling list is large but no direction is given.

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