Why Filter Tools?
Every active MCP tool consumes context in your agent’s conversation window. Loading all 22 tools when your agent only needs catalog search wastes tokens and can confuse the model with irrelevant options. Tool filtering lets you load only the tools relevant to your use case — reducing context size and improving focus.Environment Variables
ALANA_MCP_GROUPS
Load an entire category of tools by group name:| Group | Tools Included |
|---|---|
catalog | search_products, get_product, list_catalogs, get_catalog_stats |
optimization | optimize_product, batch_optimize, get_score, compare_scores |
media | generate_description, enhance_images, get_brand_context |
analytics | get_search_analytics, get_query_performance, get_recommendation_stats |
feed | Feed generation and status tools |
search | Advanced search and recommendation tools |
ALANA_MCP_TOOLS
Load specific tools by exact name:ALANA_MCP_GROUPS and ALANA_MCP_TOOLS are set, the union of both sets is loaded.
Configuration Examples
Catalog agent (read-only search)
search_products, get_product, list_catalogs, get_catalog_stats.
Content optimization agent
Analytics-only agent
Single-tool agent
Applying to MCP Client Config
Claude Desktop
Environment variable in server config
Context Window Impact
| Configuration | Tools Loaded | Approx. Token Cost |
|---|---|---|
| All tools (default) | 22 | ~4,200 tokens |
catalog group only | 4 | ~760 tokens |
| Single tool | 1 | ~190 tokens |