Skip to main content
Glama

studio_done

Needs sign-in (connect this server with OAuth, or pass an API key as the Authorization: Bearer header). Finish your own game's studio request with your own complete private staged upload. The owner can Try it and press Ship; this tool never ships.

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": {
      "request": "<request>",
      "uploadId": "<uploadId>",
      "note": "<note>"
    },
    "name": "studio_done"
  }
}

Input Schema

NameRequiredDescriptionDefault
noteYes
requestYesRequest id from studio_wait.
uploadIdYesYour own complete private staged upload.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

Annotations declare a non-destructive, non-read-only, non-idempotent, closed-world mutation. The description adds genuinely new context beyond that: an authentication requirement (OAuth connection or bearer API key) and the downstream behavior that the owner must Try and press Ship, with this tool never shipping. It does not discuss irreversibility or what happens to an incomplete upload.

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?

Three compact sentences with no filler, and the critical "this tool never ships" limit is stated plainly. The auth boilerplate leads the description rather than the tool's purpose, which is a mild front-loading flaw.

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 three-required-parameter mutation with no output schema, the description covers the auth prerequisite, the ownership precondition, and the downstream handoff to the owner. It leaves unclear what a successful call returns or produces, and gives no meaning for the mandatory note parameter, so it is adequate but incomplete.

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?

Schema description coverage is 67%: request and uploadId are annotated, but note is only bounded by length with no described meaning, and the description does not explain it either. The description reinforces the uploadId constraint ("your own complete private staged upload") but adds no syntax or format detail.

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?

Names a specific verb+resource: "Finish your own game's studio request" with a staged upload, and clarifies the boundary with shipping ("this tool never ships"), which separates it from publish-oriented siblings. The verb "finish" is slightly abstract about what state change actually occurs, keeping it 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 Guidelines3/5

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

Preconditions are stated (you must own the game, and you must supply your own complete private staged upload) and the "never ships" clause implicitly routes shipping to another tool. However, no sibling is named explicitly and there is no guidance on when to use this versus studio_fail or studio_progress, so usage is inferred rather than directed.

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