Skip to main content
Glama

server_lifecycle

Destructive

Start, stop, or restart an FXServer process launched by this MCP to manage FiveM server runtime; requires the executable path in config.json.

Instructions

Start, stop or restart an FXServer process launched by this MCP (needs executable in config.json)

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "action": "<action>"
    },
    "name": "server_lifecycle"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYes
serverNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is conveyed. The description adds the useful constraint that only MCP-launched processes can be managed and that config.json must declare an executable, but it says nothing about whether stop is graceful or whether in-flight state is lost.

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?

A single front-loaded sentence with no filler, and the precondition is attached where it is needed. Slightly dense with the parenthetical, but nothing is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive lifecycle mutation with no output schema, the definition covers what it acts on and the config precondition. It leaves out multi-server targeting semantics and the effect of stopping on running resources, which an agent needs before invoking stop.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must carry the parameter burden. The action enum is restated implicitly by the verb list, but the optional 'server' parameter is never explained — no indication of which server is targeted when it is omitted or how it maps to config.json entries.

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?

Names a specific resource (an FXServer process) and the exact verbs (start, stop, restart), and scopes it to processes launched by this MCP. That scoping separates it from a generic execute/control tool, though it never names a sibling alternative.

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 parenthetical states a real prerequisite (an executable must be present in config.json), which is genuine usage guidance. It does not say when to prefer this over process-level siblings like resource_control or dev_cycle, nor when not to stop.

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