Centia MCP Server

Official

by mapcentia

Overview Schema Source Related Servers Discussions Admin

TypeScript

Local

postEvents

Enable or disable event triggers on database tables by specifying schema, table name, and activation status.

Instructions

Install event trigger.

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>",
      "enabled": "<enabled>"
    },
    "name": "postEvents"
  }
}

Input Schema

Name	Required	Description
`schema`	Yes	Schema name
`table`	Yes	Table name
`enabled`	Yes	Enable or disable events for this table.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.9May 26, 2026

TDQS

C2.8/5.0

Behavior2/5

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

With no annotations, the description bears full burden for behavioral disclosure. 'Install event trigger' does not reveal if the operation is idempotent, what happens to existing triggers, or any permissions needed. The 'enabled' parameter suggests toggling, but this is not explained.

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 extremely concise (4 words) but may be too brief, lacking structure and essential information. While no extra words are wasted, the brevity undermines utility.

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?

For a tool with 3 required parameters and no output schema, the description lacks context about return values, side effects, or relationship to other tools. Incomplete for an agent to use effectively.

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 coverage is 100%, so parameters are well-documented in the schema. However, the description adds no extra meaning beyond what the schema provides, barely meeting the baseline of 3.

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 'Install event trigger' uses a specific verb and resource, clearly indicating the tool's action. However, it does not differentiate from sibling tools like postConstraint or postIndex, which could be clarified.

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 on when to use this tool versus alternatives. Sibling tools like getEvents exist for reading, but no context is provided. The description implies use for installation but lacks explicit when-to or when-not-to advice.

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