Value Statement

ACM Search server created in  ACM-23306 exposes tools which require SQL to be passed on arguments. Agents with help of LLM consume this MCP. It places lesser burden on these if they can query a tool by just passing simple parameters. Say we have a find-resource tool, and we use it to find pod count, in namespace foo, in cluster bar - find-resource(kind=pod, ns=foo, cluster=bar, data=count) etc. We need to add such kind of a tool as a starter.

Background - 

Writing SQL calls - or specially recovering from failed SQL calls requires the Agents to be of a certain level of sophistication to be able to handle this. We have seen this - claude code can use the Search MCP well, but OLS has struggled. With claude code - adding some prompts helps reduce token consumption, but it can work with very little prompts. 

Definition of Done for Engineering Story Owner (Checklist)

• The MCP Server can be deployed on a Hub cluster and queried from OLS as well as claude code
• Code is checked into a repo
• The minimal prompt required for OLS has been developed as well.

Development Complete

• The code is complete.
• Functionality is working.
• Any required downstream Docker file changes are made.

Tests Automated

• [ ] Unit/function tests have been automated and incorporated into the
  build.
• [ ] 100% automated unit/function test coverage for new or changed APIs.

Secure Design

• [ ] Security has been assessed and incorporated into your threat model.

Multidisciplinary Teams Readiness

• [ ] Create an informative documentation issue using the [Customer
  Portal_doc_issue template](
  https://github.com/stolostron/backlog/issues/new?assignees=&labels=squad%3Adoc&template=doc_issue.md&title=),
  and ensure doc acceptance criteria is met. Link the development issue to
  the doc issue.
• [ ] Provide input to the QE team, and ensure QE acceptance criteria
  (established between story owner and QE focal) are met.

Support Readiness

• [ ] The must-gather script has been updated.