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

bedrock-map-builder-mcp

by xRookieFight

set_sign

Writes text onto an existing Minecraft Bedrock sign block; place the sign first and use newline characters to create multiple lines.

Instructions

Write text on a sign block (place the sign first). Use \n for new lines.

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": {
      "pos": "<pos>",
      "text": "<text>"
    },
    "name": "set_sign"
  }
}

Input Schema

NameRequiredDescriptionDefault
posYes
sideNofront
textYes
waxedNo
dimensionNooverworld

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does disclose the key prerequisite (sign must already exist) and the newline convention, which are the most important behavioral facts. It omits whether existing text is overwritten, what happens if the target block is not a sign, and whether the write is reversible — meaningful gaps for a mutation tool with zero annotation coverage.

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?

Two short sentences with the operation front-loaded and the prerequisite and formatting convention packed into parentheses. Nothing is wasted and nothing is buried.

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?

The tool has a nested position object, two enum parameters, and two defaults, yet the description addresses only the text payload. There is no output schema, so the description should also indicate what happens on success or failure. For a five-parameter mutation with no annotations, it leaves too much for the agent to guess.

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?

With five parameters at 0% schema description coverage, the description must explain them, but it only touches 'text' (newline syntax) and implicitly 'pos'. The 'side', 'waxed', and 'dimension' parameters — including the non-obvious 'waxed' flag that presumably prevents further editing — are entirely unexplained, as is the coordinate object's shape.

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: 'Write text on a sign block'. An agent immediately knows the operation and its target. It does not explicitly differentiate itself from any sibling, but none of the listed siblings (palette_set, set_world_rules, fill_region, etc.) plausibly overlap, so the lack of a named alternative is a minor gap rather than confusion.

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?

The parenthetical '(place the sign first)' gives a concrete precondition that an agent must satisfy before calling, which is genuine usage guidance. However, it says nothing about when this tool is preferred over other writing/editing tools, nor about failure conditions such as targeting a non-sign block.

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