Jev enum tool selection picks a complete candidate call for a task. Our inventory contains an argument-free status inspection and two versions of list_items: kind open or kind closed. Selecting List closed items therefore identifies both the tool and its permitted argument. The model never has to invent an object or guess another enum value.
A tool description and a parameter schema answer different questions. The description explains what a tool does. The schema constrains the shape of its arguments. A perfectly shaped list_items call can still serve the wrong task, such as returning open items when the user asked for resolved ones. This exercise puts the semantic choice after a small inventory of complete local candidates.
The workflow came from an API-collected X discussion of deterministic schema checks before Jev tool selection. We also read the maintainer's WebMCP extension example, which maps enumerable inputs into typed questions. Our demo supplies three fixed calls rather than inspecting a live browser registry. It does not implement the extension, enumerate arbitrary JSON Schema or claim support for every parameter type.