Syncretica MCP Server

create_cluster_snapshot

Compute connected-components clustering for God or Myth entities and freeze the result into an immutable database snapshot for reproducible analysis.

Instructions

Compute connected-components clustering and freeze it immediately into an immutable database snapshot.

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": {
      "target_type": "<target_type>",
      "level": "<level>",
      "title": "<title>"
    },
    "name": "create_cluster_snapshot"
  }
}

Input Schema

Name	Required	Description
`level`	Yes	Strictness level (1 to 15)
`title`	Yes	Descriptive title for the frozen snapshot (e.g. 'Full Catalog Zero-Singleton Snapshot (15)')
`target_type`	Yes	Target entity class: God or Myth
`full_coverage`	No	Force 100% catalog coverage (zero singletons)

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. It does disclose one genuinely useful trait: the snapshot is immutable and created in a single immediate 'compute + freeze' step. It omits everything else an agent needs before a write: whether the computation is long-running or asynchronous (a get_job_status sibling suggests jobs exist), whether it can be overwritten or must be deleted, uniqueness constraints, and cost.

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, putting the computation first and the freezing second. It is well-formed but so terse that structure cannot compensate for the absent guidance.

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 write tool with no annotations and no output schema, the definition covers the essential mechanics (compute then freeze immutably) but leaves the mutation risk profile, latency/async behavior, and the snapshot lifecycle unexplained. Adequate to start the call, insufficient to call it confidently.

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% and all four parameters (level, title, target_type, full_coverage) are documented in the schema with ranges, enum values, and an example. The description adds no parameter meaning beyond the schema, which is the baseline-3 case.

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 compound verb and resource: computes connected-components clustering and freezes it into an immutable database snapshot. The implicit deictic 'it' makes clear the snapshot captures the clustering result. It stops short of naming compute_clusters or create_cluster_report, so the agent must infer the relationship from the name.

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?

No when-to-use, when-not, or prerequisite guidance is given. The description never says how this differs from the sibling compute_clusters (which presumably computes without freezing) or create_cluster_report, so an agent has no textual basis for choosing among them.

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