BLU

Returns 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_target_progresses

Lists 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_targets

Prepares 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.

update_weekly_game_plan

Validates 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.

prepare_report_save

Reads 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_chunk

Reads 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.

read_blu_file_pages

Saves 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.

save_report_to_blu_files

Searches 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_blu_file_content

Changes 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_company

Changes 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_active_organization

Changes 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.

set_fiscal_year

Lists 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_context

Returns 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.

list_weekly_game_plan_items

Prepares 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_initiative_progress

Prepares 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_target_progress