How AI Uses WhatIs for Real-Time Lookups
WhatIs is not just for you to browse in a browser. Vex uses it constantly behind the scenes. In fact, WhatIs is one of the key tools that makes Vex so reliable and accurate. Whenever Vex needs to look up a command, check parameter formats, or recover from an error, WhatIs provides the answers instantly — all running locally on your machine.
Way 1: Direct lookups with the what_is tool
Vex can call what_is("topic") at any time to look up commands, parameters, and examples. For instance, before using workspace.diagnose for the first time in a session, Vex calls what_is("workspace.diagnose") and receives the full parameter list, description, and working examples. This is part of the pre-command knowledge check protocol — Vex verifies how a command works before calling it, which prevents the frustrating trial-and-error loops you see with other AI tools.
Way 2: MCP Resource for context injection
The full command reference and AI guidance is available as an MCP resource at gamecatalyst://guidance. Vex can read this resource to load comprehensive guidance into its working context, including identity information, personality traits, all 17 behavioral laws, and command documentation organized by category. This is especially useful at the start of a session when Vex needs the complete picture.
Way 3: Automatic self-healing on errors
This is the most powerful integration. When Vex uses a command incorrectly — say, calling component.set without the required component parameter — GameCatalyst automatically queries WhatIs for the correct usage and appends it directly to the error response. Vex receives something like:
“Missing required parameter ‘component’. component.set requires: target (string), component (string), property (string), value (any). Example: component.set target=’Player’ component=’Rigidbody’ property=’mass’ value=2.”
Vex reads this guidance, understands exactly what went wrong, and corrects the call on the very next attempt. No user intervention needed. No back-and-forth troubleshooting.
Why this matters for you:
You rarely need to correct Vex manually. When Vex encounters an unfamiliar command, it checks WhatIs first. When Vex makes a mistake, WhatIs provides the fix automatically. This self-correcting loop means fewer interruptions, fewer error messages cluttering your conversation, and faster, more accurate results. The documentation works for both of you — you browse it in the browser, and Vex queries it through the API. It is one system serving two audiences seamlessly.
