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

db-access-mcp

by Rheopyrin
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

tunnel_list

Monitor active database tunnels by listing those currently open, each with a live health probe. Identifies connections and pins for each tunnel.

Instructions

List the tunnels currently open in THIS MCP instance, with a live health probe each. tunnel_id is accepted by down_tunnel; "connections" are the pools holding the tunnel, "pins" are up_tunnel holds. Configured-but-not-open tunnels are visible via connection_list (the tunnel field).

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.7/5.0
Behavior4/5

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

With no annotations, the description must convey behavioral traits. It mentions a 'live health probe' and describes output fields (tunnel_id, connections, pins), indicating it's a read-only operation. No side effects are suggested, but it could be more explicit about idempotency or rate limits.

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 sentences, no waste. The main action is front-loaded, and additional context about related tools and fields is provided efficiently.

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?

For a parameterless list tool with no output schema, the description sufficiently covers what it does and what the output contains. It references sibling tools to fill context, making it complete for the agent to select and invoke 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?

The tool has zero parameters, so schema description coverage is 100%. Baseline for 0 params is 4, and the description does not need to add parameter details. It adds value by explaining what the output contains.

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 clearly states 'List the tunnels currently open in THIS MCP instance' with a specific verb and resource. It distinguishes from sibling tools by mentioning connection_list for configured-but-not-open tunnels, and clarifies how fields relate to other tools like down_tunnel and up_tunnel.

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?

Provides explicit guidance on when to use this tool (to see open tunnels) and points to connection_list as an alternative for configured-but-not-open tunnels. It also explains the meaning of 'connections' and 'pins' in relation to other tools, helping the agent choose correctly.

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