anydb-mcp

List connection profiles

db_list

Read-onlyIdempotent

Lists connection profiles from the anydb config file—name, driver, default, and read-only status—for selecting a profile in other tools. Use first when the profile name is unknown.

Instructions

List the connection profiles from the anydb config file (~/.anydb/db.json): name, description, driver, which one is the default, and whether it is read-only. Call this first whenever you do not already know a profile name, then pass the name to the other tools as "profile". The result never contains a connection string, a host, a username or a password -- not masked, absent -- because this text goes into your context window and a config file is writable by anyone who can write files. If there is no config file, use "uri" with the other tools instead.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description
`ok`	Yes	False when the call failed; read "error" then.
`message`	No	Present when there is nothing to list.
`profiles`	Yes	The profiles, default first. Never a URI, a host or a credential.
`configSource`	Yes	Path of the config file read, or null.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv3.0.4Oct 2, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations already establish the safe read-only, idempotent, closed-world profile, but the description adds material context beyond them: secrets are absent rather than masked, and it explains why (output lands in the context window and the config file is writable by anyone who can write files). This negative-space disclosure is the kind of trait an agent cannot infer from the schema or annotations.

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?

Front-loaded with the resource and its returned fields, followed by usage ordering and the safety note. Three sentences all carry information, though the '-- not masked, absent --' aside is slightly rhetorical for the payload it delivers.

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, so field-level return documentation is unnecessary and the description correctly does not duplicate it. What remains — when to call it, how its output is consumed by siblings, the fallback when no config exists, and the secret-exclusion guarantee — is complete for a parameterless list tool.

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 and there is no schema semantics to add to. The description does clarify cross-tool semantics — that the profile names returned here are the values passed as 'profile' to sibling tools — which is useful bridging text but not parameter documentation.

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?

States a specific verb and resource (list connection profiles from the anydb config file) and enumerates exactly what each entry contains: name, description, driver, default flag, read-only flag. It is unmistakably distinct from the sibling query/schema/explain/health 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?

Explicitly prescribes the calling order: 'Call this first whenever you do not already know a profile name, then pass the name to the other tools as "profile".' It also names the alternative path when the config file is absent ('use "uri" with the other tools instead'), covering both the when and the when-not.

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

Deploy Server