Skip to main content
Glama

server_get_diagnostics

Read-only

Retrieves a FiveM server’s status, its 10 most recent errors, and the last managed process exit to help diagnose crashes and failures.

Instructions

Status plus the 10 most recent server errors and the last managed process exit

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

Input Schema

NameRequiredDescriptionDefault
serverNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already establish that this is a safe, read-only, non-destructive operation. The description adds useful detail about what is returned, including the limited set of recent errors and last managed process exit, but does not cover freshness, defaults, or server scoping behavior.

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?

The description is a single compact sentence with no unnecessary wording. The key returned elements are front-loaded and easy to scan.

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?

Given the tool's simplicity and the absence of an output schema, the description adequately outlines the returned values. However, it does not explain the optional server parameter or when this diagnostics tool should be preferred over related status and log tools.

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?

The input schema has one optional 'server' parameter with 0% schema description coverage, and the description does not mention the parameter at all. An agent cannot tell from the description whether omitting it targets the current server or whether a specific server name is required.

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?

The description clearly states what the tool returns: server status, the 10 most recent server errors, and the last managed process exit. It is specific about the resource and contents, though it does not explicitly distinguish itself from the related server_get_status or server_get_logs siblings.

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?

There is no explicit guidance on when to use this tool versus alternatives such as server_get_status or server_get_logs. The description implies it is a diagnostics aggregation, but does not state selection criteria or exclusions.

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