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

bedrock-map-builder-mcp

by xRookieFight

markers

Read-only

Retrieve saved points from earlier project builds—spawns, doors, chests, checkpoints, and portals—grouped by the operation that created them.

Instructions

Markers saved from earlier builds in this project (spawns, doors, chests, checkpoints, portals...), grouped by the op that made them.

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

Input 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?

The readOnlyHint=true annotation already establishes this is a safe read, so the description does not need to argue that. It does add genuinely new behavioral context: the markers originate from previous builds and are grouped by the op that produced them, which tells the agent the result is organized by origin rather than being a flat list. It stops short of describing the exact return structure, ordering, or whether empty projects yield an empty grouping.

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?

It is a single tight sentence with the core definition front-loaded, followed by examples and the grouping behavior. The parenthetical enumeration earns its place by clarifying what a 'marker' is, though the trailing ellipsis is slightly loose.

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 a zero-parameter read-only tool with no output schema, the description needs to carry the burden of explaining what comes back, and it does so at a high level by stating the content types and the op-based grouping. The remaining gap is the precise response shape (keyed object vs. list of groups), which is implied but not stated.

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, and the schema confirms an empty properties object, so there is nothing for the description to disambiguate. The baseline for a parameterless tool applies, and the description does not introduce any confusing pseudo-parameters.

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 the resource (markers saved from earlier builds in this project), illustrates the concrete kinds of markers (spawns, doors, chests, checkpoints, portals) and states the grouping key (the op that created them). It lacks an explicit verb like 'list' or 'get', but the resource and scope are unambiguous enough to distinguish it from siblings such as region_mark or block_search.

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 statement of when to call this instead of alternatives. An agent is left to infer that it should use markers rather than region_mark, block_search, or project_info when it wants previously recorded build markers. The phrase 'saved from earlier builds' hints at the retrieval use case but provides no explicit guidance or exclusions.

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