Skip to main content
Glama

Get world border

get_world_border
Read-onlyIdempotent

Retrieves the main Minecraft world border's diameter, center, damage, and warning settings so AI agents can inspect boundary limits and behavior.

Instructions

The main world's border: size (diameter), centre, damage and warning settings.

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": "get_world_border"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered structurally. The description adds which settings are exposed (size, centre, damage, warning), which is genuinely useful, but says nothing about permissions, error behavior, or whether other dimensions' borders are visible. With annotations carrying the behavioral load, a 3 fits.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded clause with no filler; every term (diameter, centre, damage, warning) carries information. It is a sentence fragment with no verb, which is terse but slightly under-specified rather than padded.

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?

This is a simple zero-argument read with a full annotation set and an output schema, so the description need not explain return structure. The only real gap is the word 'main', which hints at a single-dimension scope without explaining whether other dimensions' borders are reachable.

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?

The tool takes zero parameters, so the baseline is 4. The description cannot add parameter meaning, and it correctly spends its words on the returned content instead.

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?

Names the resource precisely ('the main world's border') and enumerates exactly what aspect is reported: size as a diameter, centre, damage settings, and warning settings. It is easily distinguished from the write-side sibling set_world_border, though it relies on the title for the 'get' verb and the scope note about the main world is implicit rather than stated.

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?

There is no explicit guidance on when to call this rather than set_world_border, and no statement of prerequisites or conditions. Usage is only inferable from the field list and the word 'border' – a reader must guess that this is the read counterpart to the setter.

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