confirm_growthpath_write
ChatGPTApplies the GrowthPath proposal identified by operationId after the user confirms it on the card. It can create records or overwrite fields on existing records. Only the card may call this tool.
create_account
ChatGPTOpens an editable create growthpath account draft. It never writes directly, creates an operation or exposes missing-form-field errors before the GrowthPath confirmation card's Review action.
create_contact
ChatGPTOpens an editable create growthpath contact draft. It never writes directly, creates an operation or exposes missing-form-field errors before the GrowthPath confirmation card's Review action.
create_opportunity
ChatGPTOpens an editable create growthpath opportunity draft. It never writes directly, creates an operation or exposes missing-form-field errors before the GrowthPath confirmation card's Review action.
get_account
ChatGPTReturns one account in the selected GrowthPath workspace using the existing CRM detail behavior. Account lifecycle is omitted. accountStatus is the Green/Yellow/Red assessment shown as Status; null means Status: Not set. When presenting embedded activities or recentActivity: Default to List mode: newest-first vertical records, each with bold title, available assignment, full timestamp and timezone, compact original Notes prefix, then available attribution. Keep source wording and order in the short prefix; use an ellipsis when shortened. Target approximately two conversational lines and finish each record after attribution. For Email lists use Email: <subject>, available From/To and Preview: <original Email preview prefix>; request the existing get_account_activity for full Email detail. Example layout (use only actual returned names and values): Service Visit with Jim Smartt Assigned to Jackie Behring 2026-08-10 18:56:11 · Europe/Istanbul Notes: Attendees and Personnel Updates Jim Smartt — Taking over Dean’s processing responsibilities. Rachel Golden — R&D Engineer… Updated by Jackie Behring Additional engagement title example: Virtual Meeting with Dean Nistal (use the actual linked Contact). Apply these rules only to Activity records. For Service Visit, In-Person Meeting, Virtual Meeting and Phone Call/Text, use the title "<activity subject> with <linked Contact full name>" when the real linked Contact is resolved. Match contactId to the same Account's returned Contacts. The linked Contact is distinct from the assigned owner; use its record name rather than inferring a name from notes. When Activity search/detail returns contactId without a label, reuse fetched same-Account Contacts or read get_account once for that Account and reuse its Contacts for all results. If the link is absent or its label remains unresolved, keep the original subject; retain that fallback after the Account read without repeated lookup or per-record queries. When reading get_account only to resolve Contact labels, preserve the requested List/Detail/Summary mode and type-specific Detail, including fetched Email Content; its embedded List default does not replace them. For every explicit summary-only request, place a separate bold Summary heading (or its conversation-language equivalent) immediately above the summary. Use structured notes for non-Email summaries. Email summaries use fetched Email Content, or clearly limited Email Preview when the body is unavailable; never substitute subject/legacy notes for message content. In explicit Summary-only mode include full date/time and timezone; include complete original notes or full Email Content only when the user also requests them. Show timestamps including seconds in the known viewer timezone, otherwise explicitly UTC, preserving the source instant. Use available source labels and omit unavailable names. Present a bounded or filtered count as returned records; disclose omitted records and offer continuation when response length limits the list.
get_account_activity
ChatGPTReturns one account activity only when it belongs to the selected GrowthPath workspace. Default to Detail mode for a non-Email Engagement: show available metadata and full timestamp/timezone, then Formatted Original Notes, then a separate Summary derived from those notes. In Formatted Original Notes format whitespace between existing tokens, and normalize confirmed list-marker glyphs into actual bullets. Indent subitems only when source hierarchy is unambiguous. Recognize a list marker from explicit list position, repeated pattern and source structure. Keep genuine question marks, in-text letter o and ambiguous markers unchanged; never globally replace ? or o. Preserve every word, token order, case, spelling, typo, number, action, owner and punctuation except confirmed list-marker glyphs. Preserve uncertainty instead of semantically guessing or correcting malformed text. Existing source heading words may occupy their own lines. Add no source words or headings, and do not paraphrase or shorten the source. If markers are normalized, an optional short disclosure outside the original-note body may say: List markers and layout normalized; wording preserved. This is wrapper explanation, not source text. Complete default Detail with a separate Summary after Formatted Original Notes, using only facts in the notes. It may paraphrase; it must not invent commitments, owners or dates. If notes are null or empty, state that no notes are available, preserve the raw null/empty source value, and supply no invented summary facts. An explicit summary-only request overrides this Detail default; include Formatted Original Notes only if the user also requests them. For HealthUpdate Detail show the real status transition, actor, full date/time and Status Notes; keep status records distinct from engagement formatting. Summarize only on explicit request. For Email Detail show the actual Subject, From/To and available CC/BCC, full message date/time, assignment, attribution and only real direction/imported-read-only flags. Use returned Email Content as the message source. If only Email Preview is available, label it Preview and state that the complete body is unavailable. Present Email Content as normal readable email paragraphs with regular Markdown typography and automatic soft wrapping to the available width; return the entire provided body by default. Use a visible Email Content heading followed by the original greeting, body paragraphs, earlier correspondence and signature as ordinary email prose. Preserve logical paragraph boundaries, blank paragraph separation, meaningful hard line breaks, wording, order, case and punctuation; visual rows may wrap naturally to the display width. Fenced or plain-text tool source containers are data delimiters, not requested presentation: render their contents as ordinary email paragraphs, never as a user-facing code block, preformatted/monospace panel or Plain text view. Render existing list structure as normal lists while preserving wording; do not invent bullets, new hierarchy or apply engagement marker-repair rules to Email. Include all provided quoted earlier correspondence, signatures, disclaimers and confidentiality footer; do not omit them for readability. Honor explicit latest-message-only, exclusion or summary-only requests and clearly label the resulting narrower coverage. If response length prevents returning all provided content, identify the actual omitted portion, disclose partial coverage and offer continuation; never call a partial body complete. Preserve the resulting tool text rather than promising pixel-identical spacing from the original HTML/CSS. Show a linked Contact only when resolved by contactId against same-Account Contacts, not inferred from From/To; preserve an available Next Action Date as a calendar date. Email Detail uses Email Content rather than Formatted Original Notes; provide a Summary only on explicit request, based on the fetched Email Content or clearly limited Preview. An explicit summary-only request overrides default Email Detail: provide the labeled Sum…
get_company_info
ChatGPTReturns a BLU company name, vision, mission, and values after checking that the authenticated user may access it. Also persists the resolved organization, company, and fiscal year as the active context for subsequent BLU requests.
get_contact
ChatGPTReturns one contact only when it belongs to the selected GrowthPath workspace.
get_context
ChatGPTLists the BLU organizations, companies or teams, and fiscal years available to the user in an interactive context widget, and lets the user choose which values subsequent BLU requests should use as the saved BLU context. Use this tool when the user wants to list or change only their organizations, browse or choose companies or teams, select a fiscal year, or view and edit the organization, company or team, and fiscal year currently selected in the saved BLU context. The widget always shows the current selection before the user edits it. It displays the connected user for reference but does not allow the connected user to be changed. Also use it for broad requests such as "show/list my organizations and companies." For Coach users, the widget lists all accessible organizations and loads the available companies or teams for the selected organization. For other users, the organization remains fixed. The selected organization, company or team, and fiscal year are saved as the active context for the authenticated BLU user and OAuth client, and subsequent BLU tools use that context by default. Prefer this tool over list_organizations and list_companies for broad workspace-browsing or workspace-selection requests. Use the list tools directly only when the user explicitly requests plain-text records, name resolution, comparison, or an exhaustive inventory. When the widget is rendered, do not repeat workspace details in the assistant message. Provide only a brief confirmation such as "Here is your BLU workspace." The widget is the source of the detailed workspace view. Also persists the resolved organization, company, and fiscal year as the active context for subsequent BLU requests.
get_crm_reference_options
ChatGPTReturns active GrowthPath reference options for the selected workspace.
get_initiative_progress
ChatGPTReturns one BLU initiative progress period and renders the initiative progress widget. Use this when the user asks to view an initiative's progress, current progress, latest progress, or progress for a specific month. When the widget is rendered, do not repeat initiative progress details in the assistant message. Provide only a brief confirmation such as "Here is the initiative progress." The widget is the source of the detailed initiative progress view. Also persists the resolved organization, company, and fiscal year as the active context for subsequent BLU requests.
get_operation_result
ChatGPTReturns the result of a completed GrowthPath operation in the selected workspace.
get_opportunity
ChatGPTReturns one opportunity only when it belongs to the selected GrowthPath workspace.
get_target_progress
ChatGPTReturns one BLU target progress period and renders the target progress widget. Use this when the user asks to view a target's progress, current progress, latest progress, or progress for a specific month. When the widget is rendered, do not repeat target progress details in the assistant message. Provide only a brief confirmation such as "Here is the target progress." The widget is the source of the detailed target progress view. Also persists the resolved organization, company, and fiscal year as the active context for subsequent BLU requests.
get_weekly_game_plan_data
ChatGPTReturns the authenticated user's Weekly Game Plan as internal source data for composing another answer or artifact. Uses the current week unless week and year are provided. Use this only when Weekly Game Plan context is needed for a report, summary, comparison, planning, analysis, recommendation, or AI-drafted Weekly Game Plan suggestion. Also persists the resolved organization, company, and fiscal year as the active context for subsequent BLU requests.
list_blu_files
ChatGPTLists files the authenticated user may access in BLU organization storage, including each file ID, parent folder ID, name, and folder path. Also persists the resolved organization, company, and fiscal year as the active context for subsequent BLU requests.
list_companies
ChatGPTLists companies or teams the authenticated BLU user may access in the selected conversation context.
list_eligible_crm_users
ChatGPTLists active CRM users eligible in the currently selected GrowthPath workspace.
list_individual_goals
ChatGPTLists the authenticated user's individual goals in the active organization. Uses the selected fiscal year unless fiscalYear is provided. The result contains structured individual goal rows that must be shown to the user. Present multiple individual goals as a compact table and never return only an introductory sentence or result count. Also persists the resolved organization, company, and fiscal year as the active context for subsequent BLU requests.
list_initiative_progresses
ChatGPTReturns BLU initiative progress entries for a fiscal month range. Use this when the user asks to list, compare, summarize, or view multiple progress updates for one initiative across a period range. If startPeriod and endPeriod are omitted, the tool returns the latest six fiscal months based on recorded progress in the selected fiscal year. Also persists the resolved organization, company, and fiscal year as the active context for subsequent BLU requests.
list_initiatives
ChatGPTLists initiatives for the company selected in this conversation context. Uses the selected fiscal year unless fiscalYear is provided. The result contains structured initiative rows that must be shown to the user. Present multiple initiatives as a compact table and never return only an introductory sentence or result count. Also persists the resolved organization, company, and fiscal year as the active context for subsequent BLU requests.
list_organizations
ChatGPTLists organizations the authenticated BLU user may select. Coaches only receive organizations assigned to them.
list_target_progresses
ChatGPTReturns BLU target progress entries for a fiscal month range. Use this when the user asks to list, compare, summarize, or view multiple progress updates for one target across a period range. If startPeriod and endPeriod are omitted, the tool returns the latest six fiscal months based on recorded progress in the selected fiscal year. Also persists the resolved organization, company, and fiscal year as the active context for subsequent BLU requests.
list_targets
ChatGPTLists targets for the company selected in this conversation context. Uses the selected fiscal year unless fiscalYear is provided. The result contains structured target rows that must be shown to the user. Present multiple targets as a compact table and never return only an introductory sentence or result count. Also persists the resolved organization, company, and fiscal year as the active context for subsequent BLU requests.
list_weekly_game_plan_items
ChatGPTReturns the authenticated user's weekly game plan and renders the Weekly Game Plan widget. Uses the current week unless week and year are provided. Always use this for direct user-facing Weekly Game Plan display requests, including "list my WGP items", "list my weekly game plan items", "show my weekly game plan", "view my weekly game plan", "open my weekly game plan", todo items, completed items, or 30-60-90 Day Plan. Do not use this as source data for reports, summaries, comparisons, planning, analysis, or AI-drafted weekly game plan suggestions. Use get_weekly_game_plan_data for those data-only workflows so no UI card is opened. When the widget is rendered, do not repeat weekly game plan details in the assistant message. Provide only a brief confirmation such as "Here is the weekly game plan." The widget is the source of the detailed weekly game plan view. Also persists the resolved organization, company, and fiscal year as the active context for subsequent BLU requests.
log_account_activity
ChatGPTOpens an editable log growthpath account activity draft. It never writes directly, creates an operation or exposes missing-form-field errors before the GrowthPath confirmation card's Review action.
prepare_growthpath_write
ChatGPTValidates the GrowthPath confirmation card form data and prepares a proposed change for the user to review. It does not apply changes to GrowthPath records. Only the card may call this tool.
prepare_report_save
ChatGPTValidates a generated PDF report, stores it temporarily, and returns writable BLU Files folders for the user to choose a destination. Call this after the user approves the report content. Also persists the resolved organization, company, and fiscal year as the active context for subsequent BLU requests.
read_blu_file_chunk
ChatGPTReads one bounded cached chunk of extracted BLU file text. Use this after list_blu_files when the user asks to inspect, summarize, or analyze a BLU file. The first call waits up to 30 seconds for extraction before returning processing. Continue with nextCursor only when more file context is needed; do not read every chunk by default. Also persists the resolved organization, company, and fiscal year as the active context for subsequent BLU requests.
read_blu_file_pages
ChatGPTReads extracted BLU file text for an exact page range from the page cache. Use this after list_blu_files when the user asks for a specific page or page range, such as the first page. The first call waits up to 30 seconds for extraction before returning processing. For broad summaries or long sequential reading, prefer read_blu_file_chunk or search_blu_file_content. Also persists the resolved organization, company, and fiscal year as the active context for subsequent BLU requests.
resolve_growthpath_form_options
ChatGPTReserved for the GrowthPath confirmation card. It refreshes dependent options after a card selection changes.
save_report_to_blu_files
ChatGPTSaves an approved prepared PDF report draft to a selected writable BLU Files folder. Use only after prepare_report_save. Also persists the resolved organization, company, and fiscal year as the active context for subsequent BLU requests.
search_account_activities
ChatGPTSearches active account activities only in the currently selected GrowthPath workspace. Returns up to 25 records by default, at most 50; the returned count is not a total-history count. Never present bounded or filtered results as the complete history. Default to List mode: newest-first vertical records, each with bold title, available assignment, full timestamp and timezone, compact original Notes prefix, then available attribution. Keep source wording and order in the short prefix; use an ellipsis when shortened. Target approximately two conversational lines and finish each record after attribution. For Email lists use Email: <subject>, available From/To and Preview: <original Email preview prefix>; request the existing get_account_activity for full Email detail. Example layout (use only actual returned names and values): Service Visit with Jim Smartt Assigned to Jackie Behring 2026-08-10 18:56:11 · Europe/Istanbul Notes: Attendees and Personnel Updates Jim Smartt — Taking over Dean’s processing responsibilities. Rachel Golden — R&D Engineer… Updated by Jackie Behring Additional engagement title example: Virtual Meeting with Dean Nistal (use the actual linked Contact). Apply these rules only to Activity records. For Service Visit, In-Person Meeting, Virtual Meeting and Phone Call/Text, use the title "<activity subject> with <linked Contact full name>" when the real linked Contact is resolved. Match contactId to the same Account's returned Contacts. The linked Contact is distinct from the assigned owner; use its record name rather than inferring a name from notes. When Activity search/detail returns contactId without a label, reuse fetched same-Account Contacts or read get_account once for that Account and reuse its Contacts for all results. If the link is absent or its label remains unresolved, keep the original subject; retain that fallback after the Account read without repeated lookup or per-record queries. When reading get_account only to resolve Contact labels, preserve the requested List/Detail/Summary mode and type-specific Detail, including fetched Email Content; its embedded List default does not replace them. For every explicit summary-only request, place a separate bold Summary heading (or its conversation-language equivalent) immediately above the summary. Use structured notes for non-Email summaries. Email summaries use fetched Email Content, or clearly limited Email Preview when the body is unavailable; never substitute subject/legacy notes for message content. In explicit Summary-only mode include full date/time and timezone; include complete original notes or full Email Content only when the user also requests them. Show timestamps including seconds in the known viewer timezone, otherwise explicitly UTC, preserving the source instant. Use available source labels and omit unavailable names. Present a bounded or filtered count as returned records; disclose omitted records and offer continuation when response length limits the list.
search_accounts
ChatGPTSearches accounts in the selected BLU GrowthPath workspace using the existing CRM list behavior. Account lifecycle is omitted. accountStatus is the Green/Yellow/Red assessment shown as Status; null means Status: Not set.
search_blu_file_content
ChatGPTSearches cached extracted BLU file chunks and returns the most relevant passages. Use this for targeted questions about a large file instead of retrieving the whole file. The first call waits up to 30 seconds for extraction before returning processing. Current implementation uses keyword search; semantic or hybrid modes may be added later without changing the response shape. Also persists the resolved organization, company, and fiscal year as the active context for subsequent BLU requests.
search_contacts
ChatGPTSearches contacts only in the currently selected BLU GrowthPath workspace.
search_opportunities
ChatGPTSearches opportunities across all stages by default, only in the currently selected BLU GrowthPath workspace. Apply a Stage filter only when explicitly requested. status is the Green/Yellow/Red color assessment; Stage and Sales Status remain separate.
set_active_company
ChatGPTChanges the company or team selected for the authenticated BLU user and OAuth client after checking BLU permissions. Also persists the resolved organization, company, and fiscal year as the active context for subsequent BLU requests.
set_active_organization
ChatGPTChanges the organization selected for the authenticated BLU user and OAuth client. Intended for Coach and Global Admin scenarios. Also persists the resolved organization, company, and fiscal year as the active context for subsequent BLU requests.
set_fiscal_year
ChatGPTChanges the active fiscal year saved for the authenticated BLU user and OAuth client. Also persists the resolved organization, company, and fiscal year as the active context for subsequent BLU requests.
update_account
ChatGPTOpens an editable update growthpath account draft. It never writes directly, creates an operation or exposes missing-form-field errors before the GrowthPath confirmation card's Review action. Requires id (the selected Account ID). Read the selected account to resolve its identifier before opening the draft.
update_account_activity
ChatGPTOpens an editable update growthpath account activity draft. It never writes directly, creates an operation or exposes missing-form-field errors before the GrowthPath confirmation card's Review action. Requires both id (the selected Activity ID) and accountId (its parent Account ID). Read the selected activity to resolve both identifiers before opening the draft.
update_account_status
ChatGPTOpens an editable update growthpath account health draft. It never writes directly, creates an operation or exposes missing-form-field errors before the GrowthPath confirmation card's Review action. Requires id (the selected Account ID). Read the selected account to resolve its identifier before opening the draft.
update_contact
ChatGPTOpens an editable update growthpath contact draft. It never writes directly, creates an operation or exposes missing-form-field errors before the GrowthPath confirmation card's Review action. Requires id (the selected Contact ID). Read the selected contact to resolve its identifier before opening the draft.
update_initiative_progress
ChatGPTPrepares an initiative progress update for user confirmation. Never set confirmed=true yourself; only the confirmation card may submit the confirmed update. Confirmed updates can overwrite an existing progress entry. Also persists the resolved organization, company, and fiscal year as the active context for subsequent BLU requests.
update_opportunity
ChatGPTOpens an editable update growthpath opportunity draft. It never writes directly, creates an operation or exposes missing-form-field errors before the GrowthPath confirmation card's Review action.
update_opportunity_status
ChatGPTOpens an editable update the health check for a growthpath opportunity draft. It never writes directly, creates an operation or exposes missing-form-field errors before the GrowthPath confirmation card's Review action.
update_target_progress
ChatGPTPrepares a target progress update for user confirmation. Never set confirmed=true yourself; only the confirmation card may submit the confirmed update. Confirmed updates can overwrite an existing progress entry. Also persists the resolved organization, company, and fiscal year as the active context for subsequent BLU requests.
update_weekly_game_plan
ChatGPTPrepares a weekly game plan update for user confirmation. The items and 30-60-90 Day Plan note input prefill the confirmation card. If called without changes, it returns the current plan for the selected week. If the user asks AI to generate or suggest a weekly game plan, first gather planning context from the previous week's Weekly Game Plan, company initiatives, company targets, and the user's individual goals, then call this tool with proposed items and confirmed omitted. If the user asks AI to create, generate, add, or update only the 30-60-90 Day Plan, call this tool with the proposed 30-60-90 Day Plan in note and confirmed omitted. Items may be omitted when only the 30-60-90 Day Plan is being proposed. If the user provides their own weekly game plan items or wants to create or edit the plan manually, do not proactively gather or add that planning context. Call this tool to open the confirmation card with only the user's provided content. If the user wants to create a Weekly Game Plan manually and has not provided items or a 30-60-90 Day Plan yet, call this tool with note set to an empty string and confirmed omitted so the editable card opens. Never set confirmed=true yourself; only the confirmation card may submit the confirmed update. Confirmed updates can replace the saved weekly items or 30-60-90 Day Plan note. When the widget is rendered, do not repeat weekly game plan details in the assistant message. Provide only a brief confirmation. The widget is the source of the detailed plan and confirmation flow. Also persists the resolved organization, company, and fiscal year as the active context for subsequent BLU requests.