Skip to main content
Glama

studio_wait

Needs sign-in (connect this server with OAuth, or pass an API key as the Authorization: Bearer header). Wait up to 45 seconds for the oldest queued change to your own game (including a remix). Claims one request for 5 minutes (studio_progress extends it to 30) and returns its DATA block and a 15-minute build.download pass. Download, change, test and stage that build, then call studio_done. Only the owner presses Ship on the site. Call again before progress to re-deliver the same pick with a fresh pass. At timeout returns {waiting:true}; call again.

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

Input Schema

NameRequiredDescriptionDefault
gameNoOptional slug of your own game.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior5/5

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

Beyond the annotations, it discloses auth requirements (OAuth connection or Bearer API key), the 5-minute request claim that studio_progress extends to 30, the 15-minute build.download pass returned with the pick, and the exact timeout return shape. The lease/claim semantics explain why readOnlyHint=false rather than contradicting it.

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?

Front-loaded with the core action and timeout, then layered with auth, claim duration, and the follow-on workflow; nearly every clause carries operational information. Some sentences are tightly packed (the re-delivery and fresh-pass sentence) and would read faster if split.

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 blocking wait with side effects and no output schema, the definition covers auth, duration, lease behavior, return payload, and next steps, which is close to everything an agent needs. Minor gaps remain around behavior when no queued change exists and how the slug default is resolved.

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?

Only one optional parameter and schema description coverage is 100%, so the schema already carries the meaning of the game slug. The description reinforces the owner-scoping ('your own game, including a remix') but never says what happens when the slug is omitted, so it adds little beyond the structured field.

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?

States a specific verb and resource with scope: wait up to 45 seconds for the oldest queued change to your own game, including remixes. The owner-scoping and timeout make it distinguishable from progress/done-style siblings without opening the 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?

Gives a clear operating loop: download, change, test, stage, then call studio_done, with an explicit retry rule (call again before progress to re-deliver the same pick) and timeout handling (call again on {waiting:true}). It names studio_progress and studio_done as adjacent steps but never says when to prefer a different wait primitive or when this tool should not be used.

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