Skip to main content
Glama

Players

list_players
Read-onlyIdempotent

Retrieve Minecraft player data: online status, first/last seen, playtime. Set online=true to list current players with world, game mode, health, and ping.

Instructions

Everyone who has played here: online state, first and last seen, playtime in seconds; limit 0 only counts them. online true lists who is playing now instead, with world, game mode, health, food, level, ping, idle time, and location.

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": "list_players"
  }
}

Input Schema

NameRequiredDescriptionDefault
sortNo`name` by default
limitNoHow many items to return; 0 answers only the total, to count without listing
cursorNo`nextCursor` from the previous page
onlineNotrue: who is online now, with their state

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv4.2.1
    • addedInput schema / properties / sort / description
      Added value: +"`name` by default"
  2. First observedv4.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, closed-world behavior. The description adds useful behavioral context by explaining what data appears in each mode and how `limit 0` changes the result to a count, though it does not discuss pagination behavior or response shape beyond field names.

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 dense sentences cover the main listing mode, counting behavior, and online mode with its returned fields. The information is front-loaded, though the second sentence is packed and could be slightly easier to scan.

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?

With no output schema, the description usefully names the fields returned in each mode. It omits explicit pagination guidance and sibling routing, but for a 4-parameter read-only listing tool with fully described schema fields, it is largely complete.

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%, so the schema already documents all four parameters. The description reinforces `limit 0` counting and `online true` mode, but it does not add syntax or semantics for `sort` or `cursor` beyond what the schema provides, making the baseline 3 appropriate.

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 resource and scope: 'Everyone who has played here,' with offline and online variants. It distinguishes the two modes internally via `online true`, but does not differentiate from siblings such as `get_player` or `list_entities`, so it falls short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives clear usage context for the two main modes: default listing of all known players, `limit 0` for counting only, and `online true` for currently playing players. It does not name sibling alternatives or state when to prefer `get_player`, but the mode guidance is explicit.

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