Skip to main content
Glama

start_service

Start a local DBngin database service (PostgreSQL or Redis) and wait until its port responds. Resolve by service ID, or by name plus type, to launch the right instance.

Instructions

Start a DBngin local database service. Supported engines: postgresql (postgres.exe spawned detached with the same command line as the DBngin app) and redis (hidden detached redis-server). Waits until the service port answers (up to 15s). Returns 'already_running' without failing if the service is up. Resolve the service by 'name' plus optional 'type' (names can repeat across engine types) or by 'id'.

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

Input Schema

NameRequiredDescriptionDefault
idNoDBngin service ID from list_services. Takes precedence over 'name'.
nameNoService name as shown in DBngin (case-insensitive). Names can repeat across engine types; pass 'type' to disambiguate (e.g. { name: 'myapp', type: 'redis' }).
typeNoEngine type used to disambiguate services that share the same name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does well: it discloses the detached spawn mechanism, a bounded wait of up to 15s for the port to answer, and a non-error idempotent return value ('already_running'). Gaps remain around what happens when the 15s wait expires, whether elevated permissions are needed, and whether a failed start leaves a partial process behind.

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?

Four dense sentences, front-loaded with the action, then engine specifics, then timing and return behavior, then resolution rules. Every sentence carries information, though the name/type/id resolution sentence largely duplicates the schema.

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 state-changing tool with no output schema and no annotations, the description covers the important surface: supported engines, blocking wait duration, and the idempotent success case. Missing timeout-failure semantics and permission requirements keep it short of complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so all three parameters, including the enum and the id-takes-precedence rule, are already documented in the schema. The description's resolution sentence restates that logic (name plus optional type, or id) without adding syntax or format detail, so baseline 3 applies.

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?

Names a specific verb and resource ('Start a DBngin local database service') and immediately scopes it with the two supported engines and their spawn behavior. The verb alone separates it from restart_service, stop_service, and service_status, so an agent can pick it without ambiguity.

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 when this applies ('Returns already_running without failing if the service is up' suggests it is for bringing a stopped service up), but it never explicitly names an alternative or exclusion condition, e.g. use restart_service to recycle a running service. It also doesn't state preconditions like whether the service must exist first (list_services is only mentioned via the id parameter).

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