Skip to main content
Glama
Sign In
Centia MCP Server

Centia MCP Server

Official
by mapcentia
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

postCallDry

Dry-run an RPC call to infer and store input/output types without modifying the database.

Instructions

Dry-run an RPC call to infer and store input/output types. Dry-runs do not modify the database. Run this before requesting TypeScript types from /api/v4/interfaces.

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": {
      "jsonrpc": "<jsonrpc>",
      "method": "<method>"
    },
    "name": "postCallDry"
  }
}

Input Schema

NameRequiredDescriptionDefault
jsonrpcYesThe version number of the JSON-RPC protocol. Must be exactly "2.0".
idNoClient-supplied request id. If present, must be a string.
methodYesName of the RPC method to call.
paramsNoParameters for the method. For SELECT methods, only one parameter set is allowed.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.9

TDQS

A4/5.0
Behavior3/5

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

With no annotations, the description carries full burden. It discloses the key behavior (no database modification) but does not mention error handling, permissions, or what 'store' entails. Adequate but not rich.

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?

Two sentences, no wasted words. Efficiently conveys purpose and key usage hint.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/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 covered by schema, description explains purpose and a critical behavior. Could mention what happens on failure, but overall complete enough.

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 schema already documents all parameters. Description adds no extra meaning beyond the schema, meeting baseline.

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?

Clearly states 'Dry-run an RPC call to infer and store input/output types', specifying the verb and resource. Distinguishes from sibling postCall and getTypeScript by describing the workflow.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides explicit guidance: 'Run this before requesting TypeScript types' and states that dry-runs do not modify the database. Lacks explicit alternatives but implied by sibling names.

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