F
licenseNot graded
qualityB
maintenanceEnables a cooperative museum-heist escape room where AI agents and human players share real-time state, coordinate actions, and solve puzzles together through MCP tools.
-
toolquest
by sysu19351015
Related Servers
Alternatives to toolquest
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityBmaintenanceEnables reproducible evaluation of AI coding agents by exposing repository inspection, code editing, test running, and deterministic verification through MCP tools.-
- AlicenseAqualityCmaintenanceAn MCP server that turns any LLM into an escape room player.10MIT
- AlicenseNot gradedqualityBmaintenanceProvides external AI agents with reliable, observable tools to inspect, navigate, and act in a Minecraft world, enabling autonomous playthroughs such as beating the game.MIT
- FlicenseNot gradedqualityAmaintenanceEnables LLMs to control a Minecraft bot and interact with the game through MCP tools, including observing state, moving, mining, crafting, building, farming, managing inventory, enchanting, and chatting in-game.1-
- AlicenseNot gradedqualityCmaintenanceEnables reproducible evaluation of AI agents on multi-source evidence investigation tasks, providing Docker-based scenarios, MCP tools, and automated scoring for payout reconciliation, performance-claim verification, and incident reconstruction.MIT
TDQS
A4.1/5.0
Scored across 10 tools
Disambiguation5/5
Each tool has a clearly distinct role: run lifecycle tools (start/get/replay/export) are separate from in-room inspection tools (look/inspect) and state-changing actions (move/use/submit). There is no meaningful overlap between any pair of tools.
Naming Consistency4/5
Most tools follow a clear verb_noun pattern such as list_rooms, start_run, get_run, and export_report. The in-room actions use single verbs like look, inspect, move, use, and submit, which is a minor deviation but still predictable and readable.
Tool Count5/5
10 tools is well-scoped for an escape-room benchmark server. Each tool covers a necessary part of discovery, run lifecycle, in-room interaction, and reporting without redundancy.
Completeness4/5
The toolset covers the main workflow: discover rooms, start a run, observe state, act in rooms, submit answers, resume runs, replay, and export reports. Minor gaps like no run-listing or explicit run-abandon tool are not required for the core benchmark use case.
Maintenance
ActivityMaintained
ResponsivenessNo issues