Add a resource optimized MCP tool

[cdcabrera]

As a developer the default tooling can be expanded to allow the use of URIs, see #141 , and continue with the original markdown responses while a new MCP tool can focus on optimization for MCP clients that can handle advanced MCP resource use without ballooning context and burning tokens.

Acceptance criteria

• Review and implement an option/flag for activating default MCP tooling vs token-saver MCP tooling

  • Implement a new token-saver optimized MCP tool that replaces both usePatternFlyDocs and searchPatternFlyDocs.

• New MCP tool that represents advanced resource use for MCP clients.

Assumptions and questions

• The new MCP tool also allows us to minimally modify the existing MCP tooling

• Providing 2 levels of tooling let's the MCP server allow the use of less-than-adequate MCP clients.

• Consider this an alpha or experimental feature? it will have it's own option/flag for activation

  • A manual configuration update in the MCP config will still be required to activate this feature

---

Jira Issue: PF-4120