Datalastic Vessel Tracking & Maritime Intelligence

List async reports

report_list

Read-only

List the caller's recent async report jobs with their statuses — result_url on the ones that are DONE, and message explaining the cause on any that are FAILED. Use this to recover a report_id, see which reports have finished, or find out why one failed — for example if a report was submitted earlier and its id was lost. Listing is free and never re-runs a report.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description	Default
`reports`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 3, 2026

addedOutput schema / properties / reports / items / properties / message
```
Added value: +{
+  "type": [
+    "null",
+    "string"
+  ]
+}
```

changedOutput schema / properties / reports / items / required

Previous value: -[
-  "report_id",
-  "report_type",
-  "status",
-  "result_url",
-  "created_at",
-  "updated_at"
-]New value: +[
+  "report_id",
+  "report_type",
+  "status",
+  "message",
+  "result_url",
+  "created_at",
+  "updated_at"
+]

First observedJul 4, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description adds value by stating 'Listing is free and never re-runs a report,' clarifying side-effect behavior. It also discloses response contents (result_url on DONE, message on FAILED), which is useful beyond the bare annotations.

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?

The description is three sentences with no filler: purpose and response shape, use cases, and a side-effect guarantee. The main verb is front-loaded and every sentence earns its place.

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 zero-parameter tool with a provided output schema and safety annotations, the description covers purpose, usage scenarios, response fields, and the no-re-run guarantee. Nothing needed to invoke it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there are no parameter semantics to document. Per the baseline for a no-parameter tool, this is adequate.

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?

The description opens with a specific verb and object: 'List the caller's recent async report jobs with their statuses.' It further details what is returned for DONE vs FAILED reports, making the tool's purpose unmistakable and distinguishing it from siblings like report_status and report_request by framing it as an overview/recovery tool.

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?

The description explicitly states when to use it: 'Use this to recover a report_id, see which reports have finished, or find out why one failed,' with a concrete example. However, it does not name alternative tools or provide when-not-to-use guidance, so it stops short of full decision-tree routing.

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

All Datalastic Vessel Tracking & Maritime Intelligence 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.