Quick Start
How It Works
| Stage | Description | Example |
|---|---|---|
| Registration | Tools register with full names | web_search, send_twilio_sms, gmail_send |
| Filtering | HERMES_ONLY_TOOLS whitelist applied | "web_search,gmail_send" |
| Selection | Only whitelisted tools available | web_search ✅, send_twilio_sms ❌, gmail_send ✅ |
Configuration Options
Environment Variable Format
Discovery Commands
Check tool filtering status:Common Patterns
Pattern 1: Environment-Specific Filtering
Pattern 2: Capability-Based Filtering
Pattern 3: Incremental Rollout
Best Practices
Use Exact Tool Names
Use Exact Tool Names
HERMES_ONLY_TOOLS requires exact spelling matching registration names. Typos silently drop tools from availability.
Set Before Agent Creation
Set Before Agent Creation
Environment variables must be set before creating agents. Runtime changes don’t affect existing agents.
Monitor Tool Availability
Monitor Tool Availability
Log or validate that required tools are available after filtering to catch configuration issues.
Use for Production Deployments
Use for Production Deployments
HERMES_ONLY_TOOLS is designed for production where deterministic behavior is critical. Consider cost, security, and reliability implications.
Troubleshooting
Missing Tool Errors
When agents try to use filtered tools:- Add missing tool to whitelist:
"web_search,send_email" - Update agent instructions to use only available tools
- Check tool name spelling in whitelist
Tool Discovery Issues
Name Matching Failures
Common tool name variations that cause mismatches:| Registered Name | Common Mistakes | Result |
|---|---|---|
web_search | websearch, web-search | Tool filtered out |
send_email | sendemail, email_send | Tool filtered out |
file_read | file-read, readfile | Tool filtered out |
Decision Guide
Choose the right filtering approach:Related
Tools Overview
Core tool system concepts
Agent Configuration
Agent setup and configuration

