Centia MCP Server

Official

by mapcentia

Overview Schema Source Related Servers Discussions Admin

TypeScript

Local

getSequence

Retrieve database sequences from a specific schema, with an option to filter by sequence name.

Instructions

Get 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>"
    },
    "name": "getSequence"
  }
}

Input Schema

Name	Required	Description	Default
`schema`	Yes	Schema name
`sequence`	No	Sequence names

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.9May 26, 2026

TDQS

C2.5/5.0

Behavior2/5

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

With no annotations, the description must disclose behavioral traits. It only states the operation ('Get') without indicating whether it is read-only, what it returns, or any permissions needed. The minimal description fails to add context beyond the tool name.

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 front-loaded but sacrifices useful information. It is technically concise but underspecified, earning a 3.

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 no output schema and no annotations, the description should offer more context about what the tool returns, how sequences are identified, or usage examples. The current description is insufficient for a complete understanding.

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 has 100% coverage with descriptions for both parameters. The description adds no extra semantic detail, 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.

Purpose3/5

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

The description 'Get sequence(s)' conveys the verb and resource, but is vague. It does not clarify what a sequence is in this context, and compared to sibling tools like getTable or getSchema, it lacks specificity. A score of 3 reflects that the purpose is clear but not well-defined.

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 is provided on when to use this tool versus alternatives such as getSchema or getTable. There is no mention of prerequisites, context, or when not to use it, leaving the agent without decision support.

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