Syncretica MCP Server

get_cluster_group

Retrieve an archetype cluster group by ID and optionally include its member deities or myths for cross-cultural mythological analysis.

Instructions

Retrieve details of a specific archetype cluster group with all member deities or myths.

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

Input Schema

Name	Required	Description	Default
`id`	Yes	Cluster Group ID
`include_members`	No	Include member deities or myths

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?

No annotations are supplied, so the description carries the full behavioral burden. It does convey that this is a read (retrieve) and that the response includes member deities or myths, but it says nothing about behavior for a nonexistent ID, permission requirements, or how the payload scales for large groups.

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 the verb, resource, and payload scope; no filler or redundancy. It could be marginally sharper by naming the ID-keyed lookup explicitly, but nothing needs cutting.

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 simple two-parameter read with full schema coverage and no output schema, the description is just enough: it states the resource and roughly what comes back. It leaves the shape of 'details' and the effect of include_members=false unspoken, which keeps it at minimum-viable rather than 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 description coverage is 100%, so baseline is 3; both 'id' and 'include_members' are documented in the schema itself. The phrase 'with all member deities or myths' loosely reinforces what include_members controls, but adds no format or edge-case 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 names a specific verb ('Retrieve') and resource ('details of a specific archetype cluster group'), plus the payload ('all member deities or myths'). That distinguishes it from get_god/get_myth (which fetch a single entity) and from the list_* siblings, though it does not explicitly contrast itself with get_cluster_report or get_cluster_snapshot.

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 prerequisites, and no named alternative or exclusion. The agent must infer from the verb alone that this is the tool for looking up one existing cluster group by ID rather than listing or computing clusters.

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