Skip to main content
Glama

list_cluster_reports

Retrieve and filter paginated multi-phase comparative particle physics and quantum state manifold synthesis reports by status, target type, detail level, or cluster snapshot.

Instructions

List generated multi-phase comparative particle physics and quantum state 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: SubatomicParticle or QuantumState
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?

No annotations are supplied, so the description carries the full behavioral burden, yet it says nothing about pagination defaults (limit 20, max 100), ordering, whether filters are combinable, or what a returned report entry contains. 'List' implies a read-only operation, but that is inference rather than disclosure, which is a real gap for a tool with six optional filters and no output schema.

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 or repetition. It is compact, though the stacked modifiers make it read as denser than it needs to be.

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?

With no annotations and no output schema, the description should explain the shape of a report entry and how the six filters interact; instead it only names the resource. For a filtered-list endpoint over a non-trivial domain object, this leaves an agent guessing about results and filter semantics.

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% and every parameter carries its own description including both enum sets, so the schema already does the work and the baseline of 3 applies. The description adds nothing beyond the schema except the phrase 'multi-phase', which loosely gestures at is_detailed but does not clarify it.

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 gives a specific verb (List) and a specific resource (generated multi-phase comparative particle physics and quantum state manifold synthesis reports), which is enough to distinguish it from singular siblings like get_cluster_report. It stops short of explicitly naming a sibling or stating the collection scope, and the dense jargon ('quantum state manifold synthesis') slightly obscures what a report actually is.

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: nothing says to call this instead of get_cluster_report for a single report, nor when to use the status/target_type filters versus a plain listing. The agent must infer the browsing use case entirely from the name.

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