AstraEye Labs

List research reports

list_research_reports

Read-onlyIdempotent

Lists the member's finished reports, newest first: id, project id, date, available languages and the url of the report's page in AstraEye. The first report is the most recently finished research run. Use get_research_report to read one.

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

Input Schema

Name	Required	Description
`limit`	No	Page size, 1 to 50. Default 20.
`cursor`	No	nextCursor from a previous page.
`researchId`	No	Only reports from this project id (from list_research_projects).

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 28, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior, so the description need not repeat safety. It adds useful context: results are the member's finished reports, newest first, and the first report is the most recently finished run.

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?

Two compact sentences, front-loaded with the resource and ordering, followed by the key routing instruction. No wasted text.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only list tool with no output schema, the description explains what is returned (id, project id, date, languages, URL) and the ordering. Annotations and schema cover safety and pagination parameters, leaving no significant gap.

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 limit, cursor, and researchId are already documented. The description does not add syntax or usage meaning beyond what the schema provides, which is appropriate for a baseline 3.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource (lists finished reports), specifies ordering (newest first), and enumerates returned fields. It also distinguishes itself from get_research_report by saying to use that tool to read one.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Clearly indicates when to use this list tool versus get_research_report for reading a single report. It does not explicitly mention when not to use it or explain filtering by researchId, though the schema covers that parameter.

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

All AstraEye Labs tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?