Skip to main content
Glama

AurelianFlo

by com.aurelianflo

Saved Report Retrieval Status

report_saved_retrieve
Read-only

Free read-only past report retrieval status utility for agents asking about previously generated reports. AurelianFlo returns report artifacts inline as artifact.contentBase64 and does not persist hosted report files server-side.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
file_nameNoOptional file name from a prior artifact response.
report_idNoOptional client-side report or case identifier to echo in the retrieval status response.
settlement_txNoOptional x402 settlement transaction hash associated with a prior paid report call.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataNoPrimary structured result payload for the tool.
errorNoMachine-readable error code or message when the tool fails.
outputNoNested renderer output when a workflow bundles an artifact render.
reportNoReport-shaped payload when available; null for status-only retrieval responses.
sourceNoSource label, route, dataset, or execution metadata for the result.
messageNoHuman-readable error or status message.
successNoWhether the tool completed successfully.
artifactNoInline generated file artifact. The service does not persist a hosted download URL.
artifactsNoArtifact rendering hints keyed by format.
artifact_summaryNoDelivery and rendering metadata for an inline generated artifact.

TDQS

A4/5.0
Behavior4/5

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

Annotations already set readOnlyHint=true. The description adds valuable behavioral context: 'returns report artifacts inline as artifact.contentBase64' and 'does not persist hosted report files server-side', clarifying the output format and server-side behavior.

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 two efficient sentences with no redundant information. The first sentence states the purpose, the second adds behavioral details, making it front-loaded and concise.

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

Completeness4/5

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

Given the presence of an output schema and annotations, the description provides sufficient context about the tool's behavior and return format. It covers the key aspects for an agent to use the tool correctly.

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% with all three parameters described. The description does not add further semantic meaning beyond what the schema provides, resulting in a baseline score.

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 clearly states the tool retrieves status of past saved reports, using specific verbs 'retrieve' and 'returns'. It distinguishes from sibling report tools by focusing on retrieval and mentioning that reports are not persisted server-side.

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

Usage Guidelines3/5

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

The description says 'for agents asking about previously generated reports', which implies the usage context. However, it does not explicitly state when not to use this tool or mention alternatives like queue_saved_list for listing saved reports.

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

All AurelianFlo toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.1/5.0
Disambiguation4/5

Tools are generally distinct, with clear differentiators like single vs batch vs report output. The queue_saved_list and report_saved_retrieve could be confused but descriptions clarify their separate domains.

Naming Consistency4/5

Prefixes like compliance_, wallet_ofac_, report_, queue_ provide consistency within subdomains, though verb order varies (e.g., report_docx_generate vs queue_saved_list).

Tool Count4/5

11 tools are appropriate for a compliance server covering screening, reporting, and optimization. Slightly on the higher side but each tool serves a unique purpose.

Completeness4/5

Covers core workflows: screening, batch, reporting, EDD memos, exposure forecasting, queue optimization, and status checks. Minor gaps like no wallet set management, but overall comprehensive.

Resources