Skip to main content
Glama

Set time of day

set_time

Set or advance the main Minecraft world's time of day with tick values or presets such as day, noon, sunset, night, midnight, and sunrise.

Instructions

Set or advance the time of day in the main world.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "value": "<value>"
    },
    "name": "set_time"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNoSet the time, or advance it by value ticks.set
valueYesTicks (20 per second, 24000 per day; 0-24000 when mode is 'set') or a preset: day=1000, noon=6000, sunset=12000, night=13000, midnight=18000, sunrise=23000.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare this is a non-read-only, non-idempotent, non-destructive mutation, so the safety profile is covered. The description adds the useful scoping fact that only the main world's time changes, but says nothing about permission/op requirements, effect on the daylight cycle or sleeping, or whether the change persists across reloads.

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?

A single front-loaded sentence with the action and the scope in the first few words; no filler or redundancy.

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?

Given a two-parameter tool with full schema coverage, an output schema, and annotations covering mutability, the description supplies the one key non-schema fact (main world scope). Only minor gaps remain, such as permission prerequisites or interaction with the game's day/night cycle.

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 tick limits, preset names and their numeric values all documented inline, so the schema carries the burden. The description only echoes the set/advance duality and adds no format or edge-case detail beyond that baseline.

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?

"Set or advance the time of day in the main world" names a concrete verb pair and resource, and the counterpart read tool (get_time) is easy to distinguish. It stops short of naming any sibling or stating scope differently, so it is clear but not fully differentiated.

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 dual verb "set or advance" implicitly maps to the two modes, and "main world" implies scope, but there is no explicit when-to-use/when-not guidance or mention of alternatives such as reading time first. Usage must be inferred from the schema.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.