Centia MCP Server

Official

by mapcentia

Overview Schema Source Related Servers Discussions Admin

TypeScript

Local

getEvents

Check if an event trigger is enabled for a specified schema and table in Centia.

Instructions

Check if event trigger is enabled.

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": "getEvents"
  }
}

Input Schema

Name	Required	Description	Default
`schema`	Yes	Schema name
`table`	No	Table name

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.9May 26, 2026

TDQS

B3.2/5.0

Behavior2/5

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

With no annotations, the description must fully disclose behavior, but it only states the action. It does not explain whether the operation is read-only, requires special permissions, or what happens if the event trigger does not exist. The agent is left to infer the safety and side effects.

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

Conciseness5/5

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

The description is a single, concise sentence that immediately states the tool's purpose. There is no extraneous information, and it is front-loaded for quick understanding.

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 tool's simplicity (2 parameters, no output schema), the description should at least hint at the return format (e.g., boolean, object). It fails to do so, leaving the agent uncertain about what to expect from the tool. The lack of output schema exacerbates this gap.

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 the input schema already describes the two parameters (schema and table). The description adds no further meaning about how these parameters relate to an 'event trigger' or what values are valid. Baseline 3 is appropriate as the schema carries the burden.

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

Purpose5/5

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

The description 'Check if event trigger is enabled' uses a specific verb ('check') and resource ('event trigger'), clearly distinguishing it from sibling tools like getTable or getColumn. It is unambiguous and immediately conveys the tool's function.

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?

The description provides no guidance on when to use this tool versus alternatives (e.g., getTable or postEvents). It lacks any indication of context, prerequisites, or scenarios where this tool is preferred. An agent has no direction on selecting it over other 'get' tools.

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