Skip to main content
Glama

server_get_stats

Retrieve live Minecraft server runtime statistics including CPU/RAM usage, player count, world details, and operational status for monitoring and management.

Instructions

Get live runtime statistics for a Minecraft server including CPU/RAM usage, online player count and list, world name/size, MOTD, version, and whether it is running

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
server_idYesServer ID or UUID

Implementation Reference

  • The handler function for the `server_get_stats` tool which fetches server statistics via an API call.
    async ({ server_id }) => {
      try {
        const data = await client.get(`/servers/${server_id}/stats`);
        return { content: [{ type: "text", text: JSON.stringify(data, null, 2) }] };
      } catch (error) {
        const msg = error instanceof Error ? error.message : String(error);
        return { content: [{ type: "text", text: `Error: ${msg}` }], isError: true };
  • Registration of the `server_get_stats` tool with its description and input schema.
    server.tool(
      "server_get_stats",
      "Get live runtime statistics for a Minecraft server including CPU/RAM usage, online player count and list, world name/size, MOTD, version, and whether it is running",
      {
        server_id: z.string().describe("Server ID or UUID"),
      },
Behavior3/5

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

No annotations are provided, so the description carries full burden. It indicates this is a read operation ('Get') and specifies the data returned, but does not disclose behavioral traits like authentication requirements, rate limits, error conditions, or whether it's real-time versus cached data. The description adds value by listing metrics but lacks operational context.

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, efficient sentence that front-loads the purpose and enumerates key metrics without unnecessary words. Every part earns its place by clarifying scope and content.

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 no annotations and no output schema, the description is moderately complete: it specifies the metrics returned but lacks details on format, pagination, or error handling. For a read-only tool with one parameter, it's adequate but has gaps in behavioral context.

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 100% for the single parameter (server_id), so the schema already documents it fully. The description does not add meaning beyond the schema, as it does not explain parameter usage or constraints. Baseline 3 is appropriate when schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the specific action ('Get live runtime statistics') and resource ('Minecraft server'), with a detailed list of included metrics (CPU/RAM usage, player count/list, world name/size, MOTD, version, running status). It distinguishes from siblings like server_get (general server info) or server_get_logs by specifying runtime statistics.

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 description implies usage for monitoring server performance, but does not explicitly state when to use this tool versus alternatives (e.g., server_get for static configuration, server_get_logs for logs, or server_list for basic listings). No exclusions or prerequisites are mentioned.

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/HadiCherkaoui/crafty-mcp'

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