Skip to main content
Glama
bedrock-map-builder-mcp

bedrock-map-builder-mcp

by xRookieFight

world_backups

Read-only

List Minecraft: Bedrock Edition world backups, optionally filtered by world, to review restore points before edits or exports.

Instructions

List world backups.

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

Input Schema

NameRequiredDescriptionDefault
worldNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

The readOnlyHint annotation already establishes that this is a safe read, so the description adds nothing about safety. It also says nothing about what a backup entry contains (timestamps, IDs, sizes), whether results are paginated or ordered, or how an empty result is represented — all behavior an agent would want before calling.

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?

The sentence is front-loaded and contains no filler or redundancy. Its brevity is close to the floor of usefulness, but nothing in the text is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only list tool with no output schema and an undocumented parameter, the description should at minimum explain the world filter and the shape of the returned list. As written it covers only the bare purpose, so an agent cannot predict results or parameter effects.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for the single optional 'world' parameter, and the description does not compensate. It never says whether 'world' filters backups to one world or is ignored, nor what happens when it is omitted, leaving the only parameter effectively undocumented.

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?

States a specific verb and resource ('List world backups'), which is unambiguous about the operation itself. It does not differentiate from related siblings such as world_backup, world_restore, or world_list, so an agent must infer that this is the read-only enumeration of existing backups.

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 when-to-use guidance, no mention of when to prefer world_restore or world_backup instead, and no stated prerequisites. The agent is left to infer the entire usage context from the three-word phrase.

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