Syncretica MCP Server

populate_pantheon_gods

Generates and adds deities to a chosen pantheon through LLM-based discovery, with an option to wait synchronously for completion.

Instructions

Discover and populate deities for a specific pantheon via LLM generation.

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": {
      "id": "<id>"
    },
    "name": "populate_pantheon_gods"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	Pantheon ID
`sync`	No	If true, wait synchronously for deity generation to finish

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Nov 13, 2026

TDQS

C2.9/5.0

Behavior2/5

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

With no annotations, the description carries the full behavioral burden. It does disclose that generation happens via LLM (implying non-determinism, latency, and possible cost), but it never says whether existing deities are overwritten, whether the call is idempotent, what happens if the pantheon ID is invalid, or whether it requires elevated permissions.

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?

A single front-loaded sentence with no filler. Minor ambiguity from pairing 'Discover and populate' without clarifying whether discovery is a separate pre-step, but nothing is wasted.

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 mutating, LLM-backed generation tool with no annotations and no output schema, the description is too thin. An agent cannot tell what the call returns (created deity records? job handle?), how long a synchronous call may block, or what state changes result, all of which the description would need to cover.

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%, so both the 'id' and 'sync' parameters are already documented in the schema, including the default and the synchronous-wait semantics of 'sync.' The description adds no parameter-level meaning beyond that, so the baseline 3 applies.

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?

States a specific verb and resource: 'Discover and populate deities for a specific pantheon via LLM generation.' The phrase 'for a specific pantheon' implicitly distinguishes it from populate_gods_bulk and populate_pantheons, but it never names those alternatives or makes the single-vs-bulk distinction explicit.

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?

There is no when-to-use or when-not-to-use guidance, no prerequisites (e.g., the pantheon must already exist), and no direction on choosing between this and populate_gods_bulk. The only usage signal is the implicit single-pantheon scoping in the phrase 'a specific pantheon.'

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