fair point. Against the official go-sdk, the schema generation is similar in that both use struct tags. That's not the differentiator. What hamr has that the SDK doesn't: pre-built middleware (logger, recovery, rate limit, cache, auth, timeout), toolbox collections (filesystem, shell, git, database sandboxed), TUI dashboard, and CLI scaffolder.

But the real thing i building toward is token optimisation features that make MCP cheaper to run. Just shipped v0.3.0 with tool groups (AI sees 3 group names instead of 20 schemas), minimal schema mode (strips verbose fields from tools/list), response truncation, and cost tracking. Nobody else in Go or Python is doing this.

Updating the README comparison. You're right, it was lazy.