Syncretica MCP Server

list_gods

List and filter deities by name, pantheon, theme, and vector-embedding status, with pagination and optional myth or embedding details.

Instructions

List and filter deities with thematic tags and vector embedding status.

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

Input Schema

Name	Required	Description
`q`	No	Search name or description substring
`limit`	No	Pagination limit (default: 50)
`theme`	No	Filter deities containing thematic tag (e.g. 'thunder', 'wisdom')
`offset`	No	Pagination offset (default: 0)
`embedded`	No	Filter by whether vector embedding has been generated
`pantheon`	No	Filter by pantheon name substring
`pantheon_id`	No	Filter by pantheon ID
`include_myth`	No	Include associated myth propositions
`include_embedding`	No	Include raw 1024-float vector array

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Nov 13, 2026

TDQS

B3.2/5.0

Behavior3/5

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

With no annotations supplied, the description carries the burden, and 'List' does at least signal a non-mutating read. However it says nothing about result ordering, the fact that results are paginated with a default of 50, or that enabling embeddings produces very large 1024-float payloads — the kind of behavioral context an agent needs before calling.

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; every word is doing work. It is arguably under-specified rather than verbose, but there is no structural or clarity defect.

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

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a nine-parameter tool with no annotations and no output schema, the fully documented schema compensates for most gaps and an agent can invoke it correctly. The description still omits behavioral context around pagination defaults and the cost of requesting raw embedding vectors, leaving it only minimally complete.

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% and each of the nine parameters carries a clear description, so the schema does the heavy lifting. The description only echoes two of them ('thematic tags' for theme, 'vector embedding status' for embedded) without adding syntax, substring semantics, or combining behavior, so the baseline of 3 is appropriate.

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 ('List and filter deities') plus the two dimensions being filtered ('thematic tags', 'vector embedding status'), so an agent knows immediately it is a read/list tool over the deity collection. It does not distinguish itself from siblings like list_myths, list_pantheons, or get_god, which is the only thing keeping it from a 5.

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 beyond the implied act of listing, no mention of when to prefer get_god for a single record, and no exclusions or prerequisites. The agent must infer the selection context entirely from the tool name and siblings.

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