fivem-mcp-server

Overview Schema Source Related Servers Discussions Admin

Connection status

status

Read-onlyIdempotent

Reports RCON configuration, devcon client-console connection, and server log tailer so agents can verify FiveM test setup before running commands.

Instructions

Report RCON configuration for the server, the devcon connection to the FiveM client console, and the server log-file tailer. Call this first.

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

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`host`	Yes
`client`	Yes
`server`	Yes
`clientDevconPorts`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.6.0Oct 17, 2026

TDQS

A3.9/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety and repeatability profile is fully covered by structured data. The description adds real value by enumerating the three subsystems whose connection state is reported, but it says nothing about failure/degraded states or what a disconnected result looks like.

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: the first enumerates scope, the second is the usage directive. Nothing is redundant and the scope statement is front-loaded.

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?

With an output schema present, return values need not be explained, and the description gives the agent enough to know what is being checked and that it should run this first. It is a near-complete diagnostic preamble, missing only guidance on interpreting a failed connection.

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

Parameters4/5

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

The tool takes zero parameters, so the baseline is 4. The description correctly introduces no parameter semantics to confuse the agent, and the schema is trivially complete.

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 verb ("Report") and three concrete resources it inspects: RCON configuration, the devcon connection to the FiveM client console, and the server log-file tailer. That is far more specific than the bare name/title "status / Connection status", though it does not explicitly differentiate itself from sibling diagnostics like server_info or read_console.

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

Usage Guidelines4/5

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

"Call this first" is an explicit, actionable ordering directive that tells the agent when to reach for this tool relative to the rest of the toolset. There is no when-not guidance or named alternative, so it stops short of a 5.

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