Steamworks Release Assistant

status

Read-only

Check release progress across your games, or pass a game folder to see each Steamworks release step, store copy and translations, and the next action to take.

Instructions

Start here. Without path: the games in the workspace (tracked ones and engine projects not tracked yet). With path: how far the game is on each release step, its values (approved, drafts, to fill, done in Steamworks), store text and translations, and the one thing to do next.

Args: path: The game's folder (the one with steamworks.yaml), relative to the workspace root.

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

Name	Required	Description	Default
`path`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.1Oct 3, 2026

TDQS

A4.4/5.0

Behavior4/5

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

The annotation already declares this is a read-only operation, so the safety burden is low. The description adds useful behavioral context by explaining what the tool reports in each mode, including statuses, translations, and a recommended next action.

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

Conciseness5/5

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

The description is brief and front-loaded with the most important routing information. Every sentence contributes to understanding the two modes and the path argument.

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

Completeness5/5

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

With only one optional parameter, a read-only annotation, and an output schema, the description supplies everything an agent needs to decide when and how to call the tool. It does not need to explain return values because an output schema already exists.

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

Parameters5/5

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

Schema description coverage is 0%, so the description must carry parameter meaning. It does so precisely: `path` is defined as the game folder containing steamworks.yaml, relative to the workspace root, and the omitted-path behavior is fully described.

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 clearly states the tool's two modes: without `path` it lists games in the workspace, with `path` it reports release progress, values, store text/translations, and the next action. This goes beyond restating the name, but it does not explicitly distinguish itself from sibling tools such as `compare_games` or `launch_watch`.

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?

The opening 'Start here' gives clear entry-point guidance, and the path/no-path distinction tells the agent exactly when to use each mode. However, it does not name alternative tools or describe when not to use this one.

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