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

bedrock-map-builder-mcp

by xRookieFight

server_stop

Stop the Bedrock server cleanly, saving the world before shutdown to prevent data loss.

Instructions

Stop the server cleanly (it saves the world first).

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

Input Schema

NameRequiredDescriptionDefault

No arguments

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?

With no annotations supplied, the description must carry the behavioral burden. It usefully discloses the critical side effect that the world is saved first, so the operation is not data-destructive. It omits other relevant traits: permission requirements, whether connected clients are disconnected, whether the stop is immediate or graceful with a timeout, and whether a restart is needed.

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?

One short sentence with the key behavior front-loaded in parentheses; every word earns its place and there is no filler.

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 trivial zero-param stop operation with no output schema, the description covers what it does and the one crucial side effect (world save). It could be more complete by clarifying scope relative to 'ws_stop' and what happens to connected clients, but it is largely sufficient.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is no parameter semantics to explain. Baseline 4 applies; the description correctly implies no configuration options are needed.

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 ('Stop the server'), plus a qualifier ('cleanly'), so the agent knows exactly what the tool does. It does not, however, distinguish itself from the sibling 'ws_stop' (workspace stop), leaving ambiguity about whether 'server' here means the whole server or the current workspace.

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

Usage Guidelines2/5

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

There is no when-to-use guidance: no mention of when to prefer this over 'ws_stop', no note about prerequisites such as saving/backup already being done, and no guidance on confirming intent before shutting down. The parenthetical is a behavior note, not usage guidance.

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