Need help to get review PR of IBM Db2 search tool?

Hey everyone,

What would be the best way to reach the maintainers/reviewers for review on the PR?
Discord/community/forum suggestions would be really helpful.

I’ve been working on adding an IBM Db2 Vector Search Tool integration for CrewAI tools to enable semantic/vector similarity search workflows using IBM Db2 native vector capabilities.

The implementation is currently aligned with the existing CrewAI vector search tool patterns and follows a similar structure to tools like the Qdrant Vector Search Tool.

Current features include:

  • vector similarity search
  • configurable distance metrics
  • configurable embedding model support
  • standardized JSON retrieval responses
  • validation and safer query handling
  • runtime dependency loading

I’ve also completed end-to-end local testing for:

  • IBM Db2 connection flow
  • embedding generation
  • vector similarity search execution
  • retrieval response handling

Issue:

PR:

Would appreciate feedback/review from the community.

Thanks!

Hi everyone,

I wanted to follow up on this thread regarding our IBM Db2 Vector Search Tool integration for CrewAI.

The implementation is still actively maintained by our team, and we’re very interested in contributing it to the CrewAI ecosystem.

For reference:

We’re mainly looking for guidance on the review process:

  • Is there a maintainer currently responsible for reviewing new crewai-tools integrations?
  • Are there any additional requirements or contribution guidelines we should follow before the PR can be reviewed?
  • If this isn’t the right place, could someone point us to the appropriate maintainer or team?

We’re committed to maintaining this integration long-term and are happy to make any requested changes, add tests, improve documentation, or align the implementation with CrewAI’s expectations.

We’d really appreciate any guidance from the CrewAI team or the community.

Thank you!

Pawan Thakur
Software Engineer, IBM Db2

Nice contribution! Since the PR already looks well documented and you’ve completed local testing, I’d give the maintainers a little time before trying to escalate it. In many open-source projects, reviewers prioritize based on availability, so a polite follow-up on the PR after a reasonable interval is usually more effective than repeated pings. If there’s an active Discord or GitHub Discussions channel, posting a brief summary there with a link to the PR can also help increase visibility without feeling intrusive. Hopefully someone from the team can take a look soon.

Hi @Matthewjon, we’re actually looking for a way to access or find the usage telemetry for the IBM Db2 Search Tool we contributed to CrewAI. Do you know if there’s any way to get this usage information?