Centia MCP Server

Official

by mapcentia

Overview Schema Source Related Servers Discussions Admin

TypeScript

Local

postGraphQL

Execute GraphQL queries and mutations on Centia schemas with dynamic variables and operation selection.

Instructions

Run a GraphQL query or mutation.

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>",
      "query": "<query>"
    },
    "name": "postGraphQL"
  }
}

Input Schema

Name	Required	Description
`schema`	Yes	Schema name.
`query`	Yes	GraphQL query string. Queries read data; mutations modify data.
`variables`	No	Variables object for the GraphQL query.
`operationName`	No	Operation name to execute when the document contains multiple operations.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.9May 26, 2026

TDQS

C2.9/5.0

Behavior2/5

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

Without annotations, the description carries full burden but merely states 'Run a GraphQL query or mutation.' It fails to disclose that mutations are write operations, potential side effects, authentication needs, or error handling. The schema hint that queries read and mutations write is only in the parameter description, not the tool description.

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

Conciseness4/5

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

The description is a single, concise sentence that immediately states the action. It is front-loaded and contains no unnecessary words. While very brief, it is effectively structured for a simple tool.

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 4 parameters, the description lacks crucial context: what is returned (likely JSON), error behavior, schema parameter meaning, and operational context. The tool is moderately complex (arbitrary GraphQL execution), but the description does not compensate for the missing structured information.

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 description coverage is 100%, and parameter descriptions are clear (e.g., query clarifies read vs mutation). The tool description adds no additional meaning, so a baseline score of 3 is appropriate as the schema already provides semantic value.

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 'Run a GraphQL query or mutation' clearly specifies the action (run) and the resource (GraphQL query or mutation). It distinguishes the tool from siblings like postSql and postCall, which deal with SQL or function calls, though it could be more descriptive about the execution context.

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, nor does it mention prerequisites, scenarios, or exclusions. This leaves the agent without context for appropriate invocation.

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