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

bedrock-map-builder-mcp

by xRookieFight

use_connection

Choose the target connection (BDS or WS) so tools act on the correct world when both a Bedrock Dedicated Server and a /connect client are active.

Instructions

Pick which connection the tools act on when both a BDS world and a /connect client are up.

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": {
      "target": "<target>"
    },
    "name": "use_connection"
  }
}

Input Schema

NameRequiredDescriptionDefault
targetYes

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?

With no annotations, the description carries the full behavioral burden, and it does disclose the key trait: this changes the target that all other tools subsequently act on, i.e. a global session-state mutation. It omits whether the choice persists across calls/sessions, whether it fails when a connection is down, and whether switching mid-work has side effects.

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?

A single short sentence with the verb and effect front-loaded and no padding. It is tight but borders on cryptic, leaving the reader to decode 'BDS' and '/connect client' from context.

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 one-parameter routing tool with no output schema and no annotations, the description covers the essentials of what it does and when it matters. It leaves out default behavior, persistence, and failure modes, which an agent needs to invoke it safely.

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 description coverage is 0%, so the description must compensate for the single 'target' parameter. It gives contextual meaning to the enum values ('BDS world' for bds, '/connect client' for ws) but never explicitly maps target=bds / target=ws, and 'ws' itself is left unexpanded.

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 uses a concrete verb ('Pick') and names the resource being routed ('which connection the tools act on'), which is specific enough to separate it from the map/region/plan siblings that operate on world content. It stops short of naming itself as a session-level routing switch, and the two connection kinds are only obliquely described.

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?

It supplies a genuine context condition for use: only when both a BDS world and a /connect client are up. However, it gives no guidance on how to choose between the two targets, no statement of the default when the tool isn't called, and no note on what to do if only one connection exists.

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