Skip to main content
Glama

close_test_build

Destructive

Needs sign-in (connect this server with OAuth, or pass an API key as the Authorization: Bearer header). Ends a test build (branch) of an alpha game. On owner-governed games (owner or maintainers mode), the owner or an approver puts an open, playable test build in from the game page, including during testing. Community-governed games merge by vote. This tool also withdraws test builds: a builder may withdraw their own (outcome "closed"), which frees its slot for another open test build. The game's creator may also turn one down ("rejected") or withdraw it, and outcome "merged" records that a build they shipped with update_game folds it in (ship:true releases the branch's own build only when it is the creator's upload).

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": {
      "slug": "<slug>",
      "branch": "<branch>",
      "outcome": "<outcome>"
    },
    "name": "close_test_build"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNoWith ship: major or minor (default).
noteNoUp to 500 characters, shown to players: how it ended and why.
shipNoWith outcome merged: release the winning build itself as the next version (minor unless kind is major).
slugYes
branchYesThe branch id from alpha_board or open_branch.
winnerNoFor a merged choice: the key of the build that won.
outcomeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior4/5

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

Beyond the annotations, the description discloses that sign-in is required via OAuth or an Authorization: Bearer API key, explains owner/maintainer/community governance differences, and notes that closing as "closed" frees a slot for another open test build. These are valuable behavioral details for a destructive mutation tool, though the description remains dense and partly confusing.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a long, dense run-on that begins with authentication requirements before stating the tool's purpose, and it includes a sentence about opening test builds that does not clearly belong in a close tool. The content is not front-loaded or cleanly separated into purpose, permissions, and outcome semantics.

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 destructive, seven-parameter mutation tool with no output schema, the description covers authentication, permissions, outcomes, and one important side effect. It still omits return-value behavior and does not clearly contrast this tool with related close/open tools, leaving some gaps for correct 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?

With 71% schema description coverage, the schema already defines most parameters, but the description adds meaningful semantics for the otherwise bare outcome enum and clarifies that ship:true releases the branch's own build only when it is the creator's upload. It does not add much for note, slug, branch, or winner beyond what the schema already provides.

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 specific verb and resource: it "Ends a test build (branch) of an alpha game" and later says it "also withdraws test builds." That makes the core purpose clear, though it does not explicitly distinguish this from sibling tools such as close_branch or close_test_session, and the sentence about an owner or approver "puts an open, playable test build in" is confusingly about opening rather than closing.

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

Usage Guidelines3/5

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

The description gives useful guidance for choosing the outcome value: "closed" when a builder withdraws their own build, "rejected" when the creator turns one down, and "merged" when update_game folds a build in. However, it does not explicitly say when to call close_test_build versus close_branch, close_test_session, or open_test_build, so tool-selection guidance remains implied.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources