What Tool Filtering Enables
Tool filtering allows you to:- Select tools by provider (e.g., Salesforce, Gmail, Workday)
- Filter by specific actions (create, read, update, delete)
- Combine multiple patterns for precise selection
- Exclude specific tools or patterns
Basic Filtering Patterns
By Provider
salesforce_*- Salesforce CRMgmail_*- Gmail & Calendarworkday_*- Workday HCM
By Action
*_create_*- All create operations*_list_*- All list operations*_get_*- All get operations
Combined Patterns
hibob_list_*- HiBob list operations onlyworkday_update_*- Workday update operations only
Use Cases
- Cross-Domain Agents: Let assistants reliably interact with whatever tools (CRMs, ERPs, comms suites, etc.) are available for the current account
- Operation-Focused Tools: Create specialized agents for read-only or write operations
- Custom Tool Sets: Combine multiple patterns for precise control
- Performance Optimization: Load only the tools your agent actually needs
Python Naming Conventions
Tool Name Structure
StackOne tools follow the pattern:provider_operation_entity
Common Patterns
By Connector (using their individual keys, eg.workday, netsuite, gmail salesforce and hundreds more)
hibob_*- HiBobbamboohr_*- BambooHRworkday_*- Workdaygreenhouse_*- Greenhouse
*_list_*- Get multiple records*_get_*- Get single record*_create_*- Create new record*_update_*- Update existing record
*employee*- Employee operations*candidate*- Candidate operations*contact*- Contact operations
Examples
For complete implementation examples, see:- Python Examples on GitHub
- Meta Tools - Dynamic tool discovery
- LangChain Integration - Use filtered tools