gmod-mcp

start_server

Launch a Garry's Mod dedicated server with optional map, gamemode, and tickrate settings. Records boot log for development.

Instructions

Starts the dedicated server through tools/start-server.sh [map] [gamemode] [tickrate] and records the log's boot boundary. Script defaults: rp_nycity_day/darkrp/33.

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

Input Schema

Name	Required	Description	Default
`map`	No
`gamemode`	No
`tickrate`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.0.0Jul 29, 2026

TDQS

B3.2/5.0

Behavior2/5

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

With no annotation hints, the description carries full burden. It mentions starting a server and recording a log boot boundary but omits critical behavioral traits like whether it stops an existing server, permissions required, or side effects. Minimal transparency.

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 efficient sentences without superfluous words. The primary action 'Starts the dedicated server' is front-loaded, and the script path and defaults are presented directly.

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

Completeness2/5

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

For a tool that starts a server with 3 parameters and no output schema, the description lacks essential context: behavior when server is already running, meaning of 'boot boundary', return value, and any error conditions. Incomplete for robust usage.

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?

Despite 0% schema description coverage, the description provides default values for all three parameters (map, gamemode, tickrate) in order, adding meaning beyond the bare schema. However, it does not explain the purpose or constraints of each parameter fully.

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?

The description clearly states 'Starts the dedicated server' with specific verb and resource. It further provides the script path and default values, making the purpose unmistakable and distinct from siblings like stop_server.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool versus alternatives such as run_console_command or stop_server. No conditions or prerequisites mentioned, leaving the agent without context for appropriate usage.

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