Steamworks Release Assistant

validate

Read-only

Check your Steam store configuration against Valve's rules to find compliance issues and failing gates before release. No files are modified.

Instructions

Review what is in steamworks.yaml (and the translations) without changing it.

section: "store" (Valve's rules in every language, the rubric, questions for you to judge), "achievements", "localization" or "all" (adds every failing gate rule). For store text, judge the returned questions and call again with llm_judgements=[{rule_id, field, outcome: pass|warn|fail, note}]; deterministic and judged results are reported separately. To propose a fix, save a new version with save_draft(strategy="revision").

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": {
      "path": "<path>"
    },
    "name": "validate"
  }
}

Input Schema

Name	Required	Default
`path`	Yes
`section`	No	all
`llm_judgements`	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/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, and the description reinforces this with 'without changing it'. It adds genuinely useful behavior beyond the annotation: the two-phase judge-then-resubmit flow with llm_judgements, and that deterministic and judged results are reported separately.

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?

The lead sentence is front-loaded and every subsequent clause (sections, workflow, fix path) earns its place. The inline 'section:' formatting and leading whitespace are slightly rough, but the content is dense and purposeful rather than padded.

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?

An output schema exists, so return values need no explanation, and the description covers the section taxonomy, the interactive judgement loop, and the fix path. For a three-parameter tool the only real omission is documentation of the 'path' argument.

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 0% schema description coverage the description must carry the load, and it does well for two of three params: it enumerates the section values and spells out the llm_judgements object shape ({rule_id, field, outcome, note}) with the pass|warn|fail outcome domain. The required 'path' parameter is left entirely unexplained, a minor remaining gap.

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 gives a specific verb+resource: it reviews/validates the contents of steamworks.yaml (and translations) without modifying it. The 'without changing it' clause usefully distinguishes it from save_draft, though it doesn't explicitly contrast with other diagnostic siblings like gap_report or scan_project.

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?

It clearly states the use case (review before changing) and enumerates the section choices ('store', 'achievements', 'localization', 'all'), then describes the two-phase workflow for store text. It also points to save_draft(strategy='revision') for fixes, giving a clear alternative, but stops short of explicit when-not-to-use guidance.

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