Skip to main content
Glama

Status and settings

status
Read-onlyIdempotent

Shows safety settings, active test server details, Java installation, undo history, and world backups so you can confirm the environment before building or testing maps.

Instructions

Call this first. Shows the person's safety settings (config file, allowed server folders, size limits, file and mod rules), the active test server (version, folder, running or not, ports, EULA), Java found on this computer, the undo history and world backups.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description's job is to say what is surfaced, and it does so in detail — config paths, folder allowlists, size limits, EULA status, Java detection, backup and undo state. It does not describe output shape or size, but there is no output schema, so the enumeration carries most of that burden acceptably.

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?

The imperative 'Call this first' is front-loaded, followed by one dense but purposeful enumeration; every listed item is something an agent would otherwise have to discover. It is a long sentence, but nothing reads as 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 zero-parameter, annotation-covered read tool with no output schema, the main missing piece is return structure, and the description lists the returned categories thoroughly. Slightly more on how the settings relate to other tools (e.g., where the allowed folders come from) would close the remaining gap.

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, which is the baseline-4 case; there is no parameter meaning to add. The description correctly implies no arguments are needed by framing it as a plain status report.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description enumerates exactly what is returned: safety settings (config file, allowed folders, size limits, rules), the active test server (version, folder, running state, ports, EULA), detected Java, undo history and backups. That scope is precise enough to separate it from siblings such as server_logs or plan_setup without opening any schema.

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

Usage Guidelines4/5

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

'Call this first' gives an explicit ordering directive that most tools lack, so the agent knows to invoke it before acting. It stops short of saying when to re-call it (e.g., after config changes) or naming an alternative for narrower queries, but the primary guidance is clear.

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