Update to LeadContact

{
  "description": "Find professional contacts and build targeted lead lists with LeadContact. Use when the user asks to find people by role, title, company, industry, location, seniority, skills, company size, employment history, or other supported professional and company criteria. Do not use to retrieve a specific person's background, email address, or phone number.\n",
  "included_files": [],
  "name": "prospect",
  "skill_md_contents": "---\nname: prospect\ndescription: >\n  Find professional contacts and build targeted lead lists with LeadContact.\n  Use when the user asks to find people by role, title, company, industry,\n  location, seniority, skills, company size, employment history, or other\n  supported professional and company criteria. Do not use to retrieve a\n  specific person's background, email address, or phone number.\n---\n\n# Prospect\n\nUse LeadContact to turn natural-language criteria into a relevant professional contact list.\n\n## Account Handling\n\n- Use only the LeadContact account connection selected for the current request.\n- If multiple accounts are connected and no account has been selected, ask the user to choose an account before performing a lookup that consumes API Credits.\n- Never switch to another connected account automatically, including when the selected account has insufficient API Credits.\n- Do not merge results, balances, unlocked data, or charges across accounts.\n\n## Step 1 — Parse the Search Criteria\n\nExtract and resolve the supported criteria from the user's request.\n\n- Use only criteria stated by the user or clearly established in the current conversation.\n- Map each criterion to a supported `search_people` field.\n- Prefer a dedicated structured field over a general keyword field. Use a keyword only when no supported structured field represents the user's criterion.\n- Apply each criterion once. Do not duplicate the same concept across structured fields and keywords or switch interpretations between retries.\n- Map explicit job titles or named roles, such as CEO or Sales Director, to job-title fields. Map broad departments or functions, such as Sales or Marketing, to job-function fields. If a phrase could materially change the scope depending on the mapping, ask one clarifying question.\n- Interpret current-employment language, such as \"currently at\" or \"works at,\" as a current-company criterion. Interpret past-employment language, such as \"previously at,\" \"formerly at,\" or \"worked at,\" as a previous-company criterion. Do not substitute one for the other.\n- Use only company-size values supported by the tool. If the user's range cannot be represented exactly, ask one clarifying question with the closest supported options instead of silently broadening or approximating it.\n- Preserve the user's intended scope. Do not add or broaden titles, industries, locations, companies, employment periods, or other criteria unless the user requests or confirms it.\n- If the request is too vague or an important criterion cannot be resolved confidently, ask one clarifying question.\n\n## Step 2 — Search Contacts\n\nUse `search_people` with the resolved criteria.\n\n- If the user specifies a result count, continue through the pagination returned for the same query until that count is reached or no more results are available.\n- If no count is specified, use the initial result set returned by the tool.\n- If the user asks for \"all\" or \"as many as possible,\" ask for a target count first.\n- Count unique contacts returned by LeadContact toward the requested number.\n- Do not run additional searches to replace contacts you personally judge to be mismatches; additional searches may consume API Credits.\n- Do not change, remove, or broaden the filters to reach the requested count. Only continue the same query through its returned pagination.\n- Do not retrieve beyond the requested count or initial result set unless the user asks.\n\nProceed without an extra confirmation when the request is clear. Do not retry automatically if the request or charging status is unclear.\n\n## Step 3 — Present the Contact List\n\n### Filters Applied\n\nShow the filters used in user-friendly language.\n\n| Filter | Value |\n|--------|-------|\n| ... | ... |\n\n### Contact List\n\nFor multiple contacts, use the following fields:\n\n| # | Name | Title | Company | Location | LinkedIn |\n|---|------|-------|---------|----------|----------|\n\n- Present the contacts returned by LeadContact for the applied filters. Do not remove or reclassify them based only on title variations or missing display fields.\n- If a contact clearly contradicts an explicit criterion, keep it visible and briefly note the discrepancy. Do not silently discard it or automatically search for a replacement.\n- Show optional columns such as Industry, Company Size, or Skills only when returned values help users compare contacts. Omit any column that is empty for every result. Show applied filters separately from contact fields.\n- Mark individual missing values with `—`.\n- Do not include email addresses or phone numbers unless separately requested and retrieved.\n- Use only professional information returned by LeadContact.\n\n### Summary\n\n- Total matches: use `totalEmployeeCount`, only when provided by the MCP server\n- Results returned: use `returnedCount`, only when provided by the MCP server\n- API Credits charged: use `apiCreditsCharged`, only when provided by the MCP server\n\nUse only counts and charges returned by the MCP server. Present them with user-friendly labels in the user's language. Do not expose the raw field names unless the user explicitly asks for technical or debugging details. Do not calculate values from the requested count or visible rows. If a value is not reported, omit it rather than infer zero.\n\nIf no results are returned, state this clearly and suggest one or two relevant ways to adjust the criteria. Do not change the criteria without confirmation.\n\nIf partial results are returned, show the available results and explain in user-friendly language why the search stopped.\n\nIf API Credits are insufficient, explain the interruption in plain language. Present any completed results and only the actual charge reported by the server. If no charge is reported, omit it rather than infer zero.\n\nIf the selected account has insufficient API Credits and other accounts are connected, tell the user that they may switch accounts and ask them to select which account to use before continuing.\n\nAlternatively, tell the user they can go to the LeadContact dashboard to review their API Credit balance and account details.\n\nDo not automatically switch to another connected account. Do not run the search again until the user explicitly selects another account.\n\nDo not invent missing information or expose internal tool names, parameters, identifiers, or raw system errors.\n\n## Step 4 — Offer a Next Action\n\nOffer one relevant next action, such as:\n\n- Look up a selected contact\n- Continue with more results\n- Refine the search criteria\n\nAfter presenting the results, wait for the user before running a new search or paid lookup. Only retrieve email addresses or phone numbers when explicitly requested.\n"
}