Skip to main content
Glama

server_get_status

Read-only

Retrieve bridge readiness, uptime, enabled dev features, and opted-in test client IDs for one FiveM server or all configured servers to verify operational status.

Instructions

Bridge readiness, uptime, enabled dev features and opted-in test client IDs. Omit server to get every configured server.

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_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
serverNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is handled elsewhere. The description adds genuine value by enumerating the returned data categories and the all-servers default, but it says nothing about error behavior for an unknown server name or about output shape, which annotations do not cover.

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?

Two short sentences with no filler, and the returned-data list is front-loaded ahead of the scoping note. The fragmentary noun-phrase style slightly reduces readability but wastes no words.

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?

This is a simple read tool with one optional parameter, full annotation coverage and no output schema, so the bar is low. The description covers the payload contents and the default-wide scope; only edge-case behavior for an invalid server name is left unstated.

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 0% for the single optional 'server' parameter, so the description must carry the meaning, and it does clarify that omitting it returns all configured servers. It does not explain what value form 'server' expects beyond the schema's regex pattern, so the compensation is partial.

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 names the concrete data the tool surfaces (bridge readiness, uptime, enabled dev features, opted-in test client IDs), which lets an agent distinguish it from log- or diagnostics-oriented siblings. It lacks an explicit verb like 'get' or 'report', so the purpose is inferred from the field list rather than stated directly.

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 only guidance is 'Omit server to get every configured server,' which explains the default scope but not when to choose this tool over server_get_diagnostics or server_get_logs. Usage is implied by the returned-content list rather than by any explicit when-to-use or when-not-to-use statement.

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