Skip to main content
Glama

List connections

list_connections
Read-only

List the database connections you can use in this SaturnSQL company, with each one's id, name, engine, database and aiAccess, which says what you may do on it. Call this first: get_schema, execute_query and export_query_results need a connectionId from this list. On an approved_queries connection use list_queries and run_saved_query instead. Connections the team closed to AI are not listed. Read-only, takes no parameters.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
connectionsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / properties / connections / items / properties / aiAccess
      Added value: +{
      +  "description": "What you may do on this connection, set by the team: approved_queries (only run_saved_query on queries shared with the team; no schema, no SQL of your own), read_only (schema plus one SELECT, WITH or EXPLAIN per call) or same_as_people (execute_write_query may also change data where the connection allows people to).",
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
  2. Changed1 schema field changed
    • changedOutput schema / properties / connections / items / additionalProperties
      Previous value: -trueNew value: +{}
  3. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already declare readOnlyHint and openWorldHint, but the description adds real behavioral context: connections closed to AI are omitted from results, and the aiAccess field encodes what the caller is permitted to do. It also states it is read-only and takes no parameters, removing any doubt about side effects.

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?

Five short sentences, all front-loaded: purpose and returned fields first, then the mandatory call-first ordering, then the alternative path, then the visibility caveat. Nothing is redundant or padding.

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?

An output schema exists, yet the description still summarizes the returned fields and the meaning of aiAccess, and it covers the prerequisite relationship to dependent tools. For a zero-parameter discovery tool this is everything an agent needs to call it correctly.

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

Parameters4/5

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

Zero parameters, so the baseline is 4; the description confirms this explicitly with "takes no parameters," sparing the agent a guess about whether filters exist. Beyond that confirmation there is no further parameter meaning to add.

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?

Specific verb+resource ("List the database connections you can use in this SaturnSQL company") plus the returned fields (id, name, engine, database, aiAccess). It also distinguishes itself from list_queries by routing approved_queries connections elsewhere, so an agent can tell the two apart without opening a schema.

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 a sequencing requirement ("Call this first") and names the three tools that depend on its connectionId (get_schema, execute_query, export_query_results). It also names the alternative path (list_queries and run_saved_query) and the condition that selects it (approved_queries connections).

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources