Azquo

List external connections

list_external_connections

Read-only

List the external database connections configured for this business. Use the connection NAME with import_from_query.

Credentials are never returned - the server holds them. Connections are set up by an administrator in azquo-admin; if the source you need is not listed, ask for it to be added rather than looking for another route to the data.

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

Input Schema

Name	Required	Description	Default
`business`	No	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.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 21, 2026

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

First observedOct 19, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Beyond the standard read-only annotation, the description adds two vital behavioral constraints: 'Credentials are never returned - the server holds them' (a security guarantee) and 'Connections are set up by an administrator in azquo-admin' (a constraint on data management/access). This significantly enhances operational awareness.

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 tool definition is highly efficient. It presents the core function, followed by immediate operational instructions (usage), and then critical constraints (security/admin setup), making maximum use of minimal text.

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?

The description is complete for a read-only listing tool. It details what the tool does, how its output must be used, and necessary security/administrative constraints, leaving no critical operational gaps for the agent.

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?

Since the schema description coverage is 100%, the schema already fully documents the `business` parameter. The description provides contextual flavor ('for this business') but does not add semantic meaning that compensates for an incomplete schema.

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 immediately states its purpose: to 'List the external database connections configured for this business.' Furthermore, it explicitly instructs the agent to 'Use the connection NAME with import_from_query,' clearly distinguishing its output role relative to sibling tools.

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?

The description provides explicit instructions for workflow. It directs the user on the subsequent action required after listing the connection ('Use the connection NAME with import_from_query') and provides a critical contingency plan for missing connections ('ask for it to be added rather than looking for another route').

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

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

Resources

Need Help?