Shadai provides five powerful tools for different use cases. This guide helps you choose the right tool for your needs.| Tool | Best For | Streaming | Memory |
|---|
| Query | Specific questions | ✅ | ✅ |
| Summarize | Document overview | ✅ | ✅ |
| Web Search | Current information | ✅ | ✅ |
| Engine | Multi-source analysis | ✅ | ✅ |
| Agent | Custom workflows | ✅ | ✅ |
Purpose: Ask specific questions about your documents.You have a specific question
Need information from documents
"What's the refund policy?"
"Who is the contract between?"
"What are the main findings?"
Best Practices:
✅ Be specific
✅ Use follow-up questions
✅ Enable memory for conversations❌ Don't ask extremely broad questions
❌ Don't query without ingesting documents firstPurpose: Get an executive summary of all documents in a session.Need overview before deep dive
Want to understand document scope
Presenting to stakeholders
Best Practices:
✅ Run after ingesting all documents
✅ Use as conversation starter
✅ Follow up with specific queries❌ Don't use for detailed analysis
❌ Don't use with no documentsPurpose: Find current information from the internet.Verifying recent information
"Current stock price of Tesla"
"Latest COVID-19 guidelines"
"Recent AI breakthroughs"
Best Practices:
✅ Use for time-sensitive queries
✅ Be specific with dates
✅ Combine with document queries❌ Don't use for historical data
❌ Don't use for private informationPurpose: Orchestrate multiple tools for comprehensive analysis.Need multi-source insights
Comparing documents with trends
Combines document knowledge
"How do our policies compare to competitors?"
"Analyze documents and check current market trends"
"What's missing from our strategy based on industry best practices?"
Best Practices:
✅ Use for complex questions
✅ Enable relevant capabilities
✅ Let it synthesize information❌ Don't use for simple queries
❌ Don't enable all features unnecessarilyPurpose: Execute custom workflows with your own tools.Need custom functionality
Integrating with your systems
Automating complex workflows
Building specialized applications
1.
Plans: Determines which tools to use
2.
Executes: Runs tools with inferred arguments
3.
Synthesizes: Combines results into answer
Database queries + report generation
API calls + data analysis
Best Practices:
✅ Provide clear tool descriptions
✅ Use type hints
✅ Keep tools focused❌ Don't create overlapping tools
❌ Don't make tools too complexQuery vs. Summarize#
Want to cite specific sections
Query vs. Web Search#
Information in your documents
Need private/internal data
Query vs. Engine#
Engine vs. Agent#
Standard capabilities sufficient
Pattern 1: Overview → Deep Dive#
Pattern 2: Documents + Current Data#
Pattern 3: Custom Workflow#
Do you need custom functionality?
├─ Yes → Agent
└─ No ↓
Do you need current/live data?
├─ Yes → Web Search
└─ No ↓
Do you need multi-source analysis?
├─ Yes → Engine
└─ No ↓
Do you need overview of documents?
├─ Yes → Summarize
└─ No → Query
Common Patterns#
Research Workflow#
Due Diligence Workflow#
Market Analysis Workflow#
Fast Queries#
Complex Analysis#
Batch Processing#
Next Steps#
Remember: Start simple with Query, add complexity as needed! Modified at 2025-10-17 17:47:10