Syncretica MCP Server

get_cluster_report

Retrieve full scholarly reports by cluster ID, including progress, markdown monograph, and optional summaries and sub-reports for synthesis review.

Instructions

Retrieve complete scholarly report content, progress percentage, markdown monograph, and intermediate summaries.

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

Input Schema

Name	Required	Description
`id`	Yes	Cluster Report ID
`include_summaries`	No	Include Phase 1 individual cluster summaries
`include_sub_reports`	No	Include Phase 2 intermediate batch syntheses

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, and it does disclose the return payload composition (content, progress percentage, monograph, summaries). However, it says nothing about permissions, behavior when the report is still in progress (the progress-percentage field implies partial states), response size, or failure modes.

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 that lists exactly what comes back and pads nothing. No restatement of the name or redundant framing.

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?

With no output schema, the description does the necessary work of naming the returned fields, and all three parameters are covered by the schema. What is missing is guidance on partial/in-progress reports and on choosing this tool over the closely related summary/sub-report siblings.

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 id, include_summaries, and include_sub_reports are already documented in the schema, making 3 the baseline. The description's mention of 'intermediate summaries' loosely echoes the two include flags but adds no format, default, or trade-off guidance 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?

States a specific verb (Retrieve) and resource (scholarly cluster report), and enumerates the payload: report content, progress percentage, markdown monograph, and intermediate summaries. It does not differentiate itself from siblings such as get_report_sub_report or get_report_summary, which appear to return overlapping slices of the same report.

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 at all: no mention of when to prefer this full report over get_report_summary or get_report_sub_report, no prerequisite that the report exist or be complete, and no exclusion conditions. The agent must infer routing purely from the sibling names.

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