goldsrc-query-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| pingA | Measure round-trip latency to a GoldSrc server. Use to check if a server is reachable and responsive. |
| get_server_infoA | Get server metadata: name, map, player counts, VAC status, and more. Use to get an overview of a server or check if it is online. |
| get_playersA | Get the current player list with names, scores, and time in-game. Use to see who is on a server. |
| get_rulesA | Get all server cvars. Use to inspect server configuration. |
| get_allA | Get server info, player list, and rules in one call. Use this instead of calling get_server_info, get_players, and get_rules separately. |
| send_rconA | Send a single RCON command and return the response. Use for one-off commands; prefer send_rcon_batch when sending multiple commands. |
| send_rcon_batchA | Send multiple RCON commands over a single authenticated connection. Use instead of rcon when running more than one command. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
Each tool has a clearly distinct purpose: ping for latency, get_server_info for metadata, get_players for player list, get_rules for cvars, get_all for a combined query, and send_rcon/send_rcon_batch for command execution. The descriptions explicitly clarify when to use each, especially distinguishing the single vs. batch RCON tools and the combined vs. individual getters.
All tool names follow a consistent verb_noun pattern with lowercase and underscores: ping, get_*, send_*. This makes the toolset predictable and easy to navigate.
With 7 tools, the server is well-scoped. Each tool serves a necessary function for querying and managing a GoldSrc server, with no redundancy or excessive bloat.
The toolset covers the full lifecycle of interacting with a GoldSrc server: checking reachability (ping), retrieving server info, players, and rules, fetching everything in one call, and sending RCON commands in both single and batch modes. There are no obvious gaps.