Skip to main content
Glama

get_cluster_report

Retrieve a complete scholarly biological cluster report by ID, including progress percentage, markdown monograph, and optional intermediate summaries or batch syntheses.

Instructions

Retrieve complete scholarly biological 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.2/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 disclosure burden; "Retrieve" does establish a read-only operation and it usefully names what comes back (content, progress percentage, monograph, summaries). It says nothing about failure behavior for an unknown ID, whether a partially generated report returns partial content, or whether progress percentage is 0-100 — gaps for a fetch-by-ID tool.

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. The trailing noun list is slightly dense but each item conveys real payload information, so nothing is wasted.

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?

Adequate for a simple three-parameter read tool with no output schema: it conveys what the response contains. It is thin on the ID lifecycle (how to obtain a valid report ID) and on behavior when the report is still being generated, which matters given the progress-percentage output.

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 the schema already defines id, include_summaries, and include_sub_reports with Phase 1/Phase 2 descriptions. The description's mention of "intermediate summaries" loosely echoes include_sub_reports but adds no format, default, or interaction detail beyond the schema; 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?

Uses a specific verb ("Retrieve") plus a scoped resource ("complete scholarly biological report content") and enumerates the returned artifacts: progress percentage, markdown monograph, intermediate summaries. The word "complete" hints at the distinction from summary-level siblings, but it never names or contrasts with get_report_summary/get_report_sub_report, so an agent must infer the boundary.

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 or when-not-to-use guidance is given. It doesn't say to prefer list_cluster_reports to find an ID, or get_report_summary for lighter fetches; the only cue is the adjective "complete," which is left implicit.

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