Skip to main content
Glama

Change world border

set_world_border

Update any combination of the main world's border settings in one call; omitted values stay unchanged, and the resulting border is returned.

Instructions

Change any combination of the main world's border settings in one call; omitted settings are left alone. Returns the resulting border.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "set_world_border"
  }
}

Input Schema

NameRequiredDescriptionDefault
sizeNoNew diameter in blocks.
grow_byNoChange the diameter by this much (negative shrinks).
center_xNoNew centre X (with center_z).
center_zNoNew centre Z (with center_x).
damage_per_blockNoDamage per second per block outside the border.
warning_distanceNoShow the warning this many blocks from the border.
transition_secondsNoAnimate the size change over this many seconds.
warning_time_secondsNoShow the warning this many seconds before it shrinks past.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful semantics beyond that: a partial-update contract where omitted settings are untouched, and the fact that the post-change border is returned. It does not state whether size and grow_by conflict or how they combine.

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 short sentences, both load-bearing, with the partial-update rule and return behavior front-loaded. Nothing is repeated from the schema or annotations.

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?

For an 8-parameter, all-optional mutation tool with a full output schema and annotations, the description covers the essential usage model. The remaining gap is interaction between size and grow_by when both are supplied, which is left for the agent to guess.

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?

With 100% schema description coverage, the schema already documents every parameter's meaning and range. The description adds only the aggregate rule that null/omitted values are left unchanged, which the schema implies through default: null but does not spell out.

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?

"Change any combination of the main world's border settings" gives a specific verb plus resource, and the qualifier "main world's" scopes it precisely. "Returns the resulting border" also distinguishes it from the read-only get_world_border sibling without naming it.

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?

"Change any combination ... in one call; omitted settings are left alone" tells the agent exactly how to invoke it: pass only the fields of interest rather than a full snapshot. It stops short of naming get_world_border as the alternative for inspecting state before a change, so there is no explicit when-not guidance.

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