Skip to main content
Glama

stop_service

Stops a DBngin local database service by ID or name, waits until its port stops answering, and returns already stopped if the service is down.

Instructions

Stop a DBngin local database service. PostgreSQL is stopped with 'pg_ctl stop -m fast'; Redis receives 'SHUTDOWN NOSAVE' via redis-cli (fallback: taskkill only if the port listener is redis-server.exe). Waits until the port stops answering (up to 15s). Returns 'already_stopped' without failing if the service is down.

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": "stop_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.7/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 substantial work: it names the exact shutdown mechanism per engine (pg_ctl -m fast, Redis SHUTDOWN NOSAVE), the fallback condition, the 15s wait bound, and the idempotent 'already_stopped' return. It stops short of stating consequences explicitly — e.g. that NOSAVE discards unsaved Redis data — and says nothing about permissions.

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?

Three front-loaded sentences with the core action first, then mechanics, then failure semantics — no filler. The taskkill/redis-server.exe detail is arguably more implementation depth than an agent needs to select the tool, but it is at least factual and compact.

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?

There is no output schema, so the description usefully documents the one meaningful return case ('already_stopped') and the wait bound. The main gap is that the schema admits mysql, mariadb, mongodb and elasticsearch engines while the description explains mechanics only for postgresql and redis, leaving those paths opaque.

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%, so the schema already documents id, name, type and their precedence/disambiguation rules. The description adds no parameter-level meaning beyond that, which is the expected baseline when the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb+resource ('Stop a DBngin local database service'), which cleanly separates it from start_service and restart_service in the sibling set. It doesn't explicitly name those siblings as alternatives, so it falls just short of a 5.

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 by the verb — an agent calls this when it wants a service down — and the 'already_stopped without failing' note clarifies idempotent use. However, there is no explicit when-to-use vs when-to-restart guidance or any stated prerequisite (e.g. whether the service must be running, whether an ID is preferred over a name).

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