list_all_serversRetrieve overview and operational status for every managed Minecraft Bedrock server. Use it to check which servers are running, stopped, or need attention.
Retrieve overview and operational status for all managed Minecraft Bedrock servers.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
| Name | Required | Description | Default |
|---|---|---|---|
| servers | No |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full disclosure burden. The verb "Retrieve" signals a safe read, and it says what is returned (overview plus operational status), but it says nothing about authorization requirements, cost of enumerating every server, or whether results are cached or live.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single sentence with no filler, front-loading the verb and the scope constraint. Every word earns its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With an output schema present and no input parameters, the description only needs to frame what the call does and roughly what it yields, which it does. Minor gaps remain around authentication or scale, but nothing blocks correct invocation.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool takes zero parameters, so there is nothing for the description to clarify beyond the schema. Baseline 4 applies for a parameterless tool.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description gives a specific verb (Retrieve) and resource (all managed Minecraft Bedrock servers), and the scope word "all" distinguishes it from the singular sibling get_server_status. It stops short of naming that sibling explicitly, so an agent must infer the boundary between listing and fetching one server's status.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Usage is only implied: "all managed ... servers" suggests a fleet-wide inventory use case versus the single-server get_server_status, but the description never states when to prefer this over get_server_status or get_system_info. No prerequisites or exclusions are given.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.