Syncretica MCP Server

compute_clusters

Compute live connected-component clusters of Gods or Myths across pantheons to group related entities without altering the database. Set strictness and full coverage to control cluster breadth.

Instructions

Compute live connected-components vector clusters for Gods or Myths across world pantheons without modifying the database.

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

Input Schema

Name	Required	Description	Default
`force`	No	Bypass Rails memory cache and recalculate adjacency graph
`level`	No	Strictness level from 1 (coarse/broad) to 15 (strict/fine-grained)
`target_type`	No	Target entity class to cluster: God or Myth	God
`full_coverage`	No	Forces 100% catalog assignment / zero singletons via adaptive distance matching

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Nov 13, 2026

TDQS

A3.5/5.0

Behavior3/5

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

With no annotations, the description carries the disclosure burden; it usefully states the operation is non-mutating. It says nothing about whether results are persisted, how expensive the computation is, or that the 'force' flag bypasses the cache and triggers recalculation (that detail lives only in the schema).

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 zero filler; the non-mutating constraint is stated compactly at the end. Nothing is redundant or padded.

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 computation tool with four optional parameters, no annotations, and no output schema, the description covers what is computed and that it is read-only but omits what the caller gets back (cluster list? assignments?) and whether the run is costly or persisted. An agent could invoke it correctly but not predict its result shape or cost.

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 all four parameters (force, level, target_type, full_coverage) are already documented, including the enum and bounds. The description adds no parameter-level meaning such as recommended level values or when to set force.

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?

Uses a specific verb ('Compute') with a concrete resource ('live connected-components vector clusters') and scopes it to Gods or Myths across pantheons. It is clearly distinguishable from CRUD siblings and from the snapshot/report tools, though it does not name them explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase 'live ... without modifying the database' hints that this computes rather than reads a stored snapshot, which implicitly separates it from get_cluster_snapshot/get_cluster_group. However, there is no explicit when-to-use or when-not-to-use guidance and no named alternative.

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