Skip to main content
Glama

set_time

Change Minecraft world time using preset options like day, night, or custom tick values to control lighting and gameplay conditions.

Instructions

Set the world time. Presets: 'day' (1000), 'noon' (6000), 'sunset' (12000), 'night' (13000), 'midnight' (18000), 'sunrise' (23000). Or use a tick value.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
timeYesTime value: 'day', 'noon', 'sunset', 'night', 'midnight', 'sunrise', or a tick number (0-24000)

Implementation Reference

  • The "set_time" tool is registered and implemented in src/tools/command-tools.ts. It takes a time string (preset or tick value), resolves it to a tick number, and sends a "time set" command via RCON.
    server.tool(
      "set_time",
      "Set the world time. Presets: 'day' (1000), 'noon' (6000), 'sunset' (12000), 'night' (13000), 'midnight' (18000), 'sunrise' (23000). Or use a tick value.",
      {
        time: z
          .string()
          .describe("Time value: 'day', 'noon', 'sunset', 'night', 'midnight', 'sunrise', or a tick number (0-24000)"),
      },
      async ({ time }) => {
        const presets: Record<string, string> = {
          day: "1000",
          noon: "6000",
          sunset: "12000",
          night: "13000",
          midnight: "18000",
          sunrise: "23000",
        };
        const value = presets[time.toLowerCase()] ?? time;
        try {
          const response = await manager.rcon.send(`time set ${value}`);
          return { content: [{ type: "text", text: response }] };
        } catch (error) {
          return {
            content: [
              {
                type: "text",
                text: `Failed: ${error instanceof Error ? error.message : String(error)}`,
              },
            ],
            isError: true,
          };
        }
      }
    );
Behavior4/5

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

No annotations provided, so description carries full disclosure burden. It adds valuable behavioral context by mapping preset keywords to exact tick values (day=1000, etc.), explaining the underlying numeric system. Could improve by noting if change is immediate, affects all worlds/players, or persists after restart.

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?

Two compact sentences with zero waste. First sentence establishes operation, second provides reference data (preset mappings). Perfectly front-loaded and appropriately sized for a single-parameter tool.

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?

Complete for a simple setter with one parameter and 100% schema coverage. The preset enumeration provides sufficient input documentation. Minor gap: doesn't mention immediate effect scope (single world vs. global) or output behavior, but adequate given tool simplicity.

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?

Schema has 100% coverage, but description adds crucial semantic enrichment: it enumerates all six valid preset strings and maps them to specific numeric tick values. This transforms abstract 'time value' into concrete actionable values, significantly augmenting the schema documentation.

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?

Excellent: specific verb 'Set' + resource 'world time' clearly identifies the operation. Distinct from siblings like set_weather, set_gamemode, set_block through precise resource naming. The scope is immediately clear.

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?

Provides implied usage by documenting preset options versus raw tick values, helping users choose input formats. However, lacks explicit guidance on when to call this vs. other state-modification tools, or prerequisites like server running status.

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/tamo2918/Minecraft-Server-MCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server