Skip to main content
Glama
Sign In

Azquo

by ai.azquo
OverviewDiscussionsAdmin

List reports

list_reports
Read-only

List the online reports (Excel reports users run in Azquo) the current user can see, across every database in the business. Read-only, no parameters. Use it to find a report's id or name before get_report_data, read_workbook or delete_report. For the reports, setup sheets and import templates of one database use list_database_sheets instead.

Who sees what: an administrator sees every report in the business; a developer sees the reports on databases they own; a user whose role has the Reports menu item sees every report in the business too (marked readOnly: true when the role may only see Reports - they run, but do not save); other users see the reports on their menus.

Returns an array of reports: id, reportName (with " uploaded by " appended), database (the one it runs against; empty for reports usable with any database, "No database" when unlinked), filename, category, explanation, dateCreated and author. A report linked to several databases appears once for each. To SHOW the person a report, call open_in_browser with its id and database: its one-use link opens the report already signed in as this same user, with their choices. Do not give the person any other address for a report - a plain one makes them sign in again, and they may land as another login of theirs, whose saved choices differ. Then the reports of the shared azquo_library databases (overlaid read-only, as list_databases shows them), marked library: true and readOnly: true - run them with get_report_data on the database shown, or show them with open_in_browser, which opens them read-only (no Save, executes do not run). A library database whose name this business also holds is left out: the business's own copy wins. With none visible, a single placeholder with id 0 and reportName "No reports found" is returned. Not paginated.

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

Input Schema

NameRequiredDescriptionDefault
businessNoOptional. The business this call is for, by name, e.g. "azquo" - it then runs there whatever business the session is in. Worth giving on writes when you work in more than one business: a new MCP session starts in the login's own business. list_businesses shows the names.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / business
      Added value: +{
+  "description": "Optional. The business this call is for, by name, e.g. \"azquo\" - it then runs there whatever business the session is in. Worth giving on writes when you work in more than one business: a new MCP session starts in the login's own business. list_businesses shows the names.",
+  "type": "string"
+}
  2. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Although annotations already declare readOnlyHint=true, the description adds substantial behavioral context: role-based visibility, readOnly: true and library: true markers, duplicate reports across databases, placeholder behavior when none are visible, and that results are not paginated. It also warns against giving users plain report addresses because of the one-use signed-in link behavior.

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?

The description is front-loaded with purpose and usage, then organized into visibility and return-value details. It is lengthy, but most detail is relevant for this complex listing tool; the inaccurate 'no parameters' phrase is a small structural flaw.

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?

With no output schema, the description usefully explains the returned array fields, role-dependent visibility, library overlay behavior, empty-result placeholder, and non-pagination. Its main gap is failing to mention the optional 'business' parameter and instead claiming there are no parameters.

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

Parameters2/5

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

Schema coverage is 100%, and the sole optional 'business' parameter is fully documented in the schema. However, the description says 'no parameters' and never mentions 'business', which is misleading for a cross-business tool even though the schema compensates.

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 states a specific verb and resource: list online reports the current user can see across every database. It explicitly distinguishes itself from list_database_sheets and positions itself before get_report_data, read_workbook, and delete_report.

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?

It gives explicit when-to-use guidance, including using the result to find a report id or name before calling get_report_data, read_workbook, or delete_report. It also names the alternative for reports/setup sheets/import templates of one database and explains how to show a report via open_in_browser.

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

All Azquo toolsInspect
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