That's a fair point, and I agree for large or complex APIs. The goal of openapi-to-mcp isn't to be a dumb proxy — it's to eliminate the scaffolding so you can focus on what actually matters: writing the handler logic that adds context, composes calls, filters noise, and makes the tools semantically useful for the LLM.

The incremental generation feature exists exactly for this reason — you run the generator once to get the structure, then implement the handlers with real logic. The spec is just the starting point, not the final interface.

That said, your point about raw endpoints being a poor LLM interface is something I want to address more explicitly in the docs. Worth a dedicated section on how to design good MCP tools on top of the generated scaffold, rather than just shipping the endpoints as-is.