Skip to main content
Glama

Controlar o processo do servidor

fivem_server_control

Start, stop, or restart an FXServer process through txAdmin to control server availability; these actions disconnect all online players.

Instructions

start, stop ou restart do FXServer pelo txAdmin. Derruba todo mundo que estiver online — para recarregar um resource use fivem_command com "ensure ".

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

Input Schema

NameRequiredDescriptionDefault
actionYesAção no processo do servidor

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.4/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 it does disclose the key consequence: the operation kicks everyone who is online. It does not distinguish which actions carry that impact (start presumably does not), nor does it mention permissions, downtime length, or whether the restart is graceful.

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?

Two short sentences, zero filler. The destructive consequence and the redirect to fivem_command are both front-loaded, and the parenthetical alternative is compact rather than a separate paragraph.

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 one-parameter tool with no output schema and no annotations, the description covers purpose, blast radius, and the main alternative. Minor gaps remain around per-action behavior (does start have any impact on players?) and permissions, but nothing that would cause a mis-call.

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% and the single enum parameter already documents the three allowed values, so the schema does the heavy lifting. The description restates the same action set without adding format, default, or per-action semantics beyond what the enum provides.

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 set (start, stop, restart) against a specific resource (the FXServer process) and names the controlling layer (txAdmin). An agent can immediately distinguish this from the sibling fivem_command, which acts on resources rather than the process.

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 names an alternative tool and the condition that selects it: to reload a resource, use fivem_command with "ensure <resource>" instead of restarting the server. This is exactly the confusion case an agent would otherwise get wrong, and it is stated up front.

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