Skip to main content
Glama

server_list

List all Minecraft servers managed by Crafty Controller with their IDs, names, types, ports, and configurations for monitoring and management.

Instructions

List all Minecraft servers managed by Crafty Controller with their IDs, names, types, ports, and configurations

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Implementation of the 'server_list' tool handler which queries the Crafty Controller API for a list of servers.
    server.tool(
      "server_list",
      "List all Minecraft servers managed by Crafty Controller with their IDs, names, types, ports, and configurations",
      {},
      async () => {
        try {
          const data = await client.get("/servers");
          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 };
        }
      }
    );
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool lists servers but does not describe behavioral traits such as authentication requirements, rate limits, pagination, error handling, or whether the operation is read-only (implied by 'List' but not confirmed). This leaves significant gaps for a tool with no annotation coverage.

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 core purpose ('List all Minecraft servers') and adds necessary details (managed by Crafty Controller with specific attributes). Every word earns its place, with no redundancy or wasted information.

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 the tool's complexity (simple list operation), no parameters, and no output schema, the description is adequate but incomplete. It specifies what information is returned but lacks details on output format (e.g., JSON structure), error cases, or dependencies like authentication. With no annotations, it should provide more behavioral context to be fully complete.

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 tool has 0 parameters, and schema description coverage is 100%, so no parameter information is needed. The description appropriately does not discuss parameters, making it complete in this regard. A baseline of 4 is applied as it meets expectations for a parameterless tool.

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 verb ('List') and resource ('all Minecraft servers managed by Crafty Controller'), including the scope of information returned (IDs, names, types, ports, and configurations). It distinguishes itself from sibling tools like 'server_get' (which retrieves a single server) and 'server_list_backups' (which lists backups rather than servers).

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?

The description implies usage context by specifying 'all Minecraft servers managed by Crafty Controller,' suggesting this is for retrieving a comprehensive list. However, it does not explicitly state when to use this tool versus alternatives like 'server_get' for a single server or provide exclusions (e.g., not for filtered lists).

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