Andrew Fribush

fig. 2.18.3: a lazy session’s context on the 200K window as the reader loads domains through load_modules

fig. 2.18.3 · a lazy session’s context on the 200K window as the reader loads domains through load_modules.
LAZY START: 1,564 TOKENS FOR 7 TOOLS; EAGER: 85,530ACCENT: A LAZY SESSION’S TOKENS ON A 200K WINDOW, 7 DISCOVERY TOOLS THEN ASEGMENT PER MODULE; GREY: THE SAME TOOLS AS NAMES.050K100K150K200K · THE WINDOWEAGER START · 369 TOOLS · 85,5301,564 TOKENS · 0.78%20 TOKENS AS NAMES ONLYLOADED: 7 DISCOVERY TOOLS (RESOLVE_ENTITY, RESOLVE_PERSON, RESOLVE_PLACE,FIND_TOOLS, LOAD_MODULES, CLEAR_CACHE, CODE_MODE)COUNT IS TOOLS:ECONOMY 59FINANCE 60HEALTH 81LEGISLATION 101SPENDING 86SAFETY 65ENVIRONMENT 36HOUSING 22EDUCATION 20INTERNATIONAL 23JUSTICE 17TRANSPORTATION 16ENERGY 8AGRICULTURE 7ALL 45 MODULES

Each segment is the measured tokens of that module’s tool definitions (gpt-tokenizer o200k_base over name, description and input schema), as load_modules registers them; a module in two domains counts once, as the server resolves it. Loading everything holds 85,888 tokens: load_modules itself stays in the list, which an eager start at this commit leaves out.

source: fedpipe 413372f, tools/list over stdio in --eager mode mapped to modules by dist/apis/*/index.js; tokens by gpt-tokenizer o200k_base per module · loadModules.data.ts

View in context: Lazy tool loading over MCP → · All figures

Andrew Fribush, software and computer engineer in Austin. I build consequential systems where software meets institutions: finance, healthcare, commerce, government data, and the mechanisms that govern AI agents. Taking new engagements: hello@andrewfribush.com.