Can't we just iteratively inspect the network traces then? We don't need to consume the whole 2mb of data, maybe just dump the network trace and use jq to get the fields to keep the context minimal. I haven't added this in https://news.ycombinator.com/item?id=47207790 , but I feel it would be a good addition. Then prompt it with instructions to gradually discover the necessary data.

But then I wonder, where the balance is between a bunch of small tool calls, vs one larger one.

I recall some recent discussion here on hn on big data analysis

> That doesn't solve the issue here because the amount of data in the browser state dwarfs the MCP overhead.

The problem with MCP is that you are paying the price in token usage, even if you are not using the MCP server. Why would anybody want that?

And no, the tool search function recently introduced by Anthropic does not completely solve this problem.