jev-mcp-dispatcher
Zero general-purpose LLM calls — anywhere in this pipeline, not for picking the tool, not for reading a parameter's value out of a sentence, not for anything. This is a proof of concept for a different way to do MCP tool dispatch: given a MCP (Model Context Protocol) server — one whose tools take primitive-typed parameters — this script dynamically discovers its tool signatures at runtime and uses — 's System One reasoning model — to route a plain natural-language command to the correct tool and extract its arguments straight out of the sentence, using only Jev's typed primitives ( / ) instead of free-text generation. The dispatcher logic never hardcodes a specific tool name, parameter name, or parameter count. It is a claim that this works against an arbitrary MCP server unconditionally — see for exactly what the input text and the tool registry need to look like.