Syncretica MCP Server

get_cluster_snapshot

Retrieve details from a frozen cluster snapshot, including member groups, deities or myths, and generated scholarly reports.

Instructions

Retrieve details of a frozen cluster snapshot including member groups and generated reports.

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_snapshot"
  }
}

Input Schema

Name	Required	Description
`id`	Yes	Cluster Snapshot ID
`include_groups`	No	Include discovered archetype cluster groups
`include_members`	No	Include deities or myths belonging to each group
`include_reports`	No	Include generated scholarly reports

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Nov 13, 2026

TDQS

B3.3/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 burden. It does convey useful behavior by calling the snapshot "frozen" (immutable, time-fixed) and by stating what is bundled into the response, but it says nothing about permissions, error behavior for a missing/stale ID, or response size when all includes default to true.

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?

A single front-loaded sentence with no filler; the resource and the notable payload contents appear immediately.

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 read with fully described parameters and no output schema, the description is adequate but thin: it hints at the return payload without describing its shape, and leaves the caller to guess whether all includes default to true and how expensive that is.

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 every parameter is already documented, including the three include_* toggles and their defaults. The description echoes include_groups and include_reports but omits include_members, so it adds almost nothing the schema doesn't already say.

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: "Retrieve details of a frozen cluster snapshot," and enumerates part of the payload (member groups, generated reports). This distinguishes it from list_cluster_snapshots and the create/delete siblings, though it never names an alternative explicitly.

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 (e.g., that the snapshot must already exist), and no pointer to list_cluster_snapshots for discovering IDs or to get_cluster_group/get_cluster_report for narrower reads. The agent must infer usage from the name alone.

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