InsightSignal

Enrich a discovered (UNVERIFIED) entity — either a company or person — and promote it to a fully verified record with contact channels (email, phone, LinkedIn). For PERSONS, prefer passing `discovery_id` (the disc_<uuid> ID returned in the unverified_discovered_persons array of entity_get_company_people). The server resolves discovery_id → person_id (creating a Person record if needed). Use `person_id` only when you have an already-verified Person you want to re-enrich. Use confirm=false for cost estimate, confirm=true to execute (after user approves the cost).

action_discovery_enrichment

Enrich specific missing fields on companies in a job. Use confirm=false for cost estimate, confirm=true to execute.

action_field_enrichment

Enrich a person's contact details (email, phone, LinkedIn) through multi-source verification. Use confirm=false for cost estimate, confirm=true to execute.

action_person_enrichment

[CATEGORY: GRAPH] Explore graph relationships starting from a company — branches, employees, industry connections, AND discovered entities (competitors, partners, subsidiaries, investors, customers, key people). This is the PRIMARY function for answering questions about a company's competitors, partners, or any related entities. Returns both Neo4j graph data (nodes/edges) and MongoDB discovered entities in a single response. Use this when the user asks about competitors, partners, subsidiaries, relationships, or connections.

graph_get_relationships

[CATEGORY: DEEP_ANALYSIS] Get the intent scoring summary for a company — how well it matches the user's business intent. Returns category (target/competitor/middleman/partner/acquired/out_of_scope), intent_enhanced_alignment score (fitness to ACT, not confidence in the category — a confirmed competitor scores LOW), exclusion_flag, reasoning, adjusted_grade, research_informed status, and previous_category if reclassified after research. Use this when the user asks about fit, alignment, or classification of a company.

analysis_get_intent

[CATEGORY: ENTITY_LOOKUP] Get full details for a specific person including title, email, phone, LinkedIn, readiness grade (A-F), email_deliverability, email_quality_score, phone_valid, phone_line_type, phone_is_voip status, and company association. Returns has_email, has_phone, has_linkedin flags — only reference contact channels that actually exist. Includes source_count (number of independent verification sources) for trust assessment. ALSO returns the verified professional profile when available: headline, about (bio), skills (list), employment_history (list of roles with company/title/dates/is_current), education (schools/degrees), languages, and certifications. Use these to answer career-history / skills / background questions directly — do NOT say a person's history is 'not in the graph' when employment_history is populated. Empty lists mean that section hasn't been enriched yet (suggest a Sync/enrichment), not that it's unknowable.

entity_get_person

[CATEGORY: PORTFOLIO] Get big-picture statistics about the user's verified knowledge graph: average quality/completeness across all entities, grade distribution (A-F), industry breakdown, company size distribution (SMB/Mid-Market/Enterprise), revenue distribution (bucketed ranges), total companies and people counts, sample of top 5 companies (by grade and quality), and per-industry quality stats. Includes a hint for drilling down with search_companies filters. Use this when the user asks for charts, graphs, or breakdowns of their portfolio.

portfolio_get_stats

Push verified companies and their contacts to the user's connected CRM (e.g. Nutshell, Monday.com). The system auto-detects which CRM is connected — users can say 'push to CRM' or 'push to Nutshell'. Syncs company data, contacts, tags, industry, and research notes. Call with confirm=false first to see estimate (includes provider name), then confirm=true to execute.

action_crm_push

Verify a single company through multi-source verification pipeline (AI, web search, LinkedIn). Provide hint fields (industry, location) to improve verification accuracy. Use confirm=false to get a cost estimate first, then confirm=true to execute. INTENT SCORING (optional but recommended): Add intent parameters to get a personalized relevance grade — same company, different purpose = different score. Three options in priority order: 1. intent_profile_id — reuse a previously created profile (zero cost) 2. intent_type — pick a preset: sales_prospect, competitor_check, partner_fit, market_intel, investment_check, or legitimacy_check. Pair with intent_context for industry. No AI cost. 3. intent_text — free-form natural language (e.g. 'Evaluating as potential acquisition target in the healthcare AI space'). Triggers one-time AI analysis; cached by text hash for repeat calls. When intent is provided, the result includes intent_score, intent_category (target/competitor/middleman/partner/acquired/out_of_scope), exclusion_flag, and intent_reasoning explaining the classification. intent_score measures FITNESS TO ACT, not confidence in the category: a confirmed competitor scores LOW.

action_quick_verify

Re-score companies in a job against an updated intent profile. Use confirm=false for cost estimate, confirm=true to execute.

action_intent_rescore

[CATEGORY: PORTFOLIO] Get the user's recent verification runs, research reports, and enrichment jobs. Results are paginated. Use next_cursor from response to get more pages. The response carries 'as_of' (when the page was built) and 'window' {basis, since, until, unbounded}. If you pass no since_days/started_after/started_before, window.unbounded is true and 'total' is an ALL-TIME count — describe it as such, and never present those rows as belonging to a recent period. Rows may be months old; check started_at against as_of before calling anything recent.

portfolio_get_activity

Re-synthesize an existing research report with latest context (reuses cached source data — much cheaper than full regeneration). Use confirm=false for cost estimate, confirm=true to execute.

action_research_refresh

Extract contact information from a business card or conference badge image. Uses AI Vision OCR for printed text and decodes any PDF417 barcode on the badge, merging both — a badge barcode often carries an email that is not printed on the badge. Use confirm=false for cost estimate, confirm=true to execute.

action_scan_ocr

[CATEGORY: SEARCH] List the events (trade shows, conferences) where this user's contacts were captured via Scan Contact, with how many records came from each. Call this BEFORE using the `events` filter on search_companies / search_people so you pass a real slug rather than guessing one — 'CES 2027' is stored as 'ces-2027'. Answers 'which events have I been to?' and 'how many contacts did I get at CES?'. Read-only; captures are created in the Scan Contact wizard, not from chat.

search_events

[CATEGORY: SEARCH] Search and filter verified companies in the user's data. Returns a paginated list with grade (the EFFECTIVE InsightSignal grade — intent-adjusted when intent scoring exists, else the base data grade; each row also carries data_grade, grade_source, and numeric score), quality, completeness, source_count (number of independent verification sources), and — ONLY for records with a CRM integration — crm_outcome ('won'|'lost'|'in_pipeline'), crm_won_at, crm_lost_at, crm_won_source, crm_lost_source, crm_loss_reason. Records without any CRM connection omit the CRM fields entirely (do NOT assume absence means 'not won/lost'). Use crm_outcome='won' for closed-won deals, 'lost' for closed-lost, 'in_pipeline' for pushed-but-not-resolved, 'not_in_crm' for never-pushed records. Results are paginated. Use next_cursor from response to get more pages. Prefer filters over paging. ALL filters are optional, independent, and AND-combine — grade/min_grade work fine with no industry filter (pass industry ONLY when the user names one). Industry matching is case-insensitive and semantic; do not retry the same term with different casing.

search_companies

[CATEGORY: SEARCH] Search and filter people across the user's data — returned as TWO BUCKETS in the response: `verified_persons` (Person records that completed enrichment: real email/phone/LinkedIn, ready for outreach) and `unverified_discovered_persons` (DiscoveredEntity records — names surfaced by research/discovery, NO contact channels yet). Use the `bucket` parameter to scope: 'verified' for outreach questions ('who can I reach out to', 'find me deliverable emails'), 'discovered' for enrichment questions ('show me discovered names', 'who can I enrich next' — these carry discovery_id for action_discovery_enrichment), or 'both' (default) when intent is ambiguous. Verified bucket carries readiness_grade (A-F), email/phone/LinkedIn availability, enrichment_status. Discovered bucket carries person_name + title_hint + discovery_id (and next_step_to_verify hint). Cross-entity filters (industry, state) apply via knowledge graph traversal. REACHABILITY / 'who can I reach out to / contact / sell to' intent: reachability is already captured by readiness_grade (it scores email + phone + LinkedIn together), so use sort_by='readiness' and do NOT stack per-channel filters. email_deliverable / phone_verified each NARROW to that single channel and combine as AND — set one true ONLY when the user explicitly requires that specific channel; never pass false (it is not a negative filter). Verified results are paginated; discovered results are returned in full (capped at 50). Use next_cursor for more pages of verified. NEVER present a discovered person as a verified contact — they have no validated email/phone. If user wants to USE a discovered person, call action_discovery_enrichment(discovery_id=...) to promote them. Each person carries `relationship` + `is_employee`: an investor / board member / advisor has is_employee=false (relationship INVESTOR_IN / BOARD_MEMBER_OF / ADVISOR_TO) — for 'who works at' / 'employees / staff at' questions, exclude or clearly distinguish them; only is_employee=true people are staff.

search_people

[CATEGORY: DISCOVERY] Get a high-level map of all InsightSignal capabilities organized by category, with recommended workflows. Call this FIRST when you are unsure which tool to use, or when the user asks a broad question. Returns tool categories (core + any admin-approved generated functions), cross-tool workflows, data quality indicators, CRM deal outcome tracking (Phase 6.3/6.4 — won/lost/win-rate), and rate/cost hints. This avoids tool sprawl by guiding you to the right 2-3 tools for any task.

discovery_get_capabilities