Centia MCP Server

Official

Overview Schema Source Related Servers Discussions Admin

getSchema

Retrieve database schemas with optional filtering by schema name. Choose to return only schema names, omitting tables and sequences.

Instructions

Get schema(s).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "getSchema"
  }
}

Input Schema

Name	Required	Description	Default
`schema`	No	Schema name
`namesOnly`	No	Return only schema names (omit tables and sequences).

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.9May 26, 2026

TDQS

C2.1/5.0

Behavior2/5

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

No annotations are provided, and the description lacks any behavioral details such as whether the operation is read-only, what side effects exist, or authorization requirements. The one-word description is insufficient.

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?

The description is extremely short but not appropriately informative. It lacks structure and fails to convey useful information, making it under-specified rather than concise.

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?

The tool has no output schema and no annotations, yet the description is completely inadequate. It does not explain what the tool returns, how parameters affect results, or any usage context.

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 documentation coverage is 100%, so the input schema already describes both parameters adequately. The description adds no additional meaning beyond what is in the schema, warranting a baseline 3.

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?

The description 'Get schema(s)' is essentially tautological, restating the tool name without specifying what kind of schema or what the output contains. It does not distinguish from sibling tools like getTable or getColumn.

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. With many sibling get tools, the description offers no context for selection.

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