Syncretica MCP Server

populate_gods_bulk

Trigger bulk LLM discovery across all or a single pantheon to populate deity datasets, with optional synchronous completion waiting.

Instructions

Trigger bulk LLM discovery across all or a single pantheon.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "populate_gods_bulk"
  }
}

Input Schema

Name	Required	Description	Default
`sync`	No	If true, wait synchronously for completion
`pantheon_id`	No	Optional pantheon ID to scope bulk discovery

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?

No annotations are supplied, so the description carries the full behavioral burden, yet it discloses almost nothing beyond the trigger verb. It does not say whether this writes to the database, whether it is idempotent, what happens to existing god records, how long it takes, or what a caller receives (job handle vs results) when sync defaults to false.

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 zero filler, which is structurally clean. However, the brevity edges into under-specification for a bulk LLM trigger with no annotations to lean on.

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 an unannotated bulk LLM operation with no output schema, the description should explain async-vs-sync behavior, what is returned, and side effects. Instead it offers one clause, leaving an agent unable to predict the call's cost, duration, or result.

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 both parameters are already documented, including the sync flag's meaning and the optional nature of pantheon_id. The description's 'all or a single pantheon' reinforces the omitting-pantheon_id-means-all behavior but adds no format or interaction detail beyond the schema.

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 states a specific verb ('Trigger') and resource ('bulk LLM discovery') plus its scope ('all or a single pantheon'), so an agent can tell it is a bulk-population operation rather than a single-record read or write. It does not explicitly contrast itself with siblings like populate_myths_bulk or populate_pantheon_gods, though the tool name carries that differentiation.

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 guidance, no exclusions, and no mention of prerequisites such as cost, expected duration, or that an LLM call is involved. The only usage signal is the scope phrase 'all or a single pantheon', which the schema already conveys through the optional pantheon_id.

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