Skip to main content
Glama

server_get

Retrieve complete configuration details for a specific Minecraft server by providing its server ID or UUID.

Instructions

Get full configuration details for a specific Minecraft server

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
server_idYesServer ID or UUID

Implementation Reference

  • The 'server_get' tool is defined and implemented directly within the registerServerTools function in src/tools/servers.ts. It takes a server_id as input and fetches server details from the Crafty Controller API.
    server.tool(
      "server_get",
      "Get full configuration details for a specific Minecraft server",
      {
        server_id: z.string().describe("Server ID or UUID"),
      },
      async ({ server_id }) => {
        try {
          const data = await client.get(`/servers/${server_id}`);
          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 this is a read operation ('Get'), implying it's non-destructive, but does not mention authentication requirements, rate limits, error conditions, or what 'full configuration details' entails in terms of response format or data structure.

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 directly states the tool's purpose without unnecessary words. It is front-loaded and wastes no space, making it easy for an agent to parse quickly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the lack of annotations and output schema, the description is insufficient for a read operation tool. It does not explain what 'full configuration details' includes, potential response formats, or error handling, leaving significant gaps in understanding how to interpret results or handle failures.

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?

The input schema has 100% description coverage, with the 'server_id' parameter clearly documented as 'Server ID or UUID'. The description adds no additional semantic context beyond what the schema provides, such as examples or format specifics, so it meets the baseline for high schema coverage.

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 action ('Get') and resource ('full configuration details for a specific Minecraft server'), making the purpose immediately understandable. However, it does not explicitly differentiate from sibling tools like 'server_get_stats' or 'server_get_logs', which also retrieve server information but for different data types.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives such as 'server_list' (for overviews) or other 'server_get_*' tools (for specific data types). It lacks context about prerequisites or typical use cases, leaving the agent to infer usage from the tool name alone.

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