Skip to main content
Glama
Sign In
Minecraft Structure Lab

Minecraft Structure Lab

by ewitulsk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

lab_status

Check world identity, limits, connection readiness, and active job progress to confirm the Minecraft Structure Lab environment is ready for structure generation and placement.

Instructions

Get world identity, limits, connection readiness, and active job progress.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.5/5.0
Behavior3/5

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

There are no annotations, so the description carries the burden of behavioral disclosure. It communicates that the tool returns status information and implicitly indicates a read operation via 'Get', but it does not state whether any state is changed, whether authentication or a live connection is required, or how the data is structured beyond broad categories.

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?

The description is a single, front-loaded sentence that names the operation and enumerates the main output categories without any filler. Every word contributes to understanding the tool's purpose.

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?

Given that the tool takes no parameters and has no output schema, the description covers the essential return categories: identity, limits, readiness, and job progress. It is slightly incomplete in not clarifying how this relates to job_status, but for a zero-input status tool it provides enough context for basic invocation.

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 has zero parameters and schema description coverage is 100%, so there is nothing meaningful for the description to add about inputs. The description appropriately focuses on what the tool returns rather than parameter details.

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 clear verb ('Get') and a specific resource ('world identity, limits, connection readiness, and active job progress'). It is more than a tautology and conveys the tool's scope, but it does not differentiate lab_status from the sibling tool job_status, which also likely reports job progress.

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?

No guidance is given about when to use lab_status versus alternatives such as job_status. The description implies this is a general status/readiness check, but it never states when this tool should be chosen over a sibling or what conditions favor another tool.

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