Skip to main content
Glama
Sign In
Centia MCP Server

Centia MCP Server

Official
by mapcentia
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

postRpc

Define reusable JSON-RPC methods that wrap SQL statements with optional type hints and output formats.

Instructions

Create JSON-RPC method definitions.

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

Input Schema

NameRequiredDescriptionDefault
requestBodyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.9

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations, the description should disclose behavioral traits like side effects, permission requirements, or validation, but it only states the basic action without additional context.

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 single-sentence description is concise and front-loaded, but could be improved by including key context without reducing brevity.

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?

The description lacks information about return values, error handling, and the ability to pass an array of definitions, making it incomplete for a complex tool with a rich schema.

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?

The input schema includes detailed descriptions for all parameters (e.g., method, q, type_hints), so the tool description does not need to add meaning; baseline score applies.

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 'Create JSON-RPC method definitions' uses a specific verb and resource, clearly distinguishing it from sibling tools like deleteRpc, getRpc, and patchRpc.

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., patchRpc for updates, postCall for invocations) and lacks prerequisites or context.

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

Deploy Server

Other Tools