Skip to main content
Glama
Sign In

Azquo

by ai.azquo
OverviewDiscussionsAdmin

List databases

list_databases
Read-only

List all Azquo databases available to the current user. The shared azquo business overlays two DBs onto every session: azquo_skills (read-only usage skills, always readable) and azquo_suggestions (open-write DB where any agent can propose improvements). Overlaid entries carry overlay: true plus readOnly and openWrite flags; local DBs never carry them. Every database in the azquo_library training library is also overlaid, read-only, carrying library: true — so worked examples can be opened and read in place with describe_database / query_aql, without copying them first. A library database is not listed in the user's business on admin.azquo.ai: when they work with one, offer early to copy it with copy_from_library (ask first) so it is theirs to see and change.

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?

Beyond the readOnlyHint and openWorldHint annotations, the description discloses important behavior: business sessions overlay azquo_skills and azquo_suggestions, overlaid entries carry overlay/readOnly/openWrite flags, library databases are read-only and carry library:true, and they are not listed in the user's business on admin.azquo.ai. This is rich context an agent needs to interpret results correctly.

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 the core action and then explains overlay and library semantics. It is somewhat long, but the additional sentences carry useful domain-specific information rather than filler.

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?

With no output schema and one optional parameter, the description provides enough detail about return values by explaining the overlay, readOnly, openWrite, and library flags. It also explains the practical implication for library databases, which is important for correct follow-up behavior.

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%, and the only parameter, business, is already documented in the schema with its semantics. The description does not add meaning beyond the schema, so the baseline score of 3 is appropriate.

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 Azquo databases available to the current user. It also explains overlay and local database distinctions, and ties library databases to related tools like describe_database, query_aql, and copy_from_library, so an agent can understand the tool's role among siblings.

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?

It gives clear post-listing guidance: library examples can be opened directly, and when a user works with a library database the agent should offer to copy it with copy_from_library after asking first. It does not explicitly state when not to use this tool or contrast it with every listing alternative, but the operational context is clear.

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