Skip to main content
Glama

list_players

Retrieve a list of all currently online players and view the server's maximum player capacity for Minecraft server administration.

Instructions

List all online players and the server's max player count.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler for the 'list_players' tool. It sends a 'list' command via RCON and returns the server's response.
    server.tool(
      "list_players",
      "List all online players and the server's max player count.",
      {},
      async () => {
        try {
          const response = await manager.rcon.send("list");
          return { content: [{ type: "text", text: response }] };
        } catch (error) {
          return {
            content: [
              {
                type: "text",
                text: `Failed: ${error instanceof Error ? error.message : String(error)}`,
              },
            ],
            isError: true,
          };
        }
      }
Behavior3/5

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

With no annotations provided, the description must carry the full burden of behavioral disclosure. It successfully indicates the scope (online players only, not offline) and mentions the max player count return value, but omits safety indicators (read-only status), permission requirements, or whether results are real-time vs cached.

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 with no wasted words. Key information (action, target resource, and secondary output) is front-loaded and immediately comprehensible.

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?

Given this is a simple read operation with no input parameters and no output schema, the description adequately compensates by specifying the two data points returned (current player list and max capacity). A brief note on output format would strengthen 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?

The input schema has zero parameters, establishing a baseline score of 4 per evaluation rules. The description appropriately does not introduce phantom parameters and correctly implies no filtering capabilities are available.

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 the tool lists 'all online players' and the 'server's max player count' using specific verbs and resources. However, it does not explicitly differentiate from sibling tools like list_ops (which lists operators), though the specificity of 'online players' provides implicit distinction.

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 provides implied usage through the specific scope ('online players' vs operators or worlds), but lacks explicit guidance on when to use this versus list_ops or other list commands, and does not mention prerequisites like server connectivity.

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