Skip to main content
Glama

server_get_history

Retrieve historical runtime statistics for a Minecraft server to analyze CPU and RAM usage trends over time.

Instructions

Get historical runtime statistics for a Minecraft server (CPU, RAM over time, useful for graphing trends)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
server_idYesServer ID or UUID

Implementation Reference

  • The handler implementation for the 'server_get_history' MCP tool, which fetches historical statistics for a Minecraft server from the Crafty client.
    server.tool(
      "server_get_history",
      "Get historical runtime statistics for a Minecraft server (CPU, RAM over time, useful for graphing trends)",
      {
        server_id: z.string().describe("Server ID or UUID"),
      },
      async ({ server_id }) => {
        try {
          const data = await client.get(`/servers/${server_id}/history`);
          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 mentions the tool retrieves data for graphing trends, but lacks details on permissions required, rate limits, data format, pagination, or error handling. For a data retrieval tool with zero annotation coverage, this leaves significant gaps in understanding its operational behavior.

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 and includes additional context without redundancy. Every part of the sentence adds value, making it appropriately sized and well-structured for quick understanding.

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 moderate complexity (retrieving historical data), lack of annotations, and no output schema, the description is incomplete. It covers the purpose and data types but omits behavioral details like response format, time range parameters, or error conditions. For a tool with no structured support, it provides a basic but insufficient overview.

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%, with the single parameter 'server_id' well-documented in the schema. The description does not add any parameter-specific information beyond what the schema provides, such as format examples or constraints. With high schema coverage, the baseline score of 3 is appropriate as the description does not compensate but also does not detract.

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 action ('Get historical runtime statistics') and resource ('Minecraft server'), with explicit details about the data retrieved ('CPU, RAM over time') and its purpose ('useful for graphing trends'). It effectively distinguishes this tool from sibling tools like 'server_get_stats' by emphasizing historical trend data rather than current statistics.

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 implies usage for graphing trends, which provides some context, but it does not explicitly state when to use this tool versus alternatives like 'server_get_stats' (for current stats) or other data retrieval tools. No guidance is given on prerequisites, exclusions, or specific scenarios where this tool is preferred.

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