Skip to main content
Glama

server_status

Check Minecraft server status to monitor uptime, player count, and server state for administration and troubleshooting.

Instructions

Get the current server status including running state, uptime, online players, and MOTD.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The "server_status" tool is registered and its handler is implemented here, calling manager.getStatus() to retrieve the data.
    server.tool(
      "server_status",
      "Get the current server status including running state, uptime, online players, and MOTD.",
      {},
      async () => {
        const status = await manager.getStatus();
        const uptimeStr = status.uptime
          ? formatUptime(status.uptime)
          : "N/A";
    
        const lines = [
          `Status: ${status.running ? "🟢 Running" : "🔴 Stopped"}`,
          `PID: ${status.pid ?? "N/A"}`,
          `Uptime: ${uptimeStr}`,
          `Players: ${status.players.length > 0 ? status.players.join(", ") : "None"}`,
          `MOTD: ${status.motd ?? "N/A"}`,
        ];
        return { content: [{ type: "text", text: lines.join("\n") }] };
      }
    );
Behavior3/5

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

With no annotations provided, the description carries full disclosure burden. It successfully enumerates return fields, clarifying what 'status' encompasses. However, it lacks operational context: no mention of whether this requires authentication, if it's safe to poll frequently, or whether the server must be running to return data.

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?

Single sentence, front-loaded with action verb, immediately followed by specific data points returned. No filler words or redundant phrases.

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?

Absence of output schema means description should document return values; it satisfies this by listing the four specific fields returned. For a simple read-only status tool, this is reasonably complete, though explicit mention of response structure (object vs string) would improve it further.

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?

Zero parameters presents a baseline of 4. The description correctly implies no filtering or input is needed to retrieve the full status snapshot.

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?

Clear verb 'Get' + resource 'server status' with specific enumerated fields (running state, uptime, online players, MOTD). Implicitly distinguishes from configuration getters like 'get_server_properties' by emphasizing runtime metrics, though it doesn't explicitly contrast with siblings like 'validate_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 explicit guidance on when to use versus alternatives. Given siblings include 'validate_server', 'get_server_properties', and 'get_world_info', the description should specify this retrieves live runtime metrics versus configuration, validation, or world-specific data.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/tamo2918/Minecraft-Server-MCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server