Skip to main content
Glama

service_status

Get live status of a DBngin service: running state, PID, port, uptime, Redis PING, and paths. Use it to verify whether an engine is up and answering before starting, stopping, or debugging.

Instructions

Detailed live status of one DBngin service: running state, PID, process name, port answering, Redis PING, uptime/started-at, and data/bin/log paths. Works for every engine type (detection is port-probe based for engines other than postgresql/redis).

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

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, the description carries the full burden and does well: it discloses that results are 'live', that engine detection is port-probe based for engines other than postgresql/redis, and what fields are gathered. It stops short of stating the operation is read-only/non-mutating or that probing may be slow or fail if the port is closed.

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?

Two tight sentences, front-loaded with the purpose and followed by the engine-coverage caveat. The long field enumeration is dense but each item is meaningful for a tool with no output 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?

No output schema exists, and the description compensates by enumerating the returned fields and explaining engine coverage. Minor gaps remain: no statement of read-only behavior, no note on what happens when a service is stopped or unreachable.

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 description coverage is 100%, with id/name/type each documented including precedence and disambiguation rules. The description adds nothing about the parameters, so the baseline of 3 applies; the schema does all the work here.

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 operation on a specific resource ('Detailed live status of one DBngin service') and enumerates exactly what that status contains (running state, PID, port answering, PING, uptime, paths). This clearly separates it from list_services (enumeration), get_logs (log retrieval), and the start/stop/restart siblings (mutation).

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?

Usage is implied rather than stated: an agent can infer this is the tool to call to inspect a single service's health. There is no explicit when-to-use/when-not guidance and no named alternative for cases like 'list everything' (list_services) or 'why did it fail' (get_logs).

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