game-agent-harness
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| workspace-root | Yes | Absolute path to the workspace root. Passed to the MCP server as the --workspace-root argument. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_scenariosA | List scenario files allowed within this workspace. |
| run_scenarioA | Run one allowlisted scenario path relative to the scenarios directory. |
| soak_scenarioB | Repeat an allowlisted scenario within the server's hard run limit. |
| read_reportA | Read report.json from one direct child of the workspace artifacts directory. |
| run_visual_scenarioB | Run one allowlisted scenario containing VisualProbe steps. |
| read_visual_reportB | Read VisualProbe JSON reports from one direct artifact directory. |
| list_visual_artifactsB | List safe PNG files directly inside an artifact directory's visual folder. |
| read_visual_artifactB | Read one safe PNG as an MCP image content block. |
| compare_visual_runsC | Return the VisualProbe reports for two confined artifact directories. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 9 tools
Most tools are clearly distinct, but run_scenario/run_visual_scenario and read_report/read_visual_report could be confused without knowing scenario types or report nesting. Descriptions clarify the visual/VisualProbe specializations enough for an agent to choose.
All tools follow a consistent verb_noun snake_case pattern with an optional visual modifier, such as list_scenarios, run_visual_scenario, read_visual_artifact, and compare_visual_runs. There are no mixed conventions or inconsistent verb styles.
9 tools is well within the ideal range for a focused harness: scenario discovery/execution, report access, and visual artifact handling are each represented without obvious bloat. The set is appropriately scoped for its purpose.
Core workflows are covered: list/run/soak scenarios, read standard reports, and run/read/list/compare visual scenarios and artifacts. Minor gaps include no direct way to list artifact/report directories or inspect a scenario for VisualProbe steps before running, but these can often be worked around by convention.