Skip to main content
Glama
wfbcargo

spawn-mcp

by wfbcargo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

spawn_audit_ui

Scan the Spawn project's code for the 21 Interface In Game UI surfaces and report each as found or missing, so you know which surfaces still need building.

Instructions

Locally count which of the 21 Interface In Game UI surfaces this Spawn game project has: no browser, no live room, no push, no credentials. This is a text scan, not a look at the screen, so it can only tell you found or missing, never whether a surface is actually built or styled — a missing verdict means go build that surface: load the skills the report names with spawn_skill, then re-run this tool to confirm it. found means only that the surface's name turned up in a path or identifier; it is not a verdict on completeness or appearance, and spawn_play_screenshot is the only authority on how a surface actually looks. Reads audit/ui.json's expect list by default, falling back to a 6-surface baseline (main-menu, in-game, settings, overlay, game-over, loading) when the file is absent; pass expect to try a different surface set without writing the file. Every finding also carries an interfaceingame.com reference link for a human to open — this tool never fetches that site itself. An unknown surface id, in expect here or in audit/ui.json's expect/ignore, fails with the full 21-slug menu instead of silently scoring it as missing.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
genreNoInterface In Game genre to add to every reference link for this call, overriding audit/ui.json's `genre`.
themeNoInterface In Game theme to add to every reference link for this call, overriding audit/ui.json's `theme`.
expectNoSurface ids to check instead of audit/ui.json's `expect` (or the 6-surface baseline, if neither exists) — try a set without writing the file first. An unknown id fails with the full 21-slug menu.
projectDirNoAbsolute path to the Spawn game project. Defaults to SPAWN_PROJECT_DIR or cwd.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.0.0

TDQS

A4.8/5.0
Behavior5/5

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

No annotations exist, so the description carries the full burden and does so richly: no browser/live room/push/credentials needed, text-scan-only semantics, found/missing limits, default expect list from audit/ui.json with a 6-surface fallback, and the failure mode for unknown surface ids.

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?

Purpose and the key caveat (text scan, cannot judge appearance) are front-loaded, and each sentence covers a distinct behavior. It is dense and somewhat long, but the complexity justifies most of the length.

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 no output schema and no annotations, the description compensates by explaining return verdicts (found/missing), the reference link it attaches, and the failure mode. An agent has everything needed to call it correctly and interpret results.

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?

Schema coverage is already 100%, so the baseline is 3, but the description adds real meaning: the default source and fallback for expect, the ability to try a set without writing the file, and the error behavior on unknown ids. It adds less for genre/theme beyond what the schema already states.

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: locally count which of the 21 Interface In Game UI surfaces a Spawn game project has. It explicitly distinguishes itself from siblings by naming spawn_play_screenshot as the authority on appearance and spawn_skill as the follow-up action, so an agent can route without opening a schema.

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

Usage Guidelines5/5

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

Gives concrete when-to-use and when-not-to-use guidance: missing means go build the surface, load skills with spawn_skill then re-run; for appearance use spawn_play_screenshot instead. It also spells out that a found verdict is not a completeness verdict, leaving nothing to inference.

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

Deploy Server

Other Tools