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

bedrock-map-builder-mcp

by xRookieFight

server_status

Read-only

Check live Minecraft Bedrock server state: world, BDS version, bridge ping, current project, and recent console lines. Use it to confirm connectivity and diagnose issues.

Instructions

What is connected right now: server state, world, BDS version, bridge ping, current project, and the last console lines.

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

Input Schema

NameRequiredDescriptionDefault
log_linesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

The readOnlyHint annotation already establishes the safety profile, but the description earns credit for disclosing what the response actually contains, including bridge ping and last console lines, which an agent could not know from annotations alone. It stops short of stating freshness, side effects on the connection, or whether the call blocks or is cached.

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?

One sentence, front-loaded with the framing clause and then a tight enumeration of returned fields. It is appropriately sized for a simple status tool, though the list is close to a raw field dump with no hierarchy among more and less important values.

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-optional-parameter read-only tool with no output schema, describing the returned facets in prose is close to sufficient. The main residual gap is that the log_lines control and its effect on response size are left for the agent to infer.

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% with a single optional log_lines integer (0-200). The phrase "the last console lines" implicitly links that parameter to the returned console output, which is a modest semantic gain, but neither the default value, the behavior at 0, nor the 200 cap is mentioned.

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 an interrogative frame ("What is connected right now") that clearly identifies this as a read-only status snapshot and enumerates the specific facets returned: server state, world, BDS version, bridge ping, current project, and console lines. It is concrete enough to distinguish from mutating siblings like server_start or server_stop, but it never differentiates itself from ws_status, which plausibly reports overlapping status.

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: an agent can infer this is the tool to call before other operations to confirm connectivity. There is no explicit when-to-use guidance, no mention of prerequisites, and no pointer to ws_status or server_console as alternatives for overlapping needs.

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