Skip to main content
Glama

list_cluster_reports

Retrieve paginated multi-phase comparative biology and ecological synthesis reports, with filters for status, target type, detail level, and cluster snapshot.

Instructions

List generated multi-phase comparative biology and ecological manifold synthesis reports.

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

Input Schema

NameRequiredDescriptionDefault
limitNoPagination limit
offsetNoPagination offset
statusNoFilter by report generation status
is_detailedNoFilter by whether report is a 3-phase detailed deep synthesis
target_typeNoFilter by target entity type: Species or Organism
cluster_snapshot_idNoFilter reports for a specific cluster snapshot ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

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 of behavioral disclosure and falls short. It does not state whether the operation is read-only, what the return shape is, whether results are paginated or ordered, or whether permissions are required. The term 'generated' is also slightly ambiguous against the status filter that includes queued/running states.

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?

The description is a single front-loaded sentence with no wasted words. Its brevity is appropriate structurally, though it leaves important behavior unstated.

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 a six-parameter list tool with filtering enums and no annotations or output schema, the description is too thin. It does not explain the report lifecycle, how the filters interact, or what agents should expect to receive, leaving the schema to carry nearly all context.

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 six parameters, including the status enum, target_type enum, and pagination controls, are fully documented in the schema. The description adds no extra meaning 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 uses a specific verb ('List') and a specific resource ('reports') with qualifiers ('generated multi-phase comparative biology and ecological manifold synthesis'). This is clearly distinguishable from get_cluster_report, but it does not clarify how it differs from list_report_summaries or list_report_sub_reports.

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 tool versus alternatives, nor any mention of prerequisites, pagination context, or which sibling to select for summaries versus full reports. Only the word 'List' implies read-only enumeration.

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