Centia MCP Server

Official

Overview Schema Source Related Servers Discussions Admin

postRule

Define rules to allow, deny, or restrict SQL queries with a WHERE filter, matching by user, service, table, schema, or IP range.

Instructions

Create rule(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": {
      "requestBody": "<requestBody>"
    },
    "name": "postRule"
  }
}

Input Schema

Name	Required	Description	Default
`requestBody`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.9May 26, 2026

TDQS

D1.7/5.0

Behavior1/5

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

No annotations are provided, and the description does not disclose any behavioral traits such as idempotency, side effects, authorization requirements, or what happens upon success/failure. The brief description fails to compensate for missing annotations.

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 it lacks substance. It is under-specified rather than appropriately concise, providing no actionable information.

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 complexity (oneOf, nested objects, many fields), no output schema, and no annotations, the description is woefully incomplete. It should at minimum state that the tool creates access-control rules for SQL and mention the option to create one or multiple rules.

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

Parameters1/5

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

The tool description does not add any meaning beyond what the input schema provides. With schema description coverage at 0% (the description mentions no parameters), it fails to summarize or clarify the complex oneOf structure. The schema itself has rich descriptions, but the tool's description does nothing to help an agent understand when to use single object vs array.

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 'Create rule(s).' is a tautology that restates the function name 'postRule'. It lacks specificity about what kind of rules (access-control rules for SQL) are created, which is only clarified later in the schema description.

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 like postClient, postTable, etc. The agent is given no context for decision-making.

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