Skip to main content
Glama

mc_server_status

Read-onlyIdempotent

Checks the online status of a Minecraft Java or Bedrock server using its address, so you can verify availability before connecting.

Instructions

Check the status of a Minecraft server (Java or Bedrock).

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": {
      "address": "<address>"
    },
    "name": "mc_server_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressYesServer address (e.g. mc.hypixel.net)
editionNojava or bedrock (default java)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.11

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety and network-touching profile is covered structurally. The description adds the useful detail that both Java and Bedrock servers are supported, but says nothing about behavior on an offline/unreachable server, timeouts, or whether failures return an error or a status payload.

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 front-loaded sentence with zero filler; nothing is redundant. Its brevity is efficient but leaves the definition thin, which is captured in the other dimensions rather than here.

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 two-parameter read-only tool with full schema coverage and annotations, the core is adequate. However, with no output schema, the description gives no hint of what 'status' includes (online state, player count, version, latency) or how an unreachable host is reported, leaving the return shape entirely unspecified.

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 100%: 'address' has an example (mc.hypixel.net) and 'edition' documents java/bedrock with a default. The description's '(Java or Bedrock)' merely echoes the edition parameter, adding no format or edge-case guidance beyond the schema.

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 ('Check the status of a Minecraft server') and adds scope with '(Java or Bedrock)', which tells an agent both editions are handled. It doesn't differentiate from similar lookups in the sibling list (isup_check, uptimerobot_get_monitors), but the domain is distinctive enough to stand alone.

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 guidance on when to use this tool versus alternatives such as isup_check or uptimerobot_get_monitors, and no stated prerequisites or exclusions. Usage is only inferable from the name and one-line purpose.

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

Deploy Server

Other Tools