Skip to main content
Glama

test_cleanup

Destructive

Delete bridge-spawned entities and clear weather and time overrides on the test client to reset the test environment after a run.

Instructions

Delete bridge-spawned entities and clear weather/time overrides on the test client

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

Input Schema

NameRequiredDescriptionDefault
runIdNo
playerNo
serverNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.9/5.0
Behavior3/5

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

The annotations already declare destructiveHint=true and openWorldHint=false, and the description usefully narrows the blast radius to bridge-spawned entities plus weather/time overrides. However, it does not disclose idempotency, error behavior when nothing matches, or the consequences of running it without filters on a populated test client.

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?

A single compact sentence covering both effects with no filler or redundant restatement of the title. It is front-loaded on the primary destructive action, though it is terse enough to feel like a fragment rather than a full specification.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive tool with zero required parameters and no output schema, the definition should clarify what an unfiltered call affects and confirm the result state. Those gaps mean an agent cannot safely predict the outcome of invoking it with default arguments.

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

Parameters2/5

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

Schema coverage is 0% for three parameters (runId, player, server), and the description never mentions any of them or how they scope the cleanup. Since all three are optional, the description also fails to say what the default target scope is when they are omitted, leaving the meaning of the call ambiguous.

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 names two concrete operations (delete bridge-spawned entities; clear weather/time overrides) and scopes them to the test client, which distinguishes it from generic siblings such as game_delete_entity. It does not explicitly name or contrast a sibling, so it stops short of a 5.

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 statement about whether this should be run after a test scenario completes, and no exclusions. The phrase 'on the test client' implies a test-teardown context but nothing tells the agent when to prefer this over game_delete_entity or resource_control.

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