You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I encountered an error while trying to use the tool. This was the error: Unsupported data type.
Tool Search a PDF's content accepts these inputs: Search a PDF's content(query: 'string') - A tool that can be used to semantic search a query the my.pdf PDF's content. query: 'Mandatory query you want to use to search the PDF's content'
# Agent: Researcher...
## Thought: In order to ...
## Using tool: Search a PDF's content
## Tool Input:
"{\"query\": \"key skills and qualifications\"}"
As I cannot influence the format of what the agent sends to the tools, I'd expect the agent would send properly query=string. Could it be the config=... is messing up things?
Screenshots/Code snippets
The error is in the description above
Operating System
Windows 11
Python Version
3.12
crewAI Version
0.67.1
crewAI Tools Version
0.12.1
Virtual Environment
Poetry
Evidence
The error is in the description above
Possible Solution
None
Additional context
Same behaviour when I use the DOCXSearchTool, so there's either something I completely misunderstand, or worse.
The text was updated successfully, but these errors were encountered:
Description
I get this error:
Steps to Reproduce
The code I use is (fluff removed for clarity):
Expected behavior
As I cannot influence the format of what the agent sends to the tools, I'd expect the agent would send properly query=string. Could it be the config=... is messing up things?
Screenshots/Code snippets
The error is in the description above
Operating System
Windows 11
Python Version
3.12
crewAI Version
0.67.1
crewAI Tools Version
0.12.1
Virtual Environment
Poetry
Evidence
The error is in the description above
Possible Solution
None
Additional context
Same behaviour when I use the DOCXSearchTool, so there's either something I completely misunderstand, or worse.
The text was updated successfully, but these errors were encountered: