Skip to main content
Glama

restart_service

Restart a DBngin local PostgreSQL or Redis service by stopping and starting it, useful when a running service needs to reload configuration or recover.

Instructions

Restart a DBngin local database service (stop_service followed by start_service). Supported engines: postgresql and redis. Use only when a restart is actually needed; for a stopped service, prefer start_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": "restart_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

A4.2/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does disclose the significant implementation detail that this is a stop-then-start sequence (implying downtime) and constrains engine support, but it says nothing about whether in-flight connections are dropped, whether data is preserved, required permissions, or how failures mid-restart are reported.

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?

Three short sentences, front-loaded with the action and its composite nature, then the engine scope, then the usage guardrail. No filler or restatement of the tool name.

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 mutation tool with no annotations and no output schema, the description covers the composite behavior, the engine scope, and the alternative to prefer, which is enough to call it correctly. It stops short of describing restart side effects (downtime, dropped connections, error behavior if the service is already running), which matters for a destructive stop/start operation.

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 id/name/type precedence and disambiguation rules are already fully documented in the schema, establishing a baseline of 3. The description adds only a scope statement about supported engines, and that statement ('postgresql and redis') sits uneasily beside an enum that also permits mysql, mariadb, mongodb, and elasticsearch – useful as a guardrail but not clarifying for parameters.

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 and resource ('Restart a DBngin local database service') and immediately discloses the composite implementation (stop_service followed by start_service), which is exactly the kind of detail an agent needs to reason about the operation. It also names the supported engines, so the agent can tell at a glance whether the tool applies to a given service.

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?

Explicitly bounds usage: 'Use only when a restart is actually needed; for a stopped service, prefer start_service.' That is a when-to-use condition plus a named alternative sibling and the condition that selects it, which is the strongest form of routing guidance.

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