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

bedrock-map-builder-mcp

by xRookieFight

project_info

Read-only

Retrieves the current Minecraft Bedrock build project's saved decisions, palette, regions, plan progress, and recent operations so clients can resume work with full context.

Instructions

Everything the current project remembers: decisions, palette, regions, plans with progress, recent ops.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds that this is an aggregate read spanning five distinct stores, which is genuine context, but it says nothing about payload size, cost, truncation, or whether 'recent ops' is bounded — relevant for a tool that returns 'everything'.

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?

One compact, front-loaded clause with no filler, and the key scoping phrase ('current project') comes first. It is a noun phrase rather than a sentence, which slightly softens the framing of what the tool actually does.

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

Completeness3/5

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

With no output schema and no parameters, the description carries the burden of explaining the return surface; enumerating the five content domains does much of that work. It remains silent on how large the response is, whether sections can be absent, and how it relates to the more granular sibling tools.

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 input schema is empty and nothing further is required from the description.

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?

The description names a specific resource, the current project's accumulated memory, and enumerates its contents (decisions, palette, regions, plans with progress, recent ops), so an agent can tell it is an aggregate snapshot rather than a single-domain read. It omits an explicit verb ('return'/'get') and never distinguishes itself from siblings such as plan_list or region_stats, which overlap its scope.

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 or when-not-to-use guidance and no named alternative, even though plan_list, plan_show, region_stats, markers and check_map all cover subsets of the same data. The enumeration of contents only weakly implies 'use for an overview'.

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