Syncretica MCP Server

create_cluster_report

Starts a two-phase map-reduce synthesis report on a frozen cluster snapshot, turning a scholarly prompt into a structured cross-cultural analysis.

Instructions

Initiate a 2-Phase Map-Reduce synthesis report on a frozen cluster 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": {
      "cluster_snapshot_id": "<cluster_snapshot_id>",
      "prompt": "<prompt>"
    },
    "name": "create_cluster_report"
  }
}

Input Schema

Name	Required	Description	Default
`prompt`	Yes	Scholarly investigation prompt (e.g. 'Analyze cross-cultural archetypes of sacred metallurgy and volcanic divine power.')
`cluster_snapshot_id`	Yes	Cluster Snapshot ID

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?

With no annotations, the description carries the full burden, and "Initiate" strongly implies an asynchronous, long-running operation, yet nothing says whether a job ID is returned, whether the caller must poll get_job_status, or how long or how costly the 2-phase map-reduce run is. The phrase "frozen cluster snapshot" hints at a state prerequisite but never states it as a constraint or what happens if the snapshot is not frozen.

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, which is appropriately sized for a two-parameter tool. The brevity is efficient but edges toward under-specification rather than maximal clarity.

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

Completeness2/5

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

For an async initiation tool with no annotations and no output schema, the description should explain what is returned and how results are later retrieved (presumably via get_cluster_report or get_job_status). None of that is present, leaving the post-call workflow opaque.

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 both parameters are already documented in the schema, including an example prompt. The description adds only the notion that cluster_snapshot_id refers to a frozen snapshot, which is marginal value beyond the schema baseline.

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 pairs a specific verb ("Initiate") with a specific resource ("synthesis report on a frozen cluster snapshot"), which cleanly separates it from the read-side siblings like get_cluster_report and list_cluster_reports. It does not explicitly name an alternative, but the create-vs-get distinction is inferable from the verb alone.

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 guidance on when to use this instead of generate_deep_synthesis or the other synthesis-adjacent tools, and no stated prerequisites such as whether the snapshot must already exist or be frozen before calling. The agent is left to infer the workflow entirely.

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