Skip to main content
Glama
Sign In
db-conn-mcp

db-conn-mcp

by Idle-Sync
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

list_databases

Lists configured databases with their allowed mode, yolo flag, fallback ports, and current active port. Use it to inspect database connection options and fallback status before querying.

Instructions

List configured databases with their allowed mode and yolo flag (no DSN).

Entries with fallback_ports configured also show them, plus active_port when a fallback port is currently in use.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose useful behavior: DSNs are deliberately omitted from output, and fallback_ports/active_port fields appear conditionally. It does not state permission requirements or whether the list is cached/live, but it covers the security-relevant omission an agent would otherwise worry about.

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 short sentences, front-loaded with the core action and the most decision-relevant caveat ('no DSN'), with zero filler wording.

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?

For a simple read-only, zero-parameter tool with an output schema present, the description supplies everything needed to decide and call it. The conditional-field sentence slightly overlaps the output schema, but nothing essential is missing.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; the schema carries no ambiguity. Baseline 4 applies for a parameterless tool.

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 gives a specific verb and resource ('List configured databases') and immediately scopes the return payload (allowed mode, yolo flag, no DSN), which distinguishes it from siblings like list_tables or get_database_schema that operate on a single database's contents.

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

Usage Guidelines3/5

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

Usage is only implied: a zero-argument enumeration tool with no prerequisites. There is no explicit statement of when to call this versus inspecting a schema directly, and no exclusions or follow-up guidance.

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

This server cannot be deployed

Other Tools