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

bedrock-map-builder-mcp

by xRookieFight

project_note

Record persistent design decisions—style, scale, colour rules, gameplay constraints—for the rest of a Minecraft Bedrock project, and remove a note by index.

Instructions

Record a design decision that should hold for the rest of the project (style, scale, colour rules, gameplay constraints). remove takes the index of a note to drop.

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_note"
  }
}

Input Schema

NameRequiredDescriptionDefault
textNo
removeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations, the description must carry the full behavioral burden. It implies a persistent mutation ('should hold for the rest of the project') and a deletion path, but it does not disclose whether text and remove can be combined, what happens to existing notes, index base, error behavior, or return values.

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 description is short and front-loads the primary recording behavior. The second sentence efficiently covers removal, though the phrasing 'remove takes the index of a note to drop' is slightly terse.

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?

For a simple two-parameter tool with no output schema, the description covers the main purpose and the removal parameter. It is still incomplete about parameter interaction and indexing behavior, which matters because neither the schema nor annotations supply that information.

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%, so the description should compensate. It explains 'remove' as an index to drop, but does not clarify indexing base, and 'text' is only implicitly described as the note content; the interaction between the two optional parameters is also left unclear.

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 states a specific action and resource: recording a design decision that should persist for the project, plus removing a note by index. It is clear what the tool does, though it does not explicitly distinguish itself from any sibling tool.

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

Usage Guidelines4/5

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

The phrase 'design decision that should hold for the rest of the project' gives clear context for when to use it, and the remove sentence covers deletion. It does not mention exclusions or alternatives, but no obvious sibling overlaps are named.

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