Skip to main content
Glama

get_cluster_report

Retrieve a complete scholarly physics cluster report by ID, including progress percentage, markdown monograph, and optional intermediate summaries and sub-reports.

Instructions

Retrieve complete scholarly physics 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

NameRequiredDescriptionDefault
idYesCluster Report ID
include_summariesNoInclude Phase 1 individual cluster summaries
include_sub_reportsNoInclude Phase 2 intermediate batch syntheses

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden; it does disclose the returned artifacts (content, progress percentage, markdown monograph, intermediate summaries), which is useful signal. However, it says nothing about whether this is a read-only operation, the size/cost of the payload, or that the boolean flags can shrink the response.

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?

One front-loaded sentence with no filler; the enumerated payload comes first and nothing is wasted. It is slightly list-like but appropriate for a retrieval tool.

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 three-parameter read tool with no output schema, the description reasonably covers what comes back, so return-value explanation is not required. What is missing is guidance on payload control via the include_* flags and how this differs from the sibling summary/sub-report getters.

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 the schema already documents id, include_summaries, and include_sub_reports. The description's mention of 'intermediate summaries' loosely corresponds to those flags but adds no semantics beyond what the schema states, so the baseline 3 applies.

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 ('complete scholarly physics report content') and enumerates the payload (progress percentage, markdown monograph, intermediate summaries). It distinguishes itself from list_cluster_reports by implying full content retrieval, though it never names the partial-retrieval siblings like get_report_summary or get_report_sub_report 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?

Usage is only implied: the word 'complete' suggests using this when the full report is needed rather than a summary or sub-report, but the description never states when to prefer those alternatives or what preconditions exist. An agent must infer the choice from sibling names alone.

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