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

bedrock-map-builder-mcp

by xRookieFight

palette_set

Set project-wide palette roles for walls, roofs, floors, trim, and lights using blocks or weighted mixes, so later builds keep a consistent look; pass null to remove a role.

Instructions

Set project wide palette roles (wall, roof, floor, trim, light, path, ...) so every later build keeps the same look. Values are blocks or weighted mixes. Pass null to remove a role.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "roles": "<roles>"
    },
    "name": "palette_set"
  }
}

Input Schema

NameRequiredDescriptionDefault
rolesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

With empty annotations the description carries the full burden, and it discloses two important behaviors beyond the name: the setting persists globally to all later builds, and null removes a role (i.e., what gets cleared). It still omits whether unmentioned roles are preserved or reset, permission/auth requirements, and error behavior on invalid block names.

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?

Three tight sentences, front-loaded with the operation and its purpose before the value format and the null case. No filler and nothing redundant.

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 single nested-object parameter with no output schema and no annotations, the description covers purpose, persistence semantics, accepted value shapes, and removal. The main remaining gap is whether setting roles merges with or overwrites existing ones and what an invalid block reference does.

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?

Schema coverage is 0%, so the description must explain a nested map whose values are a union of string, object-of-numbers, or null. It does map each branch usefully ('blocks' = string, 'weighted mixes' = number map, 'null' = removal), but the role keys are only shown as open-ended examples ('wall, roof, floor, trim, light, path, ...'), leaving the key namespace undefined.

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 verb ('Set') and resource ('project wide palette roles') and enumerates example role names (wall, roof, floor, trim, light, path), making the operation concrete. It does not explicitly contrast itself with siblings like set_world_rules or fill_region, but the 'project wide' scope and 'every later build' framing make it distinguishable on its own.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied rather than stated: 'so every later build keeps the same look' signals this is for persistent, project-wide styling rather than one-off placement. The removal path ('Pass null to remove a role') is explicit, but there is no when-not guidance and no named alternative for non-persistent or local styling.

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