@ema.co/mcp-toolkit 2026.2.13 → 2026.2.23

package/dist/sdk/generated/agent-catalog.js

@@ -0,0 +1,615 @@
+/**
+ * Agent Catalog — Auto-Generated API Fallback
+ *
+ * This is the AGENT_CATALOG array extracted from knowledge.ts.
+ * Used as a fallback when the API is unavailable.
+ *
+ * Generated from source repos via scheduled workflows.
+ * See: .context/core/guides/source-repos.md for full architecture
+ */
+export const AGENT_CATALOG = [
+    // Triggers
+    {
+        actionName: "chat_trigger",
+        displayName: "Chat Trigger",
+        category: "trigger",
+        description: "Entry point for chat-based interactions. Outputs both conversation history and current query.",
+        inputs: [],
+        outputs: [
+            { name: "chat_conversation", type: "WELL_KNOWN_TYPE_CHAT_CONVERSATION", description: "Full conversation history from start" },
+            { name: "user_query", type: "WELL_KNOWN_TYPE_TEXT_WITH_SOURCES", description: "Current user message only" },
+        ],
+        whenToUse: "Starting point for any chat or voice AI workflow",
+        criticalRules: [
+            "Each user message triggers a NEW workflow execution",
+            "chat_conversation accumulates; user_query is current message only",
+        ],
+    },
+    {
+        actionName: "document_trigger",
+        displayName: "Document Trigger",
+        category: "trigger",
+        description: "Entry point for document processing workflows triggered by file upload.",
+        inputs: [],
+        outputs: [
+            { name: "user_query", type: "WELL_KNOWN_TYPE_DOCUMENT", description: "Uploaded document(s)" },
+        ],
+        whenToUse: "When workflow is triggered by document upload for processing/extraction",
+    },
+    {
+        actionName: "voice_trigger",
+        displayName: "Voice Trigger",
+        category: "trigger",
+        description: "Entry point for voice/phone call interactions.",
+        inputs: [],
+        outputs: [
+            { name: "chat_conversation", type: "WELL_KNOWN_TYPE_CHAT_CONVERSATION", description: "Voice conversation history" },
+            { name: "user_query", type: "WELL_KNOWN_TYPE_TEXT_WITH_SOURCES", description: "Current utterance" },
+        ],
+        whenToUse: "Voice AI employees handling phone calls",
+    },
+    // Routing / Classification
+    {
+        actionName: "chat_categorizer",
+        displayName: "Intent Classifier",
+        category: "routing",
+        description: "Classifies user intent into predefined categories for routing. First routing node after trigger.",
+        inputs: [
+            { name: "conversation", type: "WELL_KNOWN_TYPE_CHAT_CONVERSATION", required: true, description: "Chat conversation to classify" },
+        ],
+        outputs: [
+            { name: "category", type: "WELL_KNOWN_TYPE_ENUM", description: "Outputs the matched category enum value (e.g., 'Client_Update', 'Fallback')" },
+        ],
+        criticalRules: [
+            "MUST have at least one outgoing edge",
+            "runIf condition: compare 'output: category' to 'enumValue: <CategoryName>' (NOT category_<name> format)",
+            "Handler nodes use runIf conditions to route by category",
+            "ALWAYS include a Fallback category",
+            "Create a runIf condition for EACH category or routing fails",
+            "You MUST create a handler for EACH category",
+        ],
+        whenToUse: "When you need to route chat conversations to different processing paths based on intent",
+        whenNotToUse: "Simple single-path workflows that don't need routing",
+        example: "Categories: [Market_Impact, Client_Lookup, Compliance_Check, Fallback]",
+    },
+    {
+        actionName: "text_categorizer",
+        displayName: "Text Categorizer",
+        category: "routing",
+        description: "Classifies text content (not conversation) into categories.",
+        inputs: [
+            { name: "text", type: "WELL_KNOWN_TYPE_TEXT_WITH_SOURCES", required: true, description: "Text to classify" },
+        ],
+        outputs: [
+            { name: "category", type: "WELL_KNOWN_TYPE_ENUM", description: "Classification result" },
+        ],
+        criticalRules: [
+            "Same rules as chat_categorizer: must have Fallback, edges for each category",
+        ],
+        whenToUse: "When routing based on text content rather than full conversation history",
+    },
+    {
+        actionName: "document_categorizer",
+        displayName: "Document Categorizer",
+        category: "routing",
+        description: "Classifies documents into categories for routing.",
+        inputs: [
+            { name: "documents", type: "WELL_KNOWN_TYPE_DOCUMENT", required: true, description: "Documents to classify" },
+        ],
+        outputs: [
+            { name: "category", type: "WELL_KNOWN_TYPE_ENUM", description: "Document classification" },
+        ],
+        whenToUse: "When routing based on document type or content",
+    },
+    {
+        actionName: "conversation_to_search_query",
+        displayName: "Conversation Summarizer",
+        category: "routing",
+        description: "Converts conversation history to a search query. Configurable turn count.",
+        inputs: [
+            { name: "conversation", type: "WELL_KNOWN_TYPE_CHAT_CONVERSATION", required: true, description: "Conversation to summarize" },
+        ],
+        outputs: [
+            { name: "summarized_conversation", type: "WELL_KNOWN_TYPE_TEXT_WITH_SOURCES", description: "Distilled search query" },
+        ],
+        whenToUse: "Before search nodes when you have chat_conversation but need TEXT_WITH_SOURCES. Also for managing long conversation context windows.",
+        whenNotToUse: "When trigger.user_query is sufficient for simple queries",
+        criticalRules: [
+            "May still be needed WITH chat_conversation for downstream agents requiring specific format",
+            "Use to reduce conversation size due to LLM context window limits",
+        ],
+    },
+    // Search & Retrieval
+    {
+        actionName: "search",
+        displayName: "File Search / Knowledge Search",
+        category: "search",
+        description: "Searches uploaded documents/knowledge base using hybrid search (keyword + vector). Use version v2 (search/v2) which requires datastore_configs input. search/v0 is deprecated.",
+        inputs: [
+            { name: "query", type: "WELL_KNOWN_TYPE_TEXT_WITH_SOURCES", required: true, description: "Search query" },
+            { name: "datastore_configs", type: "WELL_KNOWN_TYPE_ANY", required: false, description: "Datastore configuration (v2). Wired from persona widget config." },
+        ],
+        outputs: [
+            { name: "search_results", type: "WELL_KNOWN_TYPE_SEARCH_RESULT", description: "Matching passages with sources and citations" },
+        ],
+        whenToUse: "When searching static uploaded documents or internal knowledge base. Always use search/v2 (not deprecated search/v0).",
+        whenNotToUse: "For real-time web content — use live_web_search or ai_web_search instead",
+        example: "FAQ lookup, policy search, documentation assistant",
+    },
+    {
+        actionName: "live_web_search",
+        displayName: "Live Web Search / Deep Web Search",
+        category: "search",
+        description: "Real-time web search for external information not in knowledge base.",
+        inputs: [
+            { name: "query", type: "WELL_KNOWN_TYPE_TEXT_WITH_SOURCES", required: true, description: "Search query" },
+        ],
+        outputs: [
+            { name: "web_search_results", type: "WELL_KNOWN_TYPE_SEARCH_RESULT", description: "Web search results" },
+        ],
+        whenToUse: "When you need real-time external information not in the knowledge base",
+        example: "Current events, live data, external research",
+    },
+    {
+        actionName: "combine_search_results",
+        displayName: "Combine Search Results",
+        category: "search",
+        description: "Merges results from multiple search sources with deduplication.",
+        inputs: [
+            { name: "search_results_1", type: "WELL_KNOWN_TYPE_SEARCH_RESULT", required: true, description: "First result set" },
+            { name: "search_results_2", type: "WELL_KNOWN_TYPE_SEARCH_RESULT", required: true, description: "Second result set" },
+        ],
+        outputs: [
+            { name: "combined_results", type: "WELL_KNOWN_TYPE_SEARCH_RESULT", description: "Merged, deduplicated results" },
+        ],
+        criticalRules: [
+            "AVOID using unless necessary - prefer combine_and_rerank_search_results or call_llm with named_inputs",
+            "combine_and_rerank_search_results provides intelligent relevance ranking",
+            "call_llm with named_inputs allows prompt-based ranking control",
+        ],
+        whenToUse: "When combining local + web search, or multiple knowledge bases",
+        whenNotToUse: "When you need intelligent ranking - use combine_and_rerank_search_results instead",
+    },
+    {
+        actionName: "combine_and_rerank_search_results",
+        displayName: "Rerank Search Results",
+        category: "search",
+        description: "Combines and reranks search results by relevance.",
+        inputs: [
+            { name: "query", type: "WELL_KNOWN_TYPE_TEXT_WITH_SOURCES", required: true, description: "Original query for relevance scoring" },
+            { name: "search_results_lists", type: "WELL_KNOWN_TYPE_SEARCH_RESULT", required: true, description: "Results to rerank" },
+        ],
+        outputs: [
+            { name: "reranked_results", type: "WELL_KNOWN_TYPE_SEARCH_RESULT", description: "Reranked results" },
+        ],
+        whenToUse: "When you need to prioritize results by relevance after combining multiple sources",
+    },
+    {
+        actionName: "document_metasearch",
+        displayName: "Document Metasearch",
+        category: "search",
+        description: "Searches across document metadata.",
+        inputs: [
+            { name: "query", type: "WELL_KNOWN_TYPE_TEXT_WITH_SOURCES", required: true, description: "Metadata query" },
+            { name: "template", type: "WELL_KNOWN_TYPE_TEXT_WITH_SOURCES", required: true, description: "Search template" },
+        ],
+        outputs: [
+            { name: "document_metasearch_results", type: "WELL_KNOWN_TYPE_SEARCH_RESULT", description: "Metadata search results" },
+        ],
+        whenToUse: "When searching by document metadata rather than content",
+    },
+    // Generation & Response
+    {
+        actionName: "call_llm",
+        displayName: "Respond",
+        category: "generation",
+        description: "Generates response using LLM with custom instructions. Accepts ANY type via named_inputs. Also used for LLM templating.",
+        inputs: [
+            { name: "query", type: "WELL_KNOWN_TYPE_TEXT_WITH_SOURCES", required: true, description: "User query" },
+            { name: "named_inputs", type: "WELL_KNOWN_TYPE_ANY", required: false, description: "Additional context (use named_inputs_<Name> suffix)" },
+        ],
+        outputs: [
+            { name: "response_with_sources", type: "WELL_KNOWN_TYPE_TEXT_WITH_SOURCES", description: "Generated response" },
+        ],
+        whenToUse: "When you need custom response generation, content synthesis, or LLM templating for documents",
+        whenNotToUse: "For strict regulatory formats requiring pixel-perfect layouts - use template engine instead",
+        criticalRules: [
+            "named_inputs accepts ANY type - use for tool results, search results, etc.",
+            "Use suffix pattern: named_inputs_<Descriptive_Name>",
+            "LLM TEMPLATING: Include structured section headers (## Section) in prompt - let LLM determine appropriate sections based on content",
+            "For document generation: Set temperature 0.3-0.5 for consistent formatting",
+            "Use structured prompts with clear formatting rules and examples",
+        ],
+        example: "named_inputs_Market_Context, named_inputs_Client_Data | " +
+            "LLM Template prompt: 'Generate structured content with clear ## section headers, organized by themes'",
+    },
+    {
+        actionName: "generate_document",
+        displayName: "Generate Document",
+        category: "generation",
+        description: "Converts markdown content to formatted document (.docx). Use after call_llm for document generation workflows.",
+        inputs: [
+            { name: "markdown_file_contents", type: "WELL_KNOWN_TYPE_TEXT_WITH_SOURCES", required: true, description: "Well-structured markdown to convert" },
+            { name: "template", type: "WELL_KNOWN_TYPE_DOCUMENT", required: false, description: "Optional template from data source for styling" },
+        ],
+        outputs: [
+            { name: "document_link", type: "WELL_KNOWN_TYPE_DOCUMENT", description: "Link to generated document" },
+        ],
+        whenToUse: "When converting LLM-generated markdown to professional document format",
+        criticalRules: [
+            "Ensure input markdown has clear headers (## Section) and structure",
+            "For email attachment: use named_inputs (not attachment_links) due to DOCUMENT type",
+            "Chain pattern: call_llm (content generation) → generate_document → send_email (via named_inputs)",
+            "Optional: Add CSS/styling in markdown for professional formatting",
+        ],
+        example: "detailed_content (call_llm) → generate_doc → send_email.named_inputs_Attachment",
+    },
+    {
+        actionName: "respond_with_sources",
+        displayName: "Respond using Search Results",
+        category: "generation",
+        description: "Generates response grounded in search results with citations.",
+        inputs: [
+            { name: "query", type: "WELL_KNOWN_TYPE_TEXT_WITH_SOURCES", required: true, description: "User query" },
+            { name: "search_results", type: "WELL_KNOWN_TYPE_SEARCH_RESULT", required: true, description: "Search results to ground response" },
+        ],
+        outputs: [
+            { name: "response_with_sources", type: "WELL_KNOWN_TYPE_TEXT_WITH_SOURCES", description: "Response with citations" },
+        ],
+        whenToUse: "When you want responses grounded in specific search results with source citations",
+        criticalRules: [
+            "Enable use_citation_based_filtering for trust",
+            "Implement confidence thresholds for quality control",
+        ],
+    },
+    {
+        actionName: "respond_for_external_actions",
+        displayName: "Respond using Tool Result",
+        category: "generation",
+        description: "Generates response explaining external tool/action results.",
+        inputs: [
+            { name: "query", type: "WELL_KNOWN_TYPE_TEXT_WITH_SOURCES", required: true, description: "Original query" },
+            { name: "external_action_result", type: "WELL_KNOWN_TYPE_ANY", required: true, description: "Tool execution result" },
+        ],
+        outputs: [
+            { name: "response", type: "WELL_KNOWN_TYPE_TEXT_WITH_SOURCES", description: "Human-friendly explanation" },
+        ],
+        whenToUse: "After external_action_caller to explain results to user",
+    },
+    {
+        actionName: "fixed_response",
+        displayName: "Fixed Response",
+        category: "generation",
+        description: "Returns a static/template response with {{variable}} substitution. No LLM call.",
+        inputs: [
+            { name: "named_inputs", type: "WELL_KNOWN_TYPE_ANY", required: false, description: "Variables to substitute into template (use named_inputs_<Variable_Name>)" },
+            { name: "extracted_variables", type: "WELL_KNOWN_TYPE_ANY", required: false, description: "JSON key-value pairs for variable substitution" },
+            { name: "fixed_response", type: "WELL_KNOWN_TYPE_TEXT_WITH_SOURCES", required: true, description: "Template with {{variable_name}} placeholders" },
+        ],
+        outputs: [
+            { name: "fixed_response_with_sources", type: "WELL_KNOWN_TYPE_TEXT_WITH_SOURCES", description: "Response with variables substituted" },
+        ],
+        whenToUse: "For short, structured messages with variables: confirmations, acknowledgments, simple notifications",
+        whenNotToUse: "For complex templates - use data source templates with generate_document or fill_document_template instead",
+        criticalRules: [
+            "Use {{variable_name}} syntax for dynamic content (case-sensitive)",
+            "named_inputs takes precedence over extracted_variables when same variable name exists",
+            "Keep templates SHORT - for long emails/documents use data source templates",
+            "Variables must match exactly including case",
+        ],
+        example: "Template: 'Dear {{Customer_Name}}, your order {{Order_ID}} has been {{Status}}.' " +
+            "→ Connect entity_extraction.customer_name to named_inputs_Customer_Name",
+    },
+    {
+        actionName: "send_email_agent",
+        displayName: "Send Email",
+        category: "external",
+        description: "Sends email via configured email provider.",
+        inputs: [
+            { name: "email_to", type: "WELL_KNOWN_TYPE_TEXT_WITH_SOURCES", required: true, description: "Recipient email address - use fixed_response with {{email}} template" },
+            { name: "email_subject", type: "WELL_KNOWN_TYPE_ANY", required: false, description: "Email subject line" },
+            { name: "email_body", type: "WELL_KNOWN_TYPE_TEXT_WITH_SOURCES", required: true, description: "Email body content" },
+            { name: "attachment_links", type: "WELL_KNOWN_TYPE_TEXT_WITH_SOURCES", required: false, description: "Document links to attach (use named_inputs for DOCUMENT type)" },
+        ],
+        outputs: [
+            { name: "send_status", type: "WELL_KNOWN_TYPE_ANY", description: "Send confirmation" },
+        ],
+        whenToUse: "When you need to send email after user confirmation",
+        criticalRules: [
+            "email_to requires TEXT_WITH_SOURCES type - use fixed_response with {{email}} template populated from entity_extraction",
+            "ALWAYS use HITL confirmation before sending (runIf: 'HITL Success')",
+            "For attachments with DOCUMENT type, use named_inputs instead of attachment_links",
+            "Never connect summarized_conversation or search_results directly to email_to",
+        ],
+        example: "entity_extraction → fixed_response('{{email}}') → send_email.email_to (CORRECT pattern)",
+    },
+    // External Actions
+    {
+        actionName: "external_action_caller",
+        displayName: "External Tool Caller / Intelligent Actions",
+        category: "external",
+        description: "Calls external APIs/tools (ServiceNow, Salesforce, Workday, etc.).",
+        inputs: [
+            { name: "query", type: "WELL_KNOWN_TYPE_TEXT_WITH_SOURCES", required: true, description: "Context for tool call" },
+            { name: "conversation", type: "WELL_KNOWN_TYPE_CHAT_CONVERSATION", required: false, description: "Conversation history" },
+        ],
+        outputs: [
+            { name: "tool_execution_result", type: "WELL_KNOWN_TYPE_ANY", description: "Tool execution result" },
+        ],
+        whenToUse: "When you need to call external systems (create ticket, send email, lookup CRM, update records)",
+        criticalRules: [
+            "Check conversation history before creating records to avoid duplicates",
+            "external_action_caller does NOT support HITL — only send_email_agent and entity_extraction_with_documents do",
+        ],
+        example: "ServiceNow ticket creation, Salesforce record update, Email sending",
+    },
+    // Entity & Rule Processing
+    {
+        actionName: "entity_extraction_with_documents",
+        displayName: "Entity Extraction",
+        category: "entity",
+        description: "Extracts structured entities from documents for cross-document linking or API calls.",
+        inputs: [
+            { name: "documents", type: "WELL_KNOWN_TYPE_DOCUMENT", required: true, description: "Documents to extract from" },
+            { name: "extraction_columns", type: "WELL_KNOWN_TYPE_ANY", required: true, description: "Schema defining what to extract" },
+        ],
+        outputs: [
+            { name: "extraction_columns", type: "WELL_KNOWN_TYPE_ANY", description: "Extracted structured data" },
+        ],
+        criticalRules: [
+            "Works on DOCUMENTS, not text",
+            "Requires schema definition for extraction columns",
+        ],
+        whenToUse: "When you need structured data extraction for cross-document linking, API calls, or audit trails with citations",
+        whenNotToUse: "For simple conversational queries—use LLM resolution instead",
+    },
+    {
+        actionName: "rule_validation_with_documents",
+        displayName: "Rule Validation",
+        category: "validation",
+        description: "Validates extracted data against business rules. Rules are configured through the node's settings panel (UI), not via workflow_def inputs. Each rule has a name and description. Output mode is Pass/Fail per rule.",
+        inputs: [
+            { name: "primary_docs", type: "WELL_KNOWN_TYPE_DOCUMENT", required: true, description: "Primary documents to validate against" },
+            { name: "map_of_extracted_columns", type: "WELL_KNOWN_TYPE_ANY", required: true, description: "Extracted data from entity_extraction to validate" },
+        ],
+        outputs: [
+            { name: "ruleset_output", type: "WELL_KNOWN_TYPE_ANY", description: "Pass/Fail results per rule with explanations" },
+        ],
+        whenToUse: "For compliance checks, business rule validation, threshold checking. Rules (e.g., 'Required Fields', 'Data Variance') are defined in the node's UI settings — the LLM only needs to wire inputs/outputs correctly.",
+    },
+    // Human Collaboration
+    // NOTE: general_hitl is NOT a deployable node — it appears in catalogs but cannot be deployed.
+    // HITL is implemented as a FLAG on specific agents: entity_extraction_with_documents and send_email_agent.
+    // Kept here for reference when analyzing existing workflows that may use it.
+    {
+        actionName: "general_hitl",
+        displayName: "Human Collaboration (NOT RECOMMENDED — use agent flags instead)",
+        category: "collaboration",
+        description: "NOT DEPLOYABLE — general_hitl appears in catalogs but cannot be deployed. HITL approval is a flag on entity_extraction_with_documents and send_email_agent only. Do NOT add general_hitl nodes to workflows.",
+        inputs: [
+            { name: "query", type: "WELL_KNOWN_TYPE_TEXT_WITH_SOURCES", required: true, description: "Context for review" },
+        ],
+        outputs: [
+            { name: "hitl_status_HITL Success", type: "WELL_KNOWN_TYPE_ANY", description: "Human approved path" },
+            { name: "hitl_status_HITL Failure", type: "WELL_KNOWN_TYPE_ANY", description: "Human rejected path" },
+        ],
+        criticalRules: [
+            "general_hitl is NOT deployable — do NOT add it to any workflow",
+            "If user asks for approval: enable the HITL flag on entity_extraction_with_documents or send_email_agent (only nodes that support HITL)",
+            "external_action_caller does NOT support HITL despite appearing in older guidance",
+            "If you encounter general_hitl in an existing workflow: it may not function correctly",
+        ],
+        whenToUse: "DO NOT USE — general_hitl is not deployable. HITL is a flag on entity_extraction_with_documents and send_email_agent only.",
+        example: "For approval: enable HITL flag on send_email_agent (disable_human_interaction: false)",
+    },
+    // Validation & Guardrails
+    {
+        actionName: "response_validator",
+        displayName: "Response Validator",
+        category: "validation",
+        description: "Validates LLM output against criteria. Guardrail for response quality.",
+        inputs: [
+            { name: "reference_query", type: "WELL_KNOWN_TYPE_TEXT_WITH_SOURCES", required: true, description: "Original query" },
+            { name: "response_to_validate", type: "WELL_KNOWN_TYPE_TEXT_WITH_SOURCES", required: true, description: "Response to check" },
+        ],
+        outputs: [
+            { name: "abstain_reason", type: "WELL_KNOWN_TYPE_TEXT_WITH_SOURCES", description: "Reason if validation fails" },
+        ],
+        whenToUse: "For guardrails, compliance checking on generated responses, quality control",
+    },
+    {
+        actionName: "abstain_action",
+        displayName: "Abstain from Answering",
+        category: "validation",
+        description: "Declines to answer when appropriate. Graceful handling of out-of-scope queries.",
+        inputs: [
+            { name: "abstain_reason", type: "WELL_KNOWN_TYPE_TEXT_WITH_SOURCES", required: true, description: "Why abstaining" },
+        ],
+        outputs: [
+            { name: "abstain_reason", type: "WELL_KNOWN_TYPE_TEXT_WITH_SOURCES", description: "Abstention message" },
+        ],
+        whenToUse: "When the AI should explicitly decline to answer or redirect",
+    },
+    // Sentiment & Analysis
+    {
+        actionName: "sentiment_analyzer",
+        displayName: "Sentiment Analyzer",
+        category: "analytics",
+        description: "Analyzes sentiment/emotion in user input.",
+        inputs: [
+            { name: "text", type: "WELL_KNOWN_TYPE_TEXT_WITH_SOURCES", required: true, description: "Text to analyze" },
+        ],
+        outputs: [
+            { name: "sentiment", type: "WELL_KNOWN_TYPE_TEXT_WITH_SOURCES", description: "Sentiment analysis" },
+        ],
+        whenToUse: "When you need to gauge user emotion for routing or response tone adjustment",
+    },
+    // Domain Agents - Finance
+    {
+        actionName: "financial_risk_assessor",
+        displayName: "Financial Risk Assessor",
+        category: "finance",
+        description: "Analyzes financial risk factors for investment/credit decisions.",
+        inputs: [{ name: "query", type: "WELL_KNOWN_TYPE_TEXT_WITH_SOURCES", required: true, description: "Risk query" }],
+        outputs: [{ name: "risk_assessment", type: "WELL_KNOWN_TYPE_TEXT_WITH_SOURCES", description: "Risk analysis" }],
+        whenToUse: "Financial services: portfolio risk, credit assessment, exposure analysis",
+    },
+    {
+        actionName: "financial_statement_analyzer",
+        displayName: "Financial Statement Analyzer",
+        category: "finance",
+        description: "Analyzes financial statements and reports.",
+        inputs: [{ name: "documents", type: "WELL_KNOWN_TYPE_DOCUMENT", required: true, description: "Financial documents" }],
+        outputs: [{ name: "analysis", type: "WELL_KNOWN_TYPE_TEXT_WITH_SOURCES", description: "Financial analysis" }],
+        whenToUse: "Analyzing P&L, balance sheets, annual reports",
+    },
+    {
+        actionName: "tax_advisor",
+        displayName: "Tax Advisor",
+        category: "finance",
+        description: "Provides tax-related guidance and analysis.",
+        inputs: [{ name: "query", type: "WELL_KNOWN_TYPE_TEXT_WITH_SOURCES", required: true, description: "Tax question" }],
+        outputs: [{ name: "tax_advice", type: "WELL_KNOWN_TYPE_TEXT_WITH_SOURCES", description: "Tax guidance" }],
+        whenToUse: "Tax planning, compliance questions, deduction analysis",
+    },
+    {
+        actionName: "audit_evidence_verifier",
+        displayName: "Audit Evidence Verifier",
+        category: "finance",
+        description: "Verifies audit evidence and documentation.",
+        inputs: [{ name: "documents", type: "WELL_KNOWN_TYPE_DOCUMENT", required: true, description: "Audit documents" }],
+        outputs: [{ name: "verification", type: "WELL_KNOWN_TYPE_TEXT_WITH_SOURCES", description: "Verification results" }],
+        whenToUse: "Audit support, evidence verification, compliance documentation",
+    },
+    // Domain Agents - Healthcare
+    {
+        actionName: "medical_record_summarizer",
+        displayName: "Medical Record Summarizer",
+        category: "healthcare",
+        description: "Summarizes medical records and patient history.",
+        inputs: [{ name: "documents", type: "WELL_KNOWN_TYPE_DOCUMENT", required: true, description: "Medical records" }],
+        outputs: [{ name: "summary", type: "WELL_KNOWN_TYPE_TEXT_WITH_SOURCES", description: "Record summary" }],
+        whenToUse: "Healthcare: summarizing patient records, medical history, clinical notes",
+    },
+    {
+        actionName: "medical_research_assistant",
+        displayName: "Medical Research Assistant",
+        category: "healthcare",
+        description: "Assists with medical research queries.",
+        inputs: [{ name: "query", type: "WELL_KNOWN_TYPE_TEXT_WITH_SOURCES", required: true, description: "Research query" }],
+        outputs: [{ name: "research", type: "WELL_KNOWN_TYPE_TEXT_WITH_SOURCES", description: "Research findings" }],
+        whenToUse: "Medical research, literature review, clinical guidance",
+    },
+    {
+        actionName: "insurance_claim_summarizer",
+        displayName: "Insurance Claim Summarizer",
+        category: "healthcare",
+        description: "Summarizes insurance claims and documentation.",
+        inputs: [{ name: "documents", type: "WELL_KNOWN_TYPE_DOCUMENT", required: true, description: "Claim documents" }],
+        outputs: [{ name: "summary", type: "WELL_KNOWN_TYPE_TEXT_WITH_SOURCES", description: "Claim summary" }],
+        whenToUse: "Insurance processing, claim analysis",
+    },
+    // Domain Agents - Legal
+    {
+        actionName: "compliance_document_analyzer",
+        displayName: "Compliance Document Analyzer",
+        category: "legal",
+        description: "Analyzes documents for compliance issues.",
+        inputs: [{ name: "documents", type: "WELL_KNOWN_TYPE_DOCUMENT", required: true, description: "Documents to analyze" }],
+        outputs: [{ name: "compliance_findings", type: "WELL_KNOWN_TYPE_TEXT_WITH_SOURCES", description: "Compliance analysis" }],
+        whenToUse: "Regulatory compliance, contract review, policy compliance",
+    },
+    {
+        actionName: "legal_expert",
+        displayName: "Legal Expert",
+        category: "legal",
+        description: "Provides legal analysis and guidance.",
+        inputs: [{ name: "query", type: "WELL_KNOWN_TYPE_TEXT_WITH_SOURCES", required: true, description: "Legal question" }],
+        outputs: [{ name: "legal_analysis", type: "WELL_KNOWN_TYPE_TEXT_WITH_SOURCES", description: "Legal guidance" }],
+        whenToUse: "Legal research, contract analysis, regulatory questions",
+    },
+    {
+        actionName: "information_redacter",
+        displayName: "Information Redacter",
+        category: "legal",
+        description: "Redacts sensitive information from documents.",
+        inputs: [{ name: "documents", type: "WELL_KNOWN_TYPE_DOCUMENT", required: true, description: "Documents to redact" }],
+        outputs: [{ name: "redacted", type: "WELL_KNOWN_TYPE_DOCUMENT", description: "Redacted documents" }],
+        whenToUse: "Privacy compliance, document sanitization",
+    },
+    // Domain Agents - IT/Security
+    {
+        actionName: "phishing_email_detector",
+        displayName: "Phishing Email Detector",
+        category: "it_security",
+        description: "Detects phishing attempts in emails.",
+        inputs: [{ name: "email_content", type: "WELL_KNOWN_TYPE_TEXT_WITH_SOURCES", required: true, description: "Email to analyze" }],
+        outputs: [{ name: "detection_result", type: "WELL_KNOWN_TYPE_TEXT_WITH_SOURCES", description: "Phishing analysis" }],
+        whenToUse: "Email security, security operations",
+    },
+    {
+        actionName: "cybersecurity_expert",
+        displayName: "Cybersecurity Expert",
+        category: "it_security",
+        description: "Provides cybersecurity analysis and guidance.",
+        inputs: [{ name: "query", type: "WELL_KNOWN_TYPE_TEXT_WITH_SOURCES", required: true, description: "Security query" }],
+        outputs: [{ name: "security_analysis", type: "WELL_KNOWN_TYPE_TEXT_WITH_SOURCES", description: "Security guidance" }],
+        whenToUse: "Security incident analysis, vulnerability assessment",
+    },
+    {
+        actionName: "technical_support",
+        displayName: "Technical Support",
+        category: "it_security",
+        description: "Provides IT technical support guidance.",
+        inputs: [{ name: "query", type: "WELL_KNOWN_TYPE_TEXT_WITH_SOURCES", required: true, description: "Support query" }],
+        outputs: [{ name: "support_response", type: "WELL_KNOWN_TYPE_TEXT_WITH_SOURCES", description: "Technical guidance" }],
+        whenToUse: "IT helpdesk, troubleshooting, technical guidance",
+    },
+    // Domain Agents - Sales
+    {
+        actionName: "sales_intelligence",
+        displayName: "Sales Intelligence",
+        category: "sales",
+        description: "Provides sales insights and account intelligence.",
+        inputs: [{ name: "query", type: "WELL_KNOWN_TYPE_TEXT_WITH_SOURCES", required: true, description: "Sales query" }],
+        outputs: [{ name: "intelligence", type: "WELL_KNOWN_TYPE_TEXT_WITH_SOURCES", description: "Sales insights" }],
+        whenToUse: "Account research, competitive analysis, opportunity assessment",
+    },
+    {
+        actionName: "email_writer",
+        displayName: "Email Writer",
+        category: "sales",
+        description: "Generates professional email content.",
+        inputs: [{ name: "query", type: "WELL_KNOWN_TYPE_TEXT_WITH_SOURCES", required: true, description: "Email context" }],
+        outputs: [{ name: "email", type: "WELL_KNOWN_TYPE_TEXT_WITH_SOURCES", description: "Generated email" }],
+        whenToUse: "Sales outreach, customer communication, follow-ups",
+    },
+    // Formatting Agents
+    {
+        actionName: "json_formatter",
+        displayName: "JSON Formatter",
+        category: "formatting",
+        description: "Formats output as JSON.",
+        inputs: [{ name: "content", type: "WELL_KNOWN_TYPE_TEXT_WITH_SOURCES", required: true, description: "Content to format" }],
+        outputs: [{ name: "json", type: "WELL_KNOWN_TYPE_TEXT_WITH_SOURCES", description: "JSON formatted output" }],
+        whenToUse: "When structured JSON output is required",
+    },
+    {
+        actionName: "json_extractor",
+        displayName: "JSON Extractor",
+        category: "formatting",
+        description: "Extracts JSON from LLM output.",
+        inputs: [{ name: "content", type: "WELL_KNOWN_TYPE_TEXT_WITH_SOURCES", required: true, description: "Content containing JSON" }],
+        outputs: [{ name: "extracted_json", type: "WELL_KNOWN_TYPE_ANY", description: "Extracted JSON object" }],
+        whenToUse: "When you need to parse JSON from LLM responses",
+    },
+    {
+        actionName: "markdown_formatter",
+        displayName: "Markdown Formatter",
+        category: "formatting",
+        description: "Formats output as Markdown.",
+        inputs: [{ name: "content", type: "WELL_KNOWN_TYPE_TEXT_WITH_SOURCES", required: true, description: "Content to format" }],
+        outputs: [{ name: "markdown", type: "WELL_KNOWN_TYPE_TEXT_WITH_SOURCES", description: "Markdown formatted output" }],
+        whenToUse: "When rich text formatting is needed",
+    },
+];