Skip to main content
Glama

AurelianFlo

by com.aurelianflo

Saved Queue Status

queue_saved_list
Read-only

Free read-only saved queue status utility for agents asking whether AurelianFlo can list prior compliance_queue_optimize results. AurelianFlo does not persist saved queues server-side; rerun compliance_queue_optimize with the original review_items to recreate a queue.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum saved queue records to list if server-side queue persistence becomes configured.
case_referenceNoOptional client-side case reference to echo in the status response.

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/5.0
Behavior5/5

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

Description adds critical behavioral context beyond annotations: reveals that saved queues are not persisted server-side by AurelianFlo, meaning the tool may effectively return empty/no results. This is a key transparency disclosure not evident from readOnlyHint alone.

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 sentences, front-loaded with purpose, followed by essential caveat. No redundant information. Highly efficient.

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?

Given the output schema exists (not shown, but noted in context), the description adequately covers purpose, usage context, and behavioral caveats. With only 2 parameters fully described in schema, no further details needed.

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 baseline is 3. The description adds no additional semantic value beyond what the schema already provides for 'limit' and 'case_reference'.

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?

Clear verb+resource: 'list saved queue status'. The description specifies it's for agents asking about listing prior compliance_queue_optimize results, distinguishing it from sibling tools like compliance_queue_optimize that create queues. However, it doesn't explicitly differentiate from list-like siblings (e.g., report_saved_retrieve).

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

Usage Guidelines5/5

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

Explicitly states when to use (agents asking if AurelianFlo can list prior results) and provides a clear alternative: rerun compliance_queue_optimize with original review_items. This guides the agent away from using this ineffectively.

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