Skip to main content
Glama

list_services

Discover all local DBngin-managed database services and their live running state via TCP port probing, returning names, types, ports, and IDs needed before starting or stopping a service.

Instructions

List all DBngin-managed local database services (PostgreSQL, Redis, MySQL, ...) with live running state detected by TCP port probing. Use this first to discover service names, types, ports and IDs before calling start_service / stop_service.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations, the description carries the burden, and it does disclose a meaningful behavioral trait: running state is detected by TCP port probing, which tells the agent how liveness is determined and that it reflects live state rather than cached metadata. It does not explicitly say the call is read-only or comment on cost/latency, though 'list' strongly implies non-mutation.

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, zero filler, with the scoping/first-step guidance front-loaded before the sibling call-outs. Every clause adds information the agent needs.

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?

No parameters, no annotations, no output schema, and the description covers what is returned (names, types, ports, IDs, running state) plus the recommended call order. Nothing an agent needs in order to invoke it correctly 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; baseline 4 applies. It still usefully enumerates what the result includes (names, types, ports, IDs, running state).

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 (list) and resource (DBngin-managed local database services) with examples of types and notes that state is live via TCP port probing. It is clearly distinguishable from start_service/stop_service, which it names, so no schema opening is needed to know what it does.

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

Usage Guidelines4/5

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

Gives explicit sequencing guidance: 'Use this first to discover service names, types, ports and IDs before calling start_service / stop_service.' It does not address how this differs from service_status, which may overlap in returning running state, but the primary when-to-use direction is unambiguous.

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