Centia MCP Server

Official

Overview Schema Source Related Servers Discussions Admin

postSequence

Create sequences in a database schema with configurable increment, start value, and caching. Supports single or batch sequence creation.

Instructions

Create sequence(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>",
      "requestBody": "<requestBody>"
    },
    "name": "postSequence"
  }
}

Input Schema

Name	Required	Description	Default
`schema`	Yes	Schema name
`requestBody`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.9May 26, 2026

TDQS

D1.5/5.0

Behavior1/5

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

No annotations provided. Description fails to disclose any behavioral traits such as whether the operation is destructive, requires permissions, or has side effects. No mention of sequence properties or return behavior.

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

Conciseness2/5

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

Overly brief to the point of being uninformative. Two words do not constitute a useful description; valuable information is sacrificed for brevity.

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 creates database sequences and has multiple sibling tools, the description should explain what a sequence is and when to use it. It is entirely insufficient for an agent to decide to invoke this tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 50%, but the description adds no value beyond the schema. It does not explain the purpose of parameters or provide examples. For instance, it does not clarify that 'requestBody' can be a single object or an array for batch creation.

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

Purpose2/5

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

Description 'Create sequence(s)' is a tautology of the tool name 'postSequence'. It does not specify what a sequence is (e.g., database sequence for generating numeric values) and does not differentiate from other creation tools like postTable or postColumn.

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

Usage Guidelines1/5

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

No guidance on when to create a sequence versus alternatives such as postTable or postSchema. The description lacks any context for appropriate usage.

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