docs: note roadmap resources/prompts and no-SSE requirement

README.md

@@ -97,6 +97,22 @@ The `/mcp` endpoint supports:
 
 This is intended to work with OpenClaw’s MCP bridge and allow tool discovery + calling with request ids.
 
+## Roadmap note: what “more MCP compliant” could add
+
+In practice, your current server already covers the MCP tool surface used by
+OpenClaw (`initialize`, `tools/list`, `tools/call`).
+
+If you later want broader MCP-client compatibility, the next typical additions
+are:
+
+* **Resources** (`resources/list`, `resources/read`) for stable domain records
+  (e.g., plant/cycle summaries)
+* **Prompts** (`prompts/list`, `prompts/get`) for reusable instructions
+* **Optional eventing** (often via SSE depending on the client/transport), if
+  you later need push notifications instead of polling
+
+You do **not** need SSE to make a tool-based MCP server work for OpenClaw.
+
 ## Layering recommendation
 
 Keep ontology discovery in `virtuoso_mcp` so any specialized layer (garden, inventory, analytics, etc.) can reuse it. Domain modules should call these generic tools instead of re-implementing ontology probing logic.