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

db-access-mcp

by Rheopyrin
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

connection_find

Find database connections by host, port, database, type, read-only status, or metadata key-value pairs. Filters combine with AND, ignoring credentials.

Instructions

Find configured database connections by parameters: host, port, database, type, read_only and/or metadata key-value pairs. All provided filters are combined with AND. Username/password filters are ignored. Returns the same sanitized shape as connection_list.

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": "connection_find"
  }
}

Input Schema

NameRequiredDescriptionDefault
hostNoExact database host to match
portNoDatabase port to match
typeNoDialect: postgres | mysql | redshift
userNoIgnored: connections are never filtered by credentials
databaseNoDatabase name to match
metadataNoMetadata key-value pairs; every pair must match (AND)
passwordNoIgnored: connections are never filtered by credentials
usernameNoIgnored: connections are never filtered by credentials
read_onlyNoMatch connections with this read_only setting

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Discloses that username/password filters are ignored and that metadata filters use AND logic. References return shape to connection_list. No annotations provided, so description compensates well.

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 concise sentences, front-loaded with purpose and parameters. No fluff.

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?

Explains filtering behavior and return shape. Missing explicit behavior when no parameters provided, but inferred. Adequate for a non-complex 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?

Schema coverage is 100%, but description adds value by clarifying ignored parameters and AND logic for metadata. Provides additional meaning beyond the 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?

Description clearly states the tool finds database connections by filtering on specific parameters. It distinguishes from connection_list by specifying filtering via parameters and referencing the same return shape.

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?

The description implies use for filtering connections but lacks explicit guidance on when to choose this over connection_list or other tools. Sibling tool list provides context but no direct advice.

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

Deploy Server

Other Tools