Comments

Hacker News

The "book as an MCP server" framing is the part that interests me. I run a small MCP server myself (semantic search over government documents), and the thing I keep noticing is that the interface changes what people ask — nobody asks a PDF "what should I do in my situation," but they'll ask a tool that. Shipping specialized tools (draft_decision_doc etc.) over one generic ask_the_book tool also seems like the right call — clearer intent per call, less context spent on tool descriptions. I noticed you went with keyword search over a summary corpus plus citations rather than embedding the full text — curious whether that was a licensing decision (keeping the manuscript out of the package) or you found summaries-with-citations just work better for this kind of prescriptive content than semantic retrieval over the full prose?

by suzuridev

So nice to see a new library written in JavaScript instead of TypeScript.

by mjhea0

How does `triage_sync_vs_async` handle team-specific norms — fixed rubric, or does it lean on the model's judgment from context?

by taevirus

This has been very inspiring for a MCP design novice like me; I can now implement executable tools, reference knowledge, and user workflows in my own MCP.

by znhskzj

The readme is so thick with breathless LLMisms that it makes one wonder what is the point. That's a bit sad because the book's website and blog appear interesting, the author can write. Still: shall I spend 10 bucks by buying and reading the book, or by consuming tokens on LLMs that read it?

by polotics

Join the discussion

Write your take first — we'll ask for email only when you're ready to publish.

  • Hacker News
  • The "book as an MCP server" framing is the part that interests me. I run a small MCP server myself (semantic search over government documents), and the thing I keep noticing is that the interface changes what people ask — nobody asks a PDF "what should I do in my situation," but they'll ask a tool that. Shipping specialized tools (draft_decision_doc etc.) over one generic ask_the_book tool also seems like the right call — clearer intent per call, less context spent on tool descriptions. I noticed you went with keyword search over a summary corpus plus citations rather than embedding the full text — curious whether that was a licensing decision (keeping the manuscript out of the package) or you found summaries-with-citations just work better for this kind of prescriptive content than semantic retrieval over the full prose?
  • So nice to see a new library written in JavaScript instead of TypeScript.
  • How does `triage_sync_vs_async` handle team-specific norms — fixed rubric, or does it lean on the model's judgment from context?
  • This has been very inspiring for a MCP design novice like me; I can now implement executable tools, reference knowledge, and user workflows in my own MCP.
  • The readme is so thick with breathless LLMisms that it makes one wonder what is the point. That's a bit sad because the book's website and blog appear interesting, the author can write. Still: shall I spend 10 bucks by buying and reading the book, or by consuming tokens on LLMs that read it?