Prompts are pre-built query templates that help you effectively search and retrieve vCons using the MCP server's search tools. They guide you on:
- Exact match searches using tags
- Keyword searches for specific phrases
- Semantic searches for natural language queries
- Complex multi-criteria searches combining multiple filters
- Best practices for different query scenarios
Prompt: find_by_exact_tags
Use when: You need precise category matching with specific tag values.
Example queries:
- "Find all customers from June that were tagged as 'angry'"
- "Show me high-priority sales calls"
- "List all support tickets marked as urgent"
Arguments:
tag_criteria(required): Natural language description of tags to matchdate_range(optional): Date range description
What it teaches:
- How to parse natural language into specific tag key-value pairs
- Converting date descriptions to ISO 8601 format
- Using the
search_by_tagstool effectively - When to use
get_unique_tagsto discover available tags
Prompt: find_by_semantic_search
Use when: You want to find conversations by meaning, not just exact words.
Example queries:
- "Find all the angry customers from June"
- "Show me conversations about billing problems"
- "Locate positive customer feedback"
Arguments:
search_description(required): Natural language description of what you're looking fordate_range(optional): Date range description
What it teaches:
- How semantic search finds meaning beyond keywords
- Understanding similarity thresholds (0.6-0.8)
- Using the
search_vcons_semantictool - When embeddings are required vs. keyword search
Prompt: find_by_keywords
Use when: You need to find specific words or phrases in conversation content.
Example queries:
- "Find conversations mentioning 'refund'"
- "Search for 'technical support' in dialogs"
- "Locate invoice #12345 discussions"
Arguments:
keywords(required): Specific keywords or phrases to searchfilters(optional): Additional filters like dates, tags, parties
What it teaches:
- Full-text search capabilities
- What content is searchable (dialog, analysis, subject, parties)
- Using the
search_vcons_contenttool - Interpreting relevance scores and snippets
Prompt: find_recent_by_topic
Use when: You need recent conversations filtered by topic or category.
Example queries:
- "Show me recent support calls"
- "Find this week's sales conversations"
- "List today's billing inquiries"
Arguments:
topic(required): Topic or category to searchtimeframe(optional): Recency timeframe (default: last 30 days)
What it teaches:
- Converting relative time phrases to date ranges
- Choosing between tag-based and semantic search
- Combining date filters with topic searches
- Sorting and presenting time-sensitive results
Prompt: find_by_customer
Use when: You need all conversations involving a specific person.
Example queries:
- "Find all conversations with john@example.com"
- "Show me calls from 555-1234"
- "List all interactions with Jane Smith"
Arguments:
party_identifier(required): Name, email, or phone numberdate_range(optional): Date range to filter results
What it teaches:
- Identifying party type (email vs. phone vs. name)
- Using the appropriate party filter
- Using the
search_vconstool with party parameters - Understanding case-insensitive and partial matching
Prompt: discover_available_tags
Use when: You want to explore what tags exist in your system.
Example queries:
- "What tags are available for filtering?"
- "Show me all department tags"
- "List available priority levels"
Arguments:
tag_category(optional): Focus on specific tag category
What it teaches:
- Using the
get_unique_tagstool - Understanding tag structure (key-value pairs)
- Viewing tag usage counts
- Building effective tag-based queries
Prompt: complex_search
Use when: You need to combine multiple search criteria.
Example queries:
- "Find high-priority sales calls from Q1 where customer mentioned pricing"
- "Show angry customers from the support department this month"
- "List urgent billing issues from last week"
Arguments:
search_criteria(required): Complete search description with all criteria
What it teaches:
- Breaking down complex queries into components
- Choosing the right search strategy for mixed criteria
- Combining tags, keywords, dates, and semantic search
- Using the
search_vcons_hybridtool effectively
Prompt: find_similar_conversations
Use when: You want to find conversations similar to a specific one.
Example queries:
- "Find conversations similar to UUID abc-123-def"
- "Show me calls like this customer complaint"
- "Locate similar support tickets"
Arguments:
reference(required): vCon UUID or topic descriptionlimit(optional): Number of similar conversations (default: 10)
What it teaches:
- Using vCon embeddings for similarity
- Adjusting similarity thresholds
- Understanding semantic similarity scores
- When to use UUID vs. description
Prompt: help_me_search
Use when: You're unsure which search approach to use.
Example queries:
- "How do I find billing disputes?"
- "What's the best way to search for recent angry customers?"
- "Should I use tags or keywords for this search?"
Arguments:
what_you_want(required): Description of what you're trying to find
What it teaches:
- Decision tree for choosing search tools
- Understanding exact match vs. keyword vs. semantic search
- Query optimization strategies
- Common pitfalls to avoid
-
List available prompts: The client will automatically discover prompts from the server.
-
Select a prompt: Choose the prompt that matches your use case.
-
Fill in arguments: Provide the required information (e.g., search criteria, date range).
-
Execute: The prompt will guide you with a detailed strategy and example tool calls.
User Goal: Find angry customers from June
-
Choose Prompt:
find_by_exact_tags(if you have sentiment tags) orfind_by_semantic_search(for natural language) -
Provide Arguments:
tag_criteria: "angry customers"date_range: "from June"
-
Follow Guidance: The prompt will show:
- How to parse "angry" into
{sentiment: "angry"} - How to convert "June" to ISO 8601 dates
- Which tool to call (
search_by_tags) - Example JSON for the tool call
- How to parse "angry" into
-
Execute Tool: Use the suggested tool with parameters
-
Review Results: Get matching vCons with UUIDs and details
Use this flowchart to choose the right prompt:
Do you know the exact tag value?
├─ YES → Use "find_by_exact_tags"
└─ NO
├─ Do you need specific words/phrases?
│ └─ YES → Use "find_by_keywords"
└─ NO
├─ Are you searching by meaning/concept?
│ └─ YES → Use "find_by_semantic_search"
└─ NO
├─ Is this a person/party search?
│ └─ YES → Use "find_by_customer"
└─ NO
├─ Multiple criteria?
│ └─ YES → Use "complex_search"
└─ UNSURE → Use "help_me_search"
Prompts teach you:
- How the search tools work
- Best practices for each scenario
- Parameter optimization
- Error handling and fallbacks
Prompts provide:
- Pre-structured queries
- Example JSON for tool calls
- Step-by-step guidance
- Time-saving templates
Prompts cover:
- All search tool variations
- Date parsing and formatting
- Tag discovery and usage
- Multi-criteria combining
Here's a quick reference of the tools prompts will guide you to use:
| Tool | Purpose | Key Parameters |
|---|---|---|
search_vcons |
Basic metadata search | party_name, party_email, subject, dates |
search_vcons_content |
Keyword search | query, tags, dates |
search_vcons_semantic |
Semantic/meaning search | query, threshold, tags |
search_vcons_hybrid |
Combined approach | query, semantic_weight, tags |
search_by_tags |
Exact tag matching | tags (object), limit |
get_unique_tags |
Discover available tags | include_counts, key_filter |
get_vcon |
Retrieve specific vCon | uuid |
- Find escalated issues:
find_by_exact_tagswith priority tags - Search complaints:
find_by_semantic_searchfor "complaints" or "issues" - Track customer history:
find_by_customerwith email/phone
- High-value opportunities:
find_by_exact_tagswith priority + department - Pricing discussions:
find_by_keywordssearching for "pricing" or "quote" - Recent qualified leads:
find_recent_by_topicwith "sales" topic
- Sentiment analysis:
find_by_exact_tagsorfind_by_semantic_searchfor sentiment - Topic clustering:
find_similar_conversationsto group related calls - Trend discovery:
find_recent_by_topicwith time ranges
- Audit trails:
find_by_customerfor specific party interactions - Keyword monitoring:
find_by_keywordsfor compliance terms - Tag validation:
discover_available_tagsto review taxonomy
- Begin with
discover_available_tagsto see what's possible - Use
help_me_searchto understand the best approach - Execute the recommended search
- Refine with additional filters if needed
- Relative: "last week", "this month", "Q1"
- Absolute: "June 2024", "2024-01-01 to 2024-03-31"
- Recent: Defaults to last 30 days in most prompts
- Use
get_unique_tagsfirst to discover what tags exist - Tag searches are EXACT - "angry" won't match "frustrated"
- Combine tags with AND logic (all must match)
- Consider semantic search for fuzzy matching
- Requires pre-generated embeddings
- Works across synonyms and paraphrases
- Adjust threshold based on precision needs:
- 0.6-0.7: Broader results
- 0.7-0.8: Balanced
- 0.8-0.9: Very similar only
- Always use date filters for "recent" queries
- Limit results to what you need (10-50)
- Use tags to pre-filter before content search
- Start with exact matches, fall back to semantic
After finding vCons, access them via resources:
vcon://v1/vcons/{uuid}
Use prompts to search, then use tag tools to organize:
manage_tag- Add/update/remove tagsget_tags- View existing tagsremove_all_tags- Clear tags
Combine prompt-guided searches with:
get_database_stats- Analyze search performanceanalyze_query- Optimize slow searches
- Try
discover_available_tagsto verify tags exist - Broaden date range or remove filters
- Use semantic search for fuzzy matching
- Check if embeddings are generated (for semantic search)
- Fall back to
search_vcons_contentfor keywords - Or generate embeddings using provided scripts
- Or use
search_vcons_hybridwith low semantic weight
- Add date range filters
- Include more specific tags
- Use more specific keywords
- Increase semantic threshold
- Verify tag values with
get_unique_tags - Check date format (should be ISO 8601)
- Try different search strategy (exact vs. semantic)
- Use
help_me_searchprompt for guidance
- Try the prompts: Start with
help_me_searchto explore - Learn the tools: Each prompt teaches specific tool usage
- Optimize queries: Use insights to build better searches
- Discover your data: Use
discover_available_tagsto understand your corpus
For more information:
- Search Guide - Detailed search tool documentation
- Tags Guide - Tag system documentation
- Getting Started - Getting started guide