# com.getfreedomos/freedom-mcp (remote · twuluxmoognlwtmaoqgo.supabase.co) Business-ops MCP for FreedomOS — finance, OKRs, customer scoring, AI agents, content. 250+ tools. - Trust score: 67/100 (medium) - Change this week: +10 - Registry status: active - Liveness: live - Owner verified: no - Last scored: 2026-08-04 ## Components - remote · `twuluxmoognlwtmaoqgo.supabase.co`: 67/100 (this document), [markdown](https://verifymcp.io/servers/com-getfreedomos-freedom-mcp/functions-v1-freedom-mcp.md), [page](https://verifymcp.io/servers/com-getfreedomos-freedom-mcp/functions-v1-freedom-mcp) ## Channel facts - Endpoint: `https://twuluxmoognlwtmaoqgo.supabase.co/functions/v1/freedom-mcp` - Transports: `streamable-http` - Auth: `required` - Version: `1.0.0` ## Trust breakdown How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog) Scored 2026-08-04. - **Endpoint Security**: 89/100 - The endpoint's TLS certificate is valid, in date, and uses a strong key. - Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token. - HTTPS is enforced; there's no plaintext access path. - The HSTS (Strict-Transport-Security) header is present. - DNSSEC check failed: this domain isn't protected by DNSSEC. - **Transport & Reachability**: 100/100 - Verified streamable-http transport via a live MCP handshake. - **Schema Quality & AI Usability**: 29/100 - AI-judged instruction clarity (poor). - Context-footprint check failed: tool/resource definitions use about 47688 tokens (~200/item across 238 items; 238 tools + 0 resources), over budget; trim descriptions and params. - Usage-examples check failed: none of the tools include examples. - **Stability & Change Management**: 30/100 - Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses. - **Tool Coverage**: 100/100 - 100% of tools have a non-trivial description (not blank, and not just the tool's name). - 99% of tool parameters carry a description. - **Capabilities**: 20/100 - Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. ## Install ### Claude ```bash claude mcp add --transport http com-getfreedomos-freedom-mcp https://twuluxmoognlwtmaoqgo.supabase.co/functions/v1/freedom-mcp ``` ### Codex ```toml [mcp_servers.com-getfreedomos-freedom-mcp] url = "https://twuluxmoognlwtmaoqgo.supabase.co/functions/v1/freedom-mcp" ``` ### opencode ```json { "$schema": "https://opencode.ai/config.json", "mcp": { "com-getfreedomos-freedom-mcp": { "type": "remote", "url": "https://twuluxmoognlwtmaoqgo.supabase.co/functions/v1/freedom-mcp", "enabled": true } } } ``` ### OpenClaw ```bash openclaw mcp add com-getfreedomos-freedom-mcp --url https://twuluxmoognlwtmaoqgo.supabase.co/functions/v1/freedom-mcp --transport streamable-http ``` ### Hermes ```yaml mcp_servers: com-getfreedomos-freedom-mcp: url: "https://twuluxmoognlwtmaoqgo.supabase.co/functions/v1/freedom-mcp" ``` ### Other ```json { "mcpServers": { "com-getfreedomos-freedom-mcp": { "type": "http", "url": "https://twuluxmoognlwtmaoqgo.supabase.co/functions/v1/freedom-mcp" } } } ``` The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs. ## Changelog Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims. ### 2026-08-04 (score 67, +1) No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes. ### 2026-08-02 (score 66, +1) No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes. ### 2026-08-01 (score 65, +1) - [security] Tool “run_tactic” rewrote its description, which is the text the model reads - [functional] New tool “create_play_from_activity” - [cosmetic] “run_tactic” added an optional parameter “suggest_only” - [cosmetic] “run_tactic” reworded the description of “tactic_title” - [cosmetic] “run_tactic” reworded the description of “tactic_id” ### 2026-07-31 (score 64, +17) - [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server ### 2026-07-30 (score 47, −10) - [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server ### 2026-07-29 (score 57, 0) - [security] Tool “submit_product_request” rewrote its description, which is the text the model reads - [security] Tool “report_feedback” rewrote its description, which is the text the model reads - [cosmetic] “submit_product_request” reworded the description of “kind” - [cosmetic] “hire_agent_with_context” reworded the description of “first_72_hours” - [cosmetic] “hire_agent_with_context” reworded the description of “obsession” ### 2026-07-28 (score 57, +1) No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes. ### 2026-07-27 (score 56, 0) - [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server ## MCP tools (238) ### `grant_agent_tool` (~230 tokens) Grant ONE specific tool to an agent's loadout (tool_access). Use when an operator says "give the tool" / "let use ". The tool name is validated against the live registry at write time — phantom names are rejected, deprecated names auto-map to their successor. For wholesale capability re-derivation use recalibrate_agent_jd instead; connector tools auto-provision on connection. [sensitive-tier — first use may require a manager's approval; a from-now-on approval makes future calls seamless, a just-once approval re-asks next time.] Input parameters: - `agent_id` (string, required): UUID of the agent receiving the tool. Use get_team_roster to find IDs. - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `reason` (string): Optional one-line why — stored in the audit record on the agent's JD. - `tool_name` (string, required): Exact registry name of the tool to grant (e.g. "capture_idea"). ### `revoke_agent_tool` (~192 tokens) Remove ONE specific tool from an agent's loadout (tool_access). Use when an operator says "take away from " — or to clean a phantom/stale name out of a loadout (unresolvable names ARE removable here, unlike grant). Reports honestly when the name was not present, and when the tool is a universal base tool the runtime keeps available regardless. [write-tier — first use may require a manager's approval; a from-now-on approval makes future calls seamless, a just-once approval re-asks next time.] Input parameters: - `agent_id` (string, required): UUID of the agent. Use get_team_roster to find IDs. - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `tool_name` (string, required): Exact loadout entry to remove (phantom/stale names allowed). ### `search_connector_registry` (~143 tokens) Search the vetted connector registry for an external integration (MCP connector) you need but that is not yet connected. Returns ONLY FreedomOS-allowlisted connectors (e.g. ad platforms, analytics) — never the open internet. Use this when you hit a capability gap, then call request_connector with the name to ask the operator to connect one. Input parameters: - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `query` (string): Optional keyword to filter by name or capability (e.g. "ads", "amazon", "analytics"). Omit to list the whole vetted catalog. ### `request_connector` (~215 tokens) Request that the operator connect an external integration (MCP connector) so you can use its tools. Provide the connector name from search_connector_registry and a short reason for the capability gap it closes. Creates a one-click approval card for the operator. If the connector is NOT on the vetted allowlist, it becomes a "vet this connector" request instead. This does not connect anything by itself and never spends money. [sensitive-tier, initiates a multi-step agent process — first use may require a manager's approval; a from-now-on approval makes future calls seamless, a just-once approval re-asks next time.] Input parameters: - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `connector` (string, required): Name of the connector to request (from search_connector_registry, e.g. "Amazon Ads"). - `reason` (string): Why you need it — the capability gap it closes (e.g. "run the KDP book ad campaign"). ### `get_team_pulse` (~137 tokens) Get a real-time snapshot of team output volume, pending approvals, and founder load. Shows cards per agent, approval velocity, oldest pending items, and load trends. Use this to detect if the founder is being overwhelmed, if agents are producing too much or too little, or if cards are piling up without action. Input parameters: - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `company_id` (string): Company ID to check. Usually auto-injected from context. - `days` (number): Lookback window in days (default: 7) ### `get_activity_health` (~111 tokens) Audit all agent activities for staleness, business outcome alignment, and cross-agent overlap. Shows per-activity run count, quality scores, approval rates, and flags activities that may need retirement or adjustment. Use this to apply first principles: question every activity before optimizing it. Input parameters: - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `company_id` (string): Company ID to audit. Usually auto-injected from context. ### `get_command_center_items` (~228 tokens) List Command Center cards for the company (pending by default; pass status_filter for approved/denied/snoozed/all). Shows what needs decisions — approvals, reviews, proposals. Returns card title, source agent, priority, age in days, task type, approval_status, available_actions (live decide moves), resolution_progress (PR/builder in-flight), and a content PREVIEW only — use get_command_center_item with an id for a card's full content. Pending mode is ranked most-actionable first and carries a `featured` field naming the single card the operator's rail features first, with the true reason it leads; other status filters (including 'all') return chronological oldest-first with no featured verdict. Input parameters: - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `limit` (number): Max items to return (default: 25) - `status_filter` (string): Filter by status. Default: "pending". Options: pending, approved, denied, snoozed, all ### `get_command_center_item` (~124 tokens) Read ONE Command Center card by id — full description, full deliverable content, and full context payload, in ANY status (pending, approved, denied, snoozed). THE tool for retrieving what an already-decided card actually said, e.g. the approved package text a follow-up run needs. Input parameters: - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `item_id` (string, required): UUID of the Command Center card (from get_command_center_items or a prior card reference) ### `decide_command_center_item` (~335 tokens) Approve or deny a Command Center card. This processes the decision through the full approval pipeline including trust scoring, autopilot evaluation, skill learning, and deliverable queue progression. [sensitive-tier, initiates a multi-step agent process — first use may require a manager's approval; a from-now-on approval makes future calls seamless, a just-once approval re-asks next time.] Input parameters: - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `decision` (string, required): The decision: approved, denied, snoozed, or dismissed (dismissed = honest acknowledgment of a blocked_on_you card — never resolves it) - `feedback` (string): Optional feedback, especially important for denials. Be specific. - `grant_mode` (string): Capability-approval (mcp_tool_call) cards only: 'once' runs the approved call WITHOUT granting the capability for future calls (the next identical call asks again); 'standing' (the default when omitt… - `item_id` (string, required): UUID of the Command Center card to decide on - `revise` (boolean): revise:true with decision:"denied" sends the card back to the producing agent to redo with your feedback (feedback required in that case) — nothing publishes. Re-runs the originating activity and re-… ### `trigger_agent_activity` (~217 tokens) Trigger a specific agent to run a specific activity immediately. This dispatches the work and returns — it does not wait for the activity to complete. Use this to direct agents to take action. [sensitive-tier, initiates a multi-step agent process — first use may require a manager's approval; a from-now-on approval makes future calls seamless, a just-once approval re-asks next time.] Input parameters: - `activity_name` (string, required): Name of the activity to run (e.g. "weekly_content_report") - `agent_name` (string, required): Name of the agent to trigger (e.g. "Aiko") - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `reason` (string): Optional. A specific instruction for THIS run only — e.g. "only reconcile the X reply queue, skip everything else". When given, it becomes this run's goal and takes priority over the activity's stand… ### `run_tactic` (~281 tokens) Run a saved Play (growth_tactics) for the company operator or agent — dispatch the next unit as a one-off draft activity, or dry-run a Play brief with suggest_only. Use when the operator or agent should execute an Agreed play this cycle (same owner as Focus “Run play”), or preview cast/steps/cost without spend. Structured plays require plan Agree before dispatch; suggest_only does not. [sensitive-tier, initiates a multi-step agent process — first use may require a manager's approval; a from-now-on approval makes future calls seamless, a just-once approval re-asks next time.] Input parameters: - `agent_name` (string): Optional: override which agent runs it (else resolved from the tactic's lane or assignee). - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `suggest_only` (boolean): If true, return Play execution brief only (who / steps / readiness / estimate) — no dispatch, no spend, no Agree required. Use for Chat/MCP dry-run before Run. - `tactic_id` (string): UUID of the Play/tactic to run (use this or tactic_title). - `tactic_title` (string): Title (or fragment) of the Play/tactic to run (use this or tactic_id). ### `toggle_agent_schedule` (~187 tokens) Pause or resume an agent's scheduled activities — the whole activity plan, or a single activity via activity_name. Pausing stops future scheduler-dispatched runs until resumed; manual trigger_agent_activity still works and in-flight runs are not affected. [sensitive-tier, initiates a multi-step agent process — first use may require a manager's approval; a from-now-on approval makes future calls seamless, a just-once approval re-asks next time.] Input parameters: - `action` (string, required): pause or resume - `activity_name` (string): Optional: pause/resume only this one activity (exact name, case-insensitive). Omit to affect the agent's whole activity plan. - `agent_name` (string, required): Name of the agent whose schedule to toggle - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. ### `get_agent_performance` (~118 tokens) Get detailed performance stats for a specific agent: run count, quality scores, approval/denial rates, error count, recent errors with context, and slowest runs. Use this to audit agent health, trace problems, and identify improvement opportunities. Input parameters: - `agent_name` (string, required): Name of the agent to audit - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `days` (number): Lookback window in days (default: 30) ### `add_agent_activity` (~176 tokens) Add ONE activity to an agent's activity plan without regenerating the whole plan. Use to give an agent a new recurring or one-off deliverable. (To rebuild the entire plan, use recalibrate_agent_jd with regenerate_activities=true instead.) [sensitive-tier — first use may require a manager's approval; a from-now-on approval makes future calls seamless, a just-once approval re-asks next time.] Input parameters: - `activity` (object, required): The activity to add. - `agent_id` (string): UUID of the agent. Optional if agent_name is provided. - `agent_name` (string): Name of the agent (e.g. "Aiko"). Provide this or agent_id. - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. ### `update_agent_activity` (~210 tokens) Edit ONE existing activity in an agent's plan — change its name, description, frequency, tools_used, deliverable, or completion_criteria. Surgical alternative to regenerating the whole plan. [sensitive-tier — first use may require a manager's approval; a from-now-on approval makes future calls seamless, a just-once approval re-asks next time.] Input parameters: - `activity_index` (number): 0-based index into the activity plan. Alternative to activity_name. - `activity_name` (string): Exact (case-insensitive) name of the activity to edit. Provide this or activity_index. - `agent_id` (string): UUID of the agent. Optional if agent_name is provided. - `agent_name` (string): Name of the agent. Provide this or agent_id. - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `patch` (object, required): Fields to change. Only the supplied fields are updated. ### `remove_agent_activity` (~223 tokens) Retire ONE activity from an agent's plan. Soft-archive (recoverable): the activity is MOVED to jd_content.archived_activities and removed from the live plan, so the agent stops running it. Never hard-deletes. [sensitive-tier — first use may require a manager's approval; a from-now-on approval makes future calls seamless, a just-once approval re-asks next time.] Input parameters: - `activity_index` (number): 0-based index into the activity plan. Alternative to activity_name. - `activity_name` (string): EXACT (case-insensitive) name of the activity to retire. Provide this or activity_index. - `agent_id` (string): UUID of the agent. Optional if agent_name is provided. - `agent_name` (string): Name of the agent. Provide this or agent_id. - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `reason` (string): Optional reason for retiring (recorded on the archive + audit log). ### `split_agent_activity` (~218 tokens) Split ONE oversized activity into smaller activities (intake + finish) without regenerating the rest of the plan. Use when a run hit the continuation safety backstop while still progressing — the activity is bigger than one deliverable. [sensitive-tier — first use may require a manager's approval; a from-now-on approval makes future calls seamless, a just-once approval re-asks next time.] Input parameters: - `activity_name` (string, required): Exact (case-insensitive) name of the oversized activity to split. - `agent_id` (string): UUID of the agent. Optional if agent_name is provided. - `agent_name` (string): Name of the agent. Provide this or agent_id. - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `pieces` (array): Optional precomputed replacement activities (name, frequency, description, …). When omitted, derived from the source. - `reason` (string): Optional reason recorded on the archive + audit log. ### `create_play_from_activity` (~228 tokens) Draft a Play (growth_tactics with steps + human review) from an oversized agent activity. Does not run the play — operator Agrees on Focus first. Use when a run hit step/continuation limits because the work is multi-unit. [sensitive-tier — first use may require a manager's approval; a from-now-on approval makes future calls seamless, a just-once approval re-asks next time.] Input parameters: - `activity_name` (string, required): Oversized activity to draft a Play from. - `agent_id` (string): UUID of the agent. - `agent_name` (string): Name of the agent. Provide this or agent_id. - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `draft_category` (string) - `draft_custom_instructions` (string) - `draft_goal_impact` (string) - `draft_steps` (array) - `draft_title` (string) - `linked_kr_id` (string) - `reason` (string) ### `get_attention_budget` (~156 tokens) THE tool for the founder's attention budget — the operator-set ceiling on pending review cards before they are 'overloaded' (e.g. "what's my attention budget?", "how many pending cards is too many?", "is my overload threshold the default?"). Returns max_pending_cards and is_default (whether it's still the default 7 or operator-set). This is the ceiling get_team_pulse's overload_signal compares against; it is NOT in company settings or get_company — this is the only tool that has it, so call it directly. For the Chief of Staff / the founder. Input parameters: - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. ### `set_attention_budget` (~260 tokens) Set the founder's attention budget — the maximum pending review cards before they are 'overloaded' (a whole number 1–100; default 7) — for a manager or the founder. Use when the founder (or a manager on their behalf) wants to raise or lower their overload threshold (e.g. "set my overload threshold to 10", "I can handle more pending cards before you flag me", "lower my attention budget to 5"). This is the founder's OWN constraint, so it is gated: an autonomous agent CANNOT change it (surface a recommendation instead); only a human-present company manager can. Always call get_attention_budget first and explain why a change helps the founder. [sensitive-tier — first use may require a manager's approval; a from-now-on approval makes future calls seamless, a just-once approval re-asks next time.] Input parameters: - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `max_pending_cards` (number, required): The new ceiling: pending review cards before the founder is overloaded (whole number, 1–100). - `note` (string): Optional rationale for the change (stored with the budget). ### `create_tactic` (~259 tokens) Create a new growth tactic for the company. Use when user wants to add a tactic, strategy, or action item. [write-tier — first use may require a manager's approval; a from-now-on approval makes future calls seamless, a just-once approval re-asks next time.] Input parameters: - `category` (string, required): Growth category: Leads (lead acquisition), Conversion (leads to customers), Customer Lifetime Value (retention), Time (automation) - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `description` (string): Detailed description of the tactic - `linked_kr_id` (string): Optional key-result id the tactic most advances (validated against the company OKRs). If omitted, the most off-track KR of the bound objective is chosen. - `objective_id` (string): Optional OKR objective UUID to bind this tactic to (validated against this company). If omitted, the binding is auto-inferred from the category→OKR map. - `priority` (string): Priority level - `status` (string): Current status of the tactic - `title` (string, required): The tactic title (e.g., "LinkedIn Content Strategy") ### `generate_tactics` (~268 tokens) Generate AND save 5 grounded growth tactics for a 4-F category, composed from the company mission/vision, OKRs, and ICP customer profile. Persists them as growth_tactics (optionally bound to an objective, key result, and lane). Use when an agent should author concrete tactics for a goal — not just brainstorm. [write-tier — first use may require a manager's approval; a from-now-on approval makes future calls seamless, a just-once approval re-asks next time.] Input parameters: - `category` (string, required): Growth category (4-F spine): flow=Leads, funnel=Conversion, flourish=LTV/retention, freedom=time/automation. - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `lane_id` (string): Optional lane UUID running these tactics (validated against this company). - `linked_kr_id` (string): Optional key-result id (within the bound objective) the tactics most advance. - `objective_id` (string): Optional OKR objective UUID to bind these tactics to (validated against this company). - `userPrompt` (string, required): The focus/request the tactics must address (e.g. "fill the top of funnel for our pharmacy ICP"). ### `get_tactics` (~88 tokens) List tactics for the company. Can filter by category or status. Input parameters: - `category` (string): Filter by category - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `limit` (number): Maximum number of tactics to return (default: 10) - `status` (string): Filter by status ### `update_tactic` (~324 tokens) Update an existing tactic. Can identify by title instead of ID. Can modify title, description (the how-to / instructions), status, category, assigned_to, or re-bind it to an OKR key result (objective_id / linked_kr_id). [write-tier — first use may require a manager's approval; a from-now-on approval makes future calls seamless, a just-once approval re-asks next time.] Input parameters: - `assigned_to` (string): User ID or "me"/"current_user" to assign to - `category` (string): New category - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `description` (string): New description - `linked_kr_id` (string): Key-result id the tactic most advances (validated against the company OKRs; takes precedence over objective_id, and its parent objective is derived). Unresolvable → binding cleared to null. Omit to l… - `objective_id` (string): OKR objective UUID to re-bind this tactic to (validated against this company); its most off-track key result is chosen. Unresolvable → binding cleared to null. Omit to leave the existing binding unto… - `status` (string): New status - `tactic_id` (string): ID of the tactic to update (optional if using tactic_title) - `tactic_title` (string): Title of the tactic to update (use this or tactic_id) - `title` (string): New title ### `delete_tactic` (~129 tokens) Archive a tactic (safe delete - recoverable). Can identify by title instead of ID. [write-tier — first use may require a manager's approval; a from-now-on approval makes future calls seamless, a just-once approval re-asks next time.] Input parameters: - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `tactic_id` (string): ID of the tactic to archive (optional if using tactic_title) - `tactic_title` (string): Title of the tactic to archive (use this or tactic_id) ### `get_company` (~68 tokens) Get detailed company profile including mission, vision, and settings. Input parameters: - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `include_settings` (boolean): Whether to include extended settings in the response. Defaults to true. ### `update_company` (~158 tokens) Update company profile. Can set mission, vision, elevator pitch, logo, website, or other details. [sensitive-tier — first use may require a manager's approval; a from-now-on approval makes future calls seamless, a just-once approval re-asks next time.] Input parameters: - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `elevator_pitch` (string): Brief company description (30 seconds) - `logo_url` (string): URL to company logo image - `mission` (string): Company mission statement - `name` (string): Company name - `vision` (string): Company vision statement - `website_url` (string): Company website URL ### `set_offer` (~263 tokens) Author or update the company's grand slam OFFER — the operator-authored positioning agents ground all outbound in (the offer half of the product layer). Sets `offer` (what the company sells + the transformation it promises) and an optional `target_summary` (who it's for). Capability truth — what the product can and can't actually do — lives in feature_index via create_feature, NOT here; do not list features in the offer. [sensitive-tier — first use may require a manager's approval; a from-now-on approval makes future calls seamless, a just-once approval re-asks next time.] Input parameters: - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `is_regulated` (boolean): Mark this company/product as operating in a REGULATED category (health, medical, financial). When true, the Integrity Gate treats health/efficacy/financial claims in agent-produced outbound as requir… - `offer` (string): The grand slam offer + positioning: what the company sells and the transformation it promises. Operator-authored wisdom-like content. - `target_summary` (string): Optional one-line summary of who the offer is for (the target customer). ### `derive_capability` (~210 tokens) Scan the company's connected source code (its GitHub repo, via the Pulse connection in Smart Tools) and DRAFT a capability list — shipped FEATURES (each citing the file that proves it) plus attempted can't-do LIMITS — for the operator to ratify. It writes NOTHING: only items the operator ratifies become authoritative capability the marketing agents and the Integrity Gate use. Read-only; never executes or sends code. If no repo is connected it tells the operator to connect one in Pulse first. Use to populate or refresh a software product's capabilities without hand-maintaining them. Routing: Operator wants to pull their product's real features from its code (instead of typing them) → use this [sensitive-tier — first use may require a manager's approval; a from-now-on approval makes future calls seamless, a just-once approval re-asks next time.] Input parameters: - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. ### `ratify_capability` (~226 tokens) Persist the operator-CONFIRMED derived features (from derive_capability) into the product capability index as source='derived'. Call ONLY with features the operator has ratified — each then becomes an authoritative capability the marketing agents and the Integrity Gate use. Idempotent (re-ratifying updates in place). Derived can't-do limits are drafted for awareness but authored separately for now. Routing: Operator confirmed the derived features from derive_capability → persist them with this [sensitive-tier — EVERY call needs a manager's approval (per-send human rail): each request queues its own approval card and sends exactly once on approve. There is no standing grant for this tool.] Input parameters: - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `features` (array, required): The operator-confirmed features to persist. Each needs a title; description/solves/evidence/feature_id optional. - `scan_hash` (string): Optional repo commit SHA the derivation came from (recorded for re-scan reconciliation). ### `get_okrs` (~121 tokens) List objectives and key results for the company. Defaults to current year unless year specified or all_years=true. Input parameters: - `all_years` (boolean): Set to true to get OKRs across all years (overrides year filter) - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `limit` (number): Maximum number to return (default: 10) - `year` (number): Filter by year (e.g., 2026). Defaults to current year. ### `create_objective` (~194 tokens) Create a new objective (the O in OKR). Objectives are aspirational goals. After creating one, use generate_key_results to get intelligent, context-aware key result suggestions, then create_key_result to add the best ones. An objective without key results has no way to measure progress. [write-tier — first use may require a manager's approval; a from-now-on approval makes future calls seamless, a just-once approval re-asks next time.] Input parameters: - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `description` (string): Brief context or notes about this objective. Do NOT include key results here. - `title` (string, required): Objective title - a clear, aspirational goal (e.g., "Build & Dogfood Freedom OS") - `year` (number): Year for this objective (e.g., 2026) ### `update_objective` (~226 tokens) Update an existing objective's title, description, or year. Identify by objective_id or objective_title (preferred). If the title matches more than one active objective it refuses and lists them — pass objective_id to disambiguate. Use when the operator wants to rename or reword an objective or move it to another year — the OKR edit door for agents. [write-tier — first use may require a manager's approval; a from-now-on approval makes future calls seamless, a just-once approval re-asks next time.] Input parameters: - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `description` (string): New description for the objective - `objective_id` (string): ID of the objective to update (use this or objective_title) - `objective_title` (string): Title of the objective to update (use this or objective_id) - `title` (string): New title for the objective - `year` (number): New year for the objective (e.g., 2026) ### `create_key_result` (~328 tokens) Add a key result to an objective (the KR in OKR). Key results are measurable outcomes that track progress toward the objective. You can identify the parent objective by title or ID. [write-tier — first use may require a manager's approval; a from-now-on approval makes future calls seamless, a just-once approval re-asks next time.] Input parameters: - `assigned_to` (string): User ID or "me"/"current_user" to assign to - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `current_value` (number): Current progress value (default: 0) - `due_date` (string): Due date (YYYY-MM-DD). Strongly recommended — a KR without one cannot expire or alarm. - `measure_source` (string): Bind current progress to a live data source so it auto-updates daily instead of relying on manual edits. One of: stripe_active_subscribers (active paying Stripe subscriptions), stripe_mrr ($ MRR), cr… - `objective_id` (string): ID of the parent objective (optional if using objective_title) - `objective_title` (string): Title of the parent objective (use this or objective_id) - `target_value` (number): Target value to achieve - `title` (string, required): Key result title (measurable outcome) - `unit` (string): Unit of measurement (e.g., "%", "$", "users", "trees") ### `update_key_result` (~469 tokens) Update a key result for the company operator and any agent owning KR progress (progress, assignment, due date, rename, measure binding). Use when work moves a Key Result and you need to log current value, reassign, rename, or bind a measure source. Prefer key_result_id — the parent objective is resolved from the KR row (no fuzzy title search). Title match is a fallback; resolution uses the EXISTING title even when renaming in the same call. A missing/archived KR returns one terminal recovery with live alternatives — do not retry the same args. [write-tier — first use may require a manager's approval; a from-now-on approval makes future calls seamless, a just-once approval re-asks next time.] Input parameters: - `assigned_to` (string): User ID to assign this KR to. Use "me" or "current_user" to assign to the current user. - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `current_value` (number): Current progress value - `due_date` (string): Due date (YYYY-MM-DD format) - `key_result_id` (string): Stable KR id (preferred). Parent objective is looked up from the KR row across active objectives — do not re-search by fuzzy objective title. - `key_result_title` (string): Title of the key result to update (use this OR key_result_id) — matched against the CURRENT title, even when also renaming - `measure_source` (string): Bind current progress to a live data source (auto-updated daily by the OKR health sweep). One of: stripe_active_subscribers, stripe_mrr, crm_active_leads. Pass "none" to unbind and return the KR to m… - `objective_id` (string): ID of the parent objective (optional when key_result_id is set — id resolves the parent) - `objective_title` (string): Title of the parent objective (optional when key_result_id is set — id resolves the parent) - `start_date` (string): Start date (YYYY-MM-DD format) - `target_value` (number): Target value to achieve - `title` (string): New display title for the key result (rename) ### `generate_key_results` (~160 tokens) Generate intelligent, context-aware key result suggestions for an objective. Uses company mission, vision, financials, and existing KRs to produce high-quality suggestions tied to north star metrics. Returns suggestions that you can then create with create_key_result. [write-tier — first use may require a manager's approval; a from-now-on approval makes future calls seamless, a just-once approval re-asks next time.] Input parameters: - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `objective_id` (string): ID of the objective (optional if using objective_title) - `objective_title` (string): Title of the objective to generate key results for (use this or objective_id) ### `delete_key_result` (~218 tokens) Archive a key result (safe delete — recoverable, never hard-deleted). The KR is moved out of the objective's live list into a recoverable archive. Identify by title (preferred) or ID; optionally scope by parent objective. If the title is ambiguous it refuses and lists the matches — pass an ID to disambiguate. [write-tier — first use may require a manager's approval; a from-now-on approval makes future calls seamless, a just-once approval re-asks next time.] Input parameters: - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `key_result_id` (string): ID of the key result (optional if using key_result_title) - `key_result_title` (string): Title of the key result to archive (use this or key_result_id) - `objective_id` (string): ID of the parent objective (optional) - `objective_title` (string): Title of the parent objective, to scope the search (optional) ### `delete_objective` (~159 tokens) Archive an objective and its key results (safe delete — recoverable, never hard-deleted). Identify by title (preferred) or ID. If the title matches more than one objective it refuses and lists them — pass an ID to disambiguate. [write-tier — first use may require a manager's approval; a from-now-on approval makes future calls seamless, a just-once approval re-asks next time.] Input parameters: - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `objective_id` (string): ID of the objective (optional if using objective_title) - `objective_title` (string): Title of the objective to archive (use this or objective_id) ### `get_setup_state` (~173 tokens) Get the company's core-tenet setup completeness — mission, vision, OKRs, finances, ICP, branding, team, integrations, product, revenue channels, ICP agent model — each as done/empty/blocked/n_a/unknown, with a score, the next best setup step, and the tool to fix each gap. Derived live from current data. Use this to know what a company still needs set up before doing strategy work. WISDOM-FIRST: mission and vision are operator-authored — do NOT author or invent them. OKRs show "blocked" until mission AND vision are set; never invent OKR numbers from an empty wisdom layer — escalate to the operator. Input parameters: - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. ### `read_web_page` (~138 tokens) Read a web page and return its content as clean markdown. Use when the user asks to read, analyze, summarize, or extract information from a specific URL. Also useful for competitor research, checking a website, or reading an article. [sensitive-tier — first use may require a manager's approval; a from-now-on approval makes future calls seamless, a just-once approval re-asks next time.] Input parameters: - `companyId` (string): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `url` (string, required): The full URL to read (must include https:// or http://) ### `draft_tenet_from_signal` (~193 tokens) Draft a company tenet (mission or vision) FROM the company's existing website, for the operator to ratify or edit — instead of asking them to type it into a blank field. Use when a tenet is empty but the company already exists (has a website). Returns a DRAFT proposal with evidence and a confidence level; it writes NOTHING — the operator authors by confirming (Slice-3 update_company). The agent is a mirror, not an author: the draft is grounded in the site, never invented. [sensitive-tier — first use may require a manager's approval; a from-now-on approval makes future calls seamless, a just-once approval re-asks next time.] Input parameters: - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `tenet` (string, required): Which tenet to draft from the website signal ### `list_corpus_inventory` (~104 tokens) List what content material this company already has (knowledge folders like book-1/canon, SME Expert rules, idea_inbox assigned to the workspace). Use BEFORE inventing posts or when the operator asks 'what content do we have?'. Read-only; no LLM. Prefer promote_corpus_to_content next to mint cards. Input parameters: - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. ### `promote_corpus_to_content` (~220 tokens) Mint the NEXT content angle(s) from the company's corpus into content_ideas + Command Center cards. Default count is 1 — do NOT bulk-fill the queue. For day-to-day drafting, prefer list_knowledge / read_knowledge (or list_corpus_inventory) to pull one chapter/passage JIT — that avoids re-tokenizing the whole book. Use promote only when a human-facing card is needed (weekly queue, Held post, operator asked). Faith grain: angles only. Never invent from empty corpus. [write-tier — first use may require a manager's approval; a from-now-on approval makes future calls seamless, a just-once approval re-asks next time.] Input parameters: - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `count` (number): How many angles (1-3, default 1). Prefer 1. - `theme` (string): Optional focus (e.g. "Harness principles", "pharmacy USP") ### `originate_content_ideas` (~169 tokens) Surface CONTENT IDEAS from the company's own corpus and land them in the content pool + cards (same owner as promote_corpus_to_content). Use for 'what should I post', blank-page marketing, or when agents would otherwise invent posts. Never invents from nothing; never drafts faith prose. [write-tier — first use may require a manager's approval; a from-now-on approval makes future calls seamless, a just-once approval re-asks next time.] Input parameters: - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `count` (number): How many ideas (1-3, default 1). Prefer 1 — do not flood the queue. - `theme` (string): Optional focus theme ### `generate_carousel` (~443 tokens) Render a multi-slide image carousel + a LinkedIn-PDF from structured slide copy. Text (including the cited answer) is rendered as REAL, legible text — never the garbled in-frame text AI image/video models produce. Use for value-demonstration B2B content (the cited-answer overlay, peer-proof decks). Produces artifacts only; publish via send_to_user(intent:"publish"). Routing: Carousel / slide deck / LinkedIn PDF / legible cited-answer overlay → use this (the text stays sharp; $0). [write-tier — first use may require a manager's approval; a from-now-on approval makes future calls seamless, a just-once approval re-asks next time.] Input parameters: - `accent_hex` (string): Optional brand accent color as 6-digit hex (e.g. "#F97316"). Pass the tenant's brand color. Defaults per theme. - `brand_label` (string): Optional per-tenant wordmark shown in the slide footer (e.g. your company name). Pass YOUR company's label only. Omit to render no wordmark — never a hardcoded brand. - `caption` (string, required): The post caption that accompanies the carousel. Combined with the slide copy into the gate-text the ICP+Pledge gate scores. - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `folder` (string): Optional Media gallery folder to file this carousel into (freeform name, e.g. "q3-campaign"). Shown as a folder chip on the /media page. Reuse an existing folder name when the work belongs to it. - `format` (string): Slide dimensions. linkedin_portrait (1080×1350, 4:5, default — best LinkedIn engagement), square (1080×1080), wide (1280×720). - `slides` (array, required): Ordered slides. Each: { kicker?, title (required), body?, citation? }. 3–8 ideal, max 12. - `theme` (string): Visual theme. Defaults to brand (dark canvas + accent). ### `get_release_ledger` (~274 tokens) THE tool for "did this piece ship on this channel" — reads the cross-channel Release Ledger, the queryable truth for every confirmed send (x/linkedin/instagram/facebook/threads, hub letters, Beehiiv) written by the publish rail itself at send time. Use this instead of title-matching or a markdown tracking doc when a reconciler or operator asks whether a piece released, where it released, or wants a recent-releases feed. Returns rows plus a per-piece coverage summary (which channels a piece is KNOWN to have shipped on — never a speculative claim about what's missing). Input parameters: - `channel` (string): Filter to one channel. - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `limit` (number): How many recent releases to return, newest first (default 50, max 200). - `piece_key` (string): Filter to one piece's releases (e.g. 'output:', 'idea:', 'hub-letter:'). - `released_by` (string): Filter by who released it: 'agent', 'human', or 'system'. - `since` (string): ISO timestamp lower bound — only releases at/after this time. ### `list_integrations` (~110 tokens) List ALL connected external integrations — MCP servers, OAuth accounts (Google, X, ...), and direct integrations (Xero accounting, Stripe) — and the tools each one powers. Use when user asks about connected services, integrations, or what external tools are available. Input parameters: - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `include_tools` (boolean): Include list of available tools for each integration (default: true) ### `invoke_integration` (~147 tokens) Execute a tool on a connected MCP integration. First use list_integrations to discover available tools. [outbound-tier — EVERY call needs a manager's approval (per-send human rail): each request queues its own approval card and sends exactly once on approve. There is no standing grant for this tool.] Input parameters: - `arguments` (object): Arguments to pass to the tool - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `integration_name` (string, required): Name of the integration (e.g., "stripe", "calendar") - `tool_name` (string, required): Name of the tool to execute on the integration ### `list_my_work` (~168 tokens) List shared work-graph items (lab_work_items) in the current company — the cross-session shared plan. Defaults to items you created or are assigned; pass scope="company" for the whole company graph. Use to see what is queued, blocked, in progress, or done across sessions. Input parameters: - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `limit` (number): Max rows (default 50, max 200). - `scope` (string): mine = items you created or are assigned (default); company = all items in the company. - `status_filter` (string): Optional status filter (queued, blocked, claimed, in_progress, gated, published, verified, failed, cancelled). ### `propose_work` (~241 tokens) Create a new shared work-graph item (lab_work_items) so it is visible and coordinated across sessions and agents. Set depends_on to gate this item behind others (it starts blocked until they complete). Optionally pre-assign to an agent OR a user. [write-tier — first use may require a manager's approval; a from-now-on approval makes future calls seamless, a just-once approval re-asks next time.] Input parameters: - `assignee_agent_id` (string): Optional linnet_agents UUID to assign (agent owner). - `assignee_user_id` (string): Optional auth user UUID to assign (human owner). Cannot be combined with assignee_agent_id. - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `depends_on` (array): Optional array of lab_work_items UUIDs this item is blocked by. - `kind` (string): Kind of work (e.g. task, review, content). Default "task". - `payload` (object): Optional structured detail for the item. - `title` (string, required): Short title of the work item. ### `resolve_work` (~176 tokens) Mark a shared work-graph item resolved — verified (default), published, or cancelled. In the full system, resolving an item cascades to unblock items that depend on it, so this is a process-initiator. Optionally record a verified_outcome. [sensitive-tier, initiates a multi-step agent process — first use may require a manager's approval; a from-now-on approval makes future calls seamless, a just-once approval re-asks next time.] Input parameters: - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `outcome` (object): Optional structured verified_outcome to record. - `status` (string): Terminal status (default "verified"). - `work_item_id` (string, required): UUID of the lab_work_items row to resolve. ### `get_my_profile` (~55 tokens) Get the current user's profile information including name, title, contact info, and personal details. Input parameters: - `companyId` (string): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. ### `update_my_profile` (~515 tokens) Update the current user's profile. Can set name, title, phone, linkedin, location, zone of genius, or quiet hours (the do-not-disturb window for agent push alerts). [write-tier — first use may require a manager's approval; a from-now-on approval makes future calls seamless, a just-once approval re-asks next time.] Input parameters: - `companyId` (string): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `custom_title` (string): Custom display title - `experience_summary` (string): Brief summary of professional experience - `first_name` (string): User's first name - `founder_why` (string): Founder's motivation and purpose - `future_self_note` (string): Note to future self - `holdco_vision` (string): Vision for holding company (executives) - `last_name` (string): User's last name - `linkedin_url` (string): LinkedIn profile URL - `location` (string): City, State or Location - `outbound_routes_to_me` (boolean): The operator's OWN no-manual-outbound preference (S5). true = "I personally do outbound" → the founder-outbound tactic filter is OFF for me; false = "do NOT route founder manual outbound to me" → the… - `phone` (string): Phone number - `profile_image_url` (string): URL to profile image - `quiet_end` (string): Quiet window end, local wall-clock 24h "HH:MM" (e.g. "07:00"). May cross midnight (start after end). - `quiet_hours_enabled` (boolean): Turn the do-not-disturb / quiet-hours window on or off. When on, agent push alerts are held during the window and delivered as one summary at wake. - `quiet_start` (string): Quiet window start, local wall-clock 24h "HH:MM" (e.g. "22:00"). Set together with quiet_end and quiet_tz. - `quiet_tz` (string): IANA timezone for the quiet window, e.g. "America/Los_Angeles". Use the user's own timezone. - `title` (string): Job title (e.g., CEO, CTO, Marketing Director) - `zone_of_genius` (string): What the user is uniquely great at ### `get_my_companies` (~123 tokens) List the companies the current operator can act in (their FreedomOS portfolio), with the operator's role in each plus an `about` line (entity type + what the company is/does). Call this to discover valid companyId values before using company-scoped tools, and use `about` — not the name — to infer WHICH company the user means; if `about` doesn't settle it, ask rather than guess. Input parameters: - `companyId` (string): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. ### `get_my_channel_partner_link` (~137 tokens) Get YOUR channel partner **student share link** (https://getfreedomos.com/start/{slug}) — the classroom start page (copy Claude prompt first, then unlock). Also returns unlockUrl (/p/{slug}) for mid-funnel pay-only if someone already coached. Use when the operator asks for their partner link, UNLOCKED/student share URL, or "how do people join through me". Default students to startUrl, not unlock. Product language: Partner (not affiliate). Input parameters: - `companyId` (string): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. ### `get_my_channel_partner_stats` (~171 tokens) Get YOUR channel partner stats: student share URL (/start/slug), rev-share terms, referral counts by status (pending/joined/activated/credited), and REWARD state (rewardsVested = credits actually granted, rewardsClearing = paid but inside the 7-day vesting window, rewardsVoided = money returned before vesting so they will never land). Report rewardsVested when asked what has been EARNED — a status count is not money. Use when the operator asks how many people came through their link, partner performance, or commission terms. Product language: Partner (not affiliate). Returns empty if not a channel partner. Input parameters: - `companyId` (string): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. ### `get_my_channel_partner_starter_pack` (~141 tokens) Get YOUR classroom starter pack for students: the public share URL (https://getfreedomos.com/start/{slug}) where they copy a one-paste Claude prompt — no skill file, no AirDrop, no terminal. Also returns a short blurb you can text/post and the full student prompt. Use when the operator asks how to send students the FreedomOS handoff, "starter pack", classroom prompt, or UNLOCKED → FreedomOS distribution. Product language: Partner (not affiliate). Input parameters: - `companyId` (string): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. ### `get_partner_cos_onboard` (~192 tokens) Onboard YOUR host coding CoS (Claude Code, Cursor, etc.) to FreedomOS: returns a LIVE MCP tool catalog + a deep-research prompt so the host agent reasons how to maximize profit-per-attention with FO — no fixed labor split. FO is hungry for contacts/ops state; host may build cheaper one-shots; FO wins recurring / not-yet-built / long-running. Includes partner benefit playbooks when you are a channel partner. Re-call whenever FO ships tools. Use on first MCP connect, partner connect, or when the host asks how to use FreedomOS optimally. Input parameters: - `companyId` (string): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `host` (string): Optional host agent label: claude_code | cursor | codex | claude_desktop | other. Default claude_code. ### `get_financial_summary` (~144 tokens) Get P&L summary with revenue, expenses, and net income for the company. For single-month queries (e.g., "Feb free cash flow"), specify month parameter. Input parameters: - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `fiscal_year` (number): The fiscal year to query (default: current year) - `month` (number): Specific month (1-12). If provided, returns data for that month only. If omitted, uses period parameter for range. - `period` (string): Time period for summary when month is not specified (default: ytd) ### `get_projections` (~85 tokens) Get projected future values from financial forecasts. Shows what revenue/expenses are expected. Input parameters: - `account_name` (string): Optional filter to specific account name - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `fiscal_year` (number): The fiscal year to query (default: current year) ### `get_actuals_vs_budget` (~76 tokens) Compare actual financial results to budget/projections. Shows variance analysis. Input parameters: - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `fiscal_year` (number): The fiscal year to query - `period` (string): Time period for comparison ### `get_transactions` (~149 tokens) List company transactions with optional filters. Use for expense tracking, transaction review. Input parameters: - `category` (string): Filter by category - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `date_from` (string): Start date filter (ISO format, e.g., 2026-01-01) - `date_to` (string): End date filter (ISO format) - `is_income` (boolean): Filter to income (true) or expenses (false) - `limit` (number): Max results to return (default: 25, max: 100) - `status` (string): Filter by status ### `search_transactions` (~82 tokens) Search transactions by description. Use when user asks about specific vendors, expenses, or payments. Input parameters: - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `limit` (number): Max results (default: 10) - `query` (string, required): Text to search for in transaction descriptions ### `get_monthly_trends` (~79 tokens) Get month-over-month financial trends. Shows which accounts are increasing/decreasing. Input parameters: - `account_type` (string): Filter by account type - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `fiscal_year` (number): The fiscal year to analyze ### `get_cash_position` (~51 tokens) Get current cash and bank account balances. Use for cash flow questions. Input parameters: - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. ### `get_freedom_target` (~80 tokens) Get the user's freedom target (monthly income goal to quit day job), current FCF progress, estimated freedom date, and assumptions. Use when user asks about financial independence, freedom, or quitting their job. Input parameters: - `companyId` (string): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. ### `update_projection` (~301 tokens) Update projected values for specific accounts and months in the financial plan. Use this when the user asks to change a projection, forecast, or budget number. Only current and future months can be updated — past months with bank actuals are protected. IMPORTANT: If an account already has non-zero values, you must specify mode="add" to add on top of existing values, or mode="set" with force=true to replace. Without these, the tool will return the current values and ask for clarification. [write-tier — first use may require a manager's approval; a from-now-on approval makes future calls seamless, a just-once approval re-asks next time.] Input parameters: - `account_name` (string, required): Account name to update (must match closely, e.g., "Software Revenue", "AWS Hosting"). Use get_projections to see exact names first. - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `fiscal_year` (number): Fiscal year to update (default: current year) - `force` (boolean): When mode="set", skip the overwrite confirmation for non-zero values. Use only when user explicitly wants to replace existing values. - `mode` (string): How to apply the value. "set" = replace existing value (default). "add" = add on top of existing value. - `updates` (array, required): Array of month+value pairs ### `update_finance_note` (~158 tokens) Add or update a note on a P&L account row. Use this to annotate accounts with context like "Includes annual contract renewal" or "One-time consulting fee in June". [write-tier — first use may require a manager's approval; a from-now-on approval makes future calls seamless, a just-once approval re-asks next time.] Input parameters: - `account_name` (string, required): Account name to annotate (fuzzy matched) - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `fiscal_year` (number): Fiscal year (default: current year) - `note` (string, required): Note text to set on the account (empty string to clear) ### `update_transaction_note` (~124 tokens) Add or update a note on a specific transaction. Use after pulling transactions to annotate individual items. [write-tier — first use may require a manager's approval; a from-now-on approval makes future calls seamless, a just-once approval re-asks next time.] Input parameters: - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `note` (string, required): Note text to set on the transaction (empty string to clear) - `transaction_id` (string, required): Transaction ID (from get_transactions output) ### `get_stripe_metrics` (~133 tokens) Get Stripe metrics including average/median LTV, MRR, churn rate, active subscriptions, and an AI-recommended CAC target derived from the company's chosen LTV:CAC strategy (see get_cac_strategy / set_cac_strategy). Returns both blended company-wide metrics and per-plan-tier segments (e.g., Solo vs Team) with segment-specific LTV and CAC targets. Use this to guide customer acquisition spend decisions per customer type. Only works if Stripe is connected. Input parameters: - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. ### `get_top_customers` (~128 tokens) Get top customers ranked by lifetime value (LTV) or revenue from Stripe. Returns name, email, LTV, subscription status, and purchase count for each customer. Use this to identify high-value accounts and retention opportunities. Only works if Stripe is connected. Input parameters: - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `limit` (number): Number of top customers to return (default: 10, max: 25) - `sort_by` (string): Sort criteria (default: ltv) ### `get_subscription_stats` (~80 tokens) Get subscription statistics from Stripe — active, trialing, past-due, and canceled counts plus MRR and ARR. Use alongside get_stripe_metrics for a full revenue picture. Only works if Stripe is connected. Input parameters: - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. ### `get_cac_strategy` (~176 tokens) THE tool for any question about this company's CAC strategy or LTV:CAC ratio — e.g. "is our CAC strategy standard or conservative?", "what's our LTV:CAC ratio?", "what's our max CAC per customer?". Returns the operator's chosen posture — aggressive (2:1), standard (3:1), conservative (4:1), or enterprise (5:1) — and the effective ratio (max CAC = average LTV ÷ ratio). The CAC strategy is NOT in company settings, profile, or financials — do not use get_company or get_financial_summary for it; this is the only tool that has it, so call it directly. Input parameters: - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. ### `set_cac_strategy` (~220 tokens) Change this company's LTV:CAC strategy (the acquisition-spend posture): aggressive (2:1, early-stage growth), standard (3:1, recommended default), conservative (4:1, high churn / mature), or enterprise (5:1, long sales cycles). This governs marketing spend, so it is gated: an autonomous agent CANNOT apply it — surface a recommendation instead. Always call get_cac_strategy first and include a clear rationale when proposing a change. [sensitive-tier — first use may require a manager's approval; a from-now-on approval makes future calls seamless, a just-once approval re-asks next time.] Input parameters: - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `note` (string): Optional rationale for the change (stored with the policy). - `strategy` (string, required): The CAC posture: aggressive (2:1), standard (3:1), conservative (4:1), or enterprise (5:1). ### `set_revenue_channels` (~291 tokens) Declare where this business makes money — stripe, xero, shopify, amazon, ebay, manual invoicing, "none_yet" (pre-revenue), or other (name it). This is OPERATOR TRUTH an agent cannot derive, so it is gated: an autonomous agent CANNOT declare it — only a human (chat) or a graduated MCP operator can. Once declared, agents stop asking to connect Stripe for businesses that don't use it and are routed to the right revenue tool for this company's actual channel(s). Call get_setup_state first — if "Revenue channels" already shows done, only call this again when the operator says it changed. [sensitive-tier — first use may require a manager's approval; a from-now-on approval makes future calls seamless, a just-once approval re-asks next time.] Input parameters: - `channels` (array, required): Any that apply: stripe, xero, shopify, amazon, ebay, manual, none_yet, other. "none_yet" is exclusive — if the business is pre-revenue, pass ONLY ["none_yet"]. - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `other_label` (string): Required when channels includes "other" — the operator's own words for the revenue channel (e.g. "wholesale invoices"). ### `get_next_priority` (~209 tokens) Answer "What should I work on?" in two beats: it leads with the single most-actionable pending Command Center card the operator's rail features first (when the queue has one), then the strategic move synthesized from OKRs, the revenue constraint, and active Tactics. The featured card includes approval_status, available_actions, and resolution_progress (PR/builder in-flight). Call this when the user asks "What should I work on?" or "What's my priority?" Returns focused recommendations with reasoning. Input parameters: - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `focus_area` (string): Optional: focus on a specific tactic category - `override_constraint` (string): Optional operator PIN of the binding revenue constraint. When set, it is SAVED as this company's pin (upsert) and the priority is computed from it instead of the automatic funnel diagnosis. Use only… ### `generate_image_xai` (~460 tokens) Generate or EDIT an image using xAI Imagine. Handles ALL image styles: photorealistic, illustrations, flat graphics, icons, banners, concept art. Supports 2K resolution. Provide reference_image_url or artifact_id to EDIT an existing image. Routing: ALL image generation and editing → use this (2 credits). Handles photorealistic, illustrations, flat graphics, icons, banners. [sensitive-tier — first use may require a manager's approval; a from-now-on approval makes future calls seamless, a just-once approval re-asks next time.] Input parameters: - `artifact_id` (string): ID of an existing artifact from the MEDIA IN THIS CONVERSATION block. The system will automatically resolve a fresh signed URL from storage. Use this when referencing a previously generated image for… - `aspect_ratio` (string): Aspect ratio. Defaults to 1:1. Use "auto" to let the model choose. - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `folder` (string): Optional Media gallery folder to file this image into (freeform name, e.g. "q3-campaign" or "brand-assets"). Shown as a folder chip on the /media page so the operator can find it later. Reuse an exis… - `folder_name` (string): Subfolder name for Drive save (e.g. "Product Shots", "Headshots"). Only used when save_to_drive is true. - `prompt` (string, required): Detailed description of the photorealistic image. Include lighting, camera angle, environment, style, and subject details. - `reference_image_url` (string): URL of an existing image to EDIT (instead of generating from scratch). Use a signed URL from the MEDIA IN THIS CONVERSATION block. When provided, the prompt describes the desired changes to apply to… - `resolution` (string): Output resolution. 1k (default, web quality) or 2k (professional print quality). - `save_to_drive` (boolean): If true, also save the image to Google Drive for permanent storage. Defaults to false. ### `get_team_members` (~75 tokens) Get all team members for the current company. Returns name, email, and role for each member. Use when user asks about team, company members, who is on the team, etc. Input parameters: - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. ### `get_team_roster` (~64 tokens) Get complete AI team roster with roles, specialties, and capacity info. ALWAYS call this BEFORE recommending hires to check for existing coverage. Input parameters: - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. ### `get_agent_outcome_panel` (~153 tokens) Per-agent "what did the compute buy" facts for the operator: trailing-14-day credits, runs (with self-maintenance share), human-accepted vs denied outputs, pending cards, last-accepted date, and a playing-house flag (activity with zero accepted output). Use when the operator asks whether an agent is worth its spend, what an agent has been doing, or why credits are being used — for executives and managers reviewing their AI team. Input parameters: - `agent_id` (string): Optional: limit to one agent (uuid). Omit for the whole team. - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. ### `suggest_next_hire` (~87 tokens) Analyze team gaps and recommend hires or routing to existing agents. Use when user asks "who should I hire", "who to hire next", "what roles do I need", "hiring recommendations", "grow my team", "next hire". Input parameters: - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. ### `hire_agent` (~147 tokens) DEPRECATED: Redirects to interview_for_hire. All hiring now requires context gathering to create a proper JD. Use interview_for_hire directly when user wants to hire someone. [sensitive-tier, initiates a multi-step agent process — first use may require a manager's approval; a from-now-on approval makes future calls seamless, a just-once approval re-asks next time.] Input parameters: - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `role_name` (string, required): The role name to hire - `specialty` (string): Optional specialty domain: marketing, sales, finance, technology, operations ### `deactivate_agent` (~169 tokens) Deactivate (archive) an AI agent/specialist from the team. Use when user says "remove [agent]", "deactivate [agent]", "archive [agent]", "fire [agent]", "delete [agent]". The agent is soft-deleted (is_active=false) and can be reactivated later. Cannot deactivate Linnet (the orchestrator). [sensitive-tier — first use may require a manager's approval; a from-now-on approval makes future calls seamless, a just-once approval re-asks next time.] Input parameters: - `agent_id` (string, required): UUID of the agent to deactivate - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `reason` (string): Optional reason for deactivation ### `interview_for_hire` (~146 tokens) Research the company and return everything needed to propose a specialist hire in ONE shot. Use when the user wants to hire, needs specialist help, or describes a problem a specialist would own. Returns deep pre-researched company context + a single-proposal directive — NOT a multi-turn questionnaire. [sensitive-tier — first use may require a manager's approval; a from-now-on approval makes future calls seamless, a just-once approval re-asks next time.] Input parameters: - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `initial_request` (string, required): What the user originally said they needed help with ### `hire_agent_with_context` (~685 tokens) Hire a new specialist with full hiring context gathered from the interview. Use AFTER walking through the interview phases. The richer the context, the better the agent. [sensitive-tier, initiates a multi-step agent process — first use may require a manager's approval; a from-now-on approval makes future calls seamless, a just-once approval re-asks next time.] Input parameters: - `agent_name` (string): OPTIONAL. The exact display name the user explicitly asked for — a single first name (e.g. "Garth" from "name it Garth" / "call it Garth"). Set this ONLY when the user named the agent; leave unset to… - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `context_and_resources` (string): What the user has already tried, existing tools/data/resources available - `domain_expertise` (string): Role-specific domain knowledge that makes this agent an expert (frameworks, ratios, best practices specific to this role and industry) - `first_72_hours` (array): 3 demand-bound first actions (leads/enroll/outbound/content-to-market/cash/fulfillment). FORBIDDEN: placement audits, governance of inactive agents, fleet ownership maps, agent scoreboards. These bec… - `goal` (string, required): The specific mission this hire will achieve — be as specific as possible, include real numbers - `guardrails` (array): What this agent should NEVER do (e.g., "Never recommend cutting product investment", "Never ignore cash runway below 3 months") - `obsession` (string): The ONE demand-path KPI this agent lives or dies by (leads, enrolls, revenue, cash, customers). Not "agents activated" or team-hygiene metrics. Specific with numbers when possible (e.g., "Close the $… - `personality_traits` (array): Communication style preferences (e.g., "direct", "data-heavy", "encouraging", "concise", "detailed analysis") - `reporting_cadence` (string): How often to send updates: weekly, biweekly, monthly, or realtime - `reports_to_name` (string): Name or role of the team member this agent should report to. Use an existing team member name if one is a natural manager. Say "Linnet" for Chief of Staff, or "founder" for direct-to-founder reportin… - `required_resources` (array): Tools, integrations, or data sources this agent needs. Default documents, briefs, and reports to the FreedomOS Knowledge Base (save_knowledge / read_knowledge — always available, visible in-app); lis… - `role_name` (string, required): A descriptive role name (e.g., "YouTube Growth Specialist", "Cash Flow Analyst", "SEO Content Writer") - `success_metrics` (array, required): Specific, measurable outcomes that define success ### `update_agent_skill` (~328 tokens) Create or update a skill (process/procedure) for an agent. Use when a user says "@Marcus here's how I want you to do the cash forecast" or "change how the CFO does the monthly review" or "here's my process for X". Skills teach agents HOW to perform their activities. [sensitive-tier — first use may require a manager's approval; a from-now-on approval makes future calls seamless, a just-once approval re-asks next time.] Input parameters: - `activity_name` (string): Activity this skill backs (e.g., "Weekly Cash Review"). If provided, the skill will be linked to this activity via skill_id. - `agent_id` (string): UUID of the agent to teach. Optional if agent_name is provided. - `agent_name` (string): Name of the agent (e.g., "Marcus"). Used to look up agent_id if not provided. - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `resources` (array): URLs, doc names, templates, or other resources (e.g., ["company P&L template"]) - `skill_name` (string, required): Short name for the skill (e.g., "13-Week Cash Forecast") - `steps` (array, required): Ordered steps of the process (e.g., ["Pull balances", "Calculate 13-week average", "Flag if runway < 3 months"]) - `tools_used` (array): Tool names referenced in the process (e.g., ["get_cash_position", "create_google_sheet"]) ### `analyze_team_needs` (~118 tokens) Gather comprehensive team and company context for talent strategy analysis. Returns current team composition, growth signals, capability gaps, and integration status. Use when the user asks "what roles am I missing?", "who should I hire next?", "analyze my team", or "what gaps does my team have?". YOU are the strategist — this tool gathers the data, YOU provide the PhD-level talent recommendations. Input parameters: - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. ### `suggest_collaboration` (~173 tokens) Create a cross-agent collaboration request. Use when one agent identifies work that another agent should handle, or when the analysis reveals a gap that could be filled by an existing team member. If the target role doesn't exist on the team, mention it as a hiring opportunity instead. Input parameters: - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `from_agent_name` (string, required): Name of the agent suggesting the collaboration (e.g., "Maya", "Evan") - `priority` (string): How urgent is this collaboration request - `task_description` (string, required): What needs to be done — specific and actionable - `to_agent_name` (string, required): Name of the target agent, or a role description if the agent doesn't exist yet ### `list_scheduled_reports` (~91 tokens) List all scheduled reports for this company, optionally filtered by agent. Use when user asks "what reports are scheduled?", "show me our reports", "what reports does X have?" Input parameters: - `agent_id` (string): Optional: filter reports by a specific agent UUID - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. ### `reassign_reports` (~156 tokens) Reassign all scheduled reports from one agent to another. Use when user says "reassign reports", "transfer reports to [agent]", "move reports from [agent] to [agent]". Useful after deactivating an agent or hiring a replacement. [write-tier — first use may require a manager's approval; a from-now-on approval makes future calls seamless, a just-once approval re-asks next time.] Input parameters: - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `from_agent_id` (string, required): UUID of the agent to transfer reports FROM - `to_agent_id` (string, required): UUID of the agent to transfer reports TO ### `link_agent_okrs` (~204 tokens) Link an agent to one or more company OKRs. This creates a live connection between the agent and the company objectives they are working toward. Their system prompt will include live OKR context (objectives + key results with progress). [write-tier — first use may require a manager's approval; a from-now-on approval makes future calls seamless, a just-once approval re-asks next time.] Input parameters: - `agent_id` (string): UUID of the agent to link OKRs to - `agent_name` (string): Name of the agent (used to look up agent_id if not provided) - `append` (boolean): If true, add to existing linked OKRs. If false (default), replace all linked OKRs. - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `okr_ids` (array, required): Array of OKR UUIDs to link to this agent ### `recalibrate_agent_jd` (~209 tokens) Regenerate an agent's JD using fresh company context. Updates mission, expertise, guardrails, success metrics, and optionally activity plans. Works for both hired agents and Linnet. Use when the company has evolved, an agent needs recalibration, or the user wants to refine an agent's direction. [sensitive-tier — first use may require a manager's approval; a from-now-on approval makes future calls seamless, a just-once approval re-asks next time.] Input parameters: - `agent_id` (string, required): UUID of the agent to recalibrate. Use get_team_roster to find IDs. - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `focus_areas` (string): Optional user guidance for recalibration, e.g. "focus more on SEO" or "add financial analysis" - `regenerate_activities` (boolean): Also regenerate the activity plan (default: false — preserves evolved activities) ### `update_agent` (~221 tokens) Rename a team member or fix its role/title. Updates an agent's display name and/or role/job-title. Use when the user says "rename X to Y", "call this agent Z", or "fix the title". For changing an agent's mission/skills use recalibrate_agent_jd instead. [write-tier — first use may require a manager's approval; a from-now-on approval makes future calls seamless, a just-once approval re-asks next time.] Input parameters: - `agent_id` (string, required): UUID of the agent to update. Use get_team_roster to find IDs. - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `name` (string): New display name — a single first name (e.g. "Garth"). Omit to leave the name unchanged. - `role` (string): New role / job title (e.g. "Agent Deployment & Quality Reviewer"). Do NOT include the agent name. Omit to leave the role unchanged. ### `update_agent_avatar` (~369 tokens) Generate or regenerate AI agent profile avatar(s) for a company's AI team. Use when an operator wants to create, refresh, or restyle one or more agents' profile avatars. Single agent: pass agent_id OR agent_name. Several agents: pass agent_ids[] OR agent_names[] in ONE call. Whole team: pass all:true. The tool regenerates EVERY target itself in a single call (1 credit per agent) and returns the real new signed avatar_url for each. Report ONLY the agents listed in the result's `regenerated` array — never claim or invent an avatar for an agent the tool did not return. [sensitive-tier — first use may require a manager's approval; a from-now-on approval makes future calls seamless, a just-once approval re-asks next time.] Input parameters: - `agent_id` (string): UUID of a single agent to (re)generate an avatar for. - `agent_ids` (array): UUIDs of multiple agents to regenerate in ONE batch call. - `agent_name` (string): Name of a single agent (used to look up the agent when agent_id is not provided). Must resolve to exactly one active agent. - `agent_names` (array): Names of multiple agents to regenerate in ONE batch call. Each name must resolve to exactly one active agent (ambiguous names are returned in `failed`). - `all` (boolean): Set true to regenerate avatars for EVERY active agent in the company. Takes precedence over the id/name params. - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `style` (string): Optional style override (e.g., "pixel-art", "watercolor", "geometric"). Overrides company avatar_theme for this generation. ### `list_features` (~91 tokens) List all product features in the Feature Index. Use when user asks "what features do I have?", "show my features", "what have I built?", or wants to see their product capabilities for marketing. Input parameters: - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `status` (string): Filter by status (default: all) ### `create_feature` (~263 tokens) Add a new feature to the Feature Index. Use when user says "I built X", "add feature Y", "track this capability", or describes a product feature they want to market. Features can later be pushed to Content Pipeline for marketing content. [write-tier — first use may require a manager's approval; a from-now-on approval makes future calls seamless, a just-once approval re-asks next time.] Input parameters: - `category` (string): Category (e.g., "ai", "marketing", "finance", "automation") - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `demo_url` (string): URL to a demo video (Screen Studio, Loom, etc.) - `description` (string): Marketing-ready description of the feature - `feature_id` (string): Unique slug for the feature (e.g., "ai-content-pipeline") - `limits` (string): Current limitations (e.g., "LinkedIn only", "Beta users only") - `solves` (array): Problems/pain points this feature solves (e.g., ["manual posting", "writer's block"]) - `title` (string, required): Display title (e.g., "AI Content Pipeline") ### `update_feature_status` (~143 tokens) Mark a feature as ready for marketing. Use when user says "mark X as ready", "this feature is ready to market", or wants to highlight a feature for marketing content. [write-tier — first use may require a manager's approval; a from-now-on approval makes future calls seamless, a just-once approval re-asks next time.] Input parameters: - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `feature_id` (string, required): The feature_id slug (e.g., "ai-content-pipeline") or UUID - `status` (string, required): New status for the feature ### `update_feature` (~249 tokens) Update fields on an existing Feature Index entry — title, description, category, solves, limits, or demo_url. Use when the user wants to correct or enrich a feature's marketing copy. To change status use update_feature_status; to remove a feature from view use retire_feature — never delete. [write-tier — first use may require a manager's approval; a from-now-on approval makes future calls seamless, a just-once approval re-asks next time.] Input parameters: - `category` (string): Category (e.g., "ai", "marketing", "finance", "automation") - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `demo_url` (string): URL to a demo video (Screen Studio, Loom, etc.) - `description` (string): Marketing-ready description of the feature - `feature_id` (string, required): The feature_id slug (e.g., "ai-content-pipeline") or UUID. - `limits` (string): Current limitations - `solves` (array): Problems/pain points this feature solves - `title` (string): Display title (e.g., "AI Content Pipeline") ### `retire_feature` (~204 tokens) Archive (retire) a feature so it stops showing to readers and agents, or restore a previously retired one. Safe-archive ONLY — never hard-deletes; retiring is fully reversible. Use when a feature is no longer accurate, was replaced, or the user says "remove this feature", "retire X", or "un-retire X". [write-tier — first use may require a manager's approval; a from-now-on approval makes future calls seamless, a just-once approval re-asks next time.] Input parameters: - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `feature_id` (string, required): The feature_id slug (e.g., "ai-content-pipeline") or UUID. - `reason` (string): Optional note on why this feature is being retired. - `restore` (boolean): Set true to un-retire (restore) a previously archived feature. Default false. ### `get_icps` (~170 tokens) Get saved Ideal Customer Profiles (ICPs) from Customer Hunter. Use this when the user asks about their target customer, ideal customer, customer avatar, ICP, or who they should be selling to. Returns structured profiles including nightmare scenario, dream outcome, pain points, financial profile, and tech-savviness — plus class ('customer' or 'partner') and agentProfile (how that customer's own AI assistant participates in buying: tier, agents, surfacesRead, purchasePath). Each profile also returns publicName — the public-facing audience label to use in published copy — NEVER the internal persona name/codename (the "name" field is a private targeting label). Input parameters: - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. ### `update_icp` (~174 tokens) Update specific fields of a saved Ideal Customer Profile (ICP). Only modifies the fields you specify - all other data is preserved. To change the public audience label used in published copy, pass publicName in updates (the public-facing label — NEVER the internal persona name/codename); the internal "name" stays the private targeting label. [write-tier — first use may require a manager's approval; a from-now-on approval makes future calls seamless, a just-once approval re-asks next time.] Input parameters: - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `icp_id` (string, required): The unique ICP ID from get_icps response. - `updates` (object, required): Only the fields to update. Other fields are preserved automatically. ### `create_icp` (~437 tokens) Create a NEW Ideal Customer Profile (ICP) from scratch and save it — no Customer Hunter UI needed. Use this when get_icps returns hasICPs:false (the company has none yet) or to add another target customer profile. To CHANGE an existing ICP, use update_icp instead. [write-tier — first use may require a manager's approval; a from-now-on approval makes future calls seamless, a just-once approval re-asks next time.] Input parameters: - `agentProfile` (object): How this customer's own AI agent participates in buying: { tier: 'ambient' | 'assisted' | 'delegated' | 'builder', agents: string[], surfacesRead: string[], purchasePath: string, autonomyNotes: strin… - `channels` (array): Where they spend attention. - `class` (string): 'customer' (default) or 'partner' — partner = a distribution/affiliate ICP, not an end-buyer. - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `demographics` (object): role, companySize, industry, techStack[]. - `dreamOutcome` (string): The outcome they dream of. - `financialProfile` (object): revenueRange, typicalDealSize, budgetAuthority, buyingBehavior, growthStage, priceSensitivity. - `name` (string, required): Persona name. Required. Used to derive the ICP id/filename. INTERNAL targeting label (may be an evocative codename) — never published. - `nightmareScenario` (string): The 3am problem / nightmare scenario. - `painThemes` (array): Recurring pain themes. - `publicName` (string): The public-facing audience label to use in published copy — NEVER the internal persona name/codename. Plural noun phrase, e.g. "compounding pharmacy owners". Optional — auto-generated from the person… - `techSavviness` (string): Tech comfort level. - `title` (string): One-line descriptor of the persona. ### `delete_icp` (~179 tokens) Delete a saved Ideal Customer Profile (ICP). Mirrors the Customer Hunter UI's delete: deactivates any reviewer agent built from this ICP, strips it from every content pipeline that targets it, then ARCHIVES (does not permanently remove) the ICP file. Use when the user says "delete this ICP", "remove this customer profile", or "get rid of this persona". [sensitive-tier — first use may require a manager's approval; a from-now-on approval makes future calls seamless, a just-once approval re-asks next time.] Input parameters: - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `icp_id` (string, required): The unique ICP ID from get_icps response. - `reason` (string): Optional. Why this ICP is being deleted. ### `capture_idea` (~121 tokens) Capture an idea into the user's Ideas. Use when user shares an idea they want to save for later. [write-tier — first use may require a manager's approval; a from-now-on approval makes future calls seamless, a just-once approval re-asks next time.] Input parameters: - `companyId` (string): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `content` (string, required): The idea content to capture - `source_url` (string): Optional URL if the idea came from a link ### `list_inbox` (~93 tokens) List pending ideas in the user's Ideas. Shows ideas that haven't been triaged yet. Input parameters: - `companyId` (string): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `limit` (number): Maximum number of ideas to return (default: 10) - `status` (string): Filter by status: new (default), parked, or all pending ideas ### `list_workspace_ideas` (~97 tokens) List ideas that have been assigned to this workspace. Shows triaged ideas for the current company. Input parameters: - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `include_promoted` (boolean): Include ideas that have already been promoted to tactics (default: false) - `limit` (number): Maximum number of ideas to return (default: 10) ### `triage_idea` (~164 tokens) Assign an idea to one or more workspaces. Can identify by content snippet, ID, or "newest"/"latest". [write-tier — first use may require a manager's approval; a from-now-on approval makes future calls seamless, a just-once approval re-asks next time.] Input parameters: - `companyId` (string): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `idea_identifier` (string, required): How to find the idea: UUID, content snippet, or "newest"/"latest" for most recent - `workspace_id` (string): Single workspace/company ID (use workspace_ids for multiple) - `workspace_ids` (array): Array of workspace/company IDs to assign the idea to ### `delete_idea` (~123 tokens) Delete an idea from Ideas. Can identify by content snippet, ID, or "newest"/"latest". [write-tier — first use may require a manager's approval; a from-now-on approval makes future calls seamless, a just-once approval re-asks next time.] Input parameters: - `companyId` (string): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `idea_identifier` (string, required): How to find the idea: UUID, content snippet, or "newest"/"latest" for most recent ### `check_my_inbox` (~239 tokens) Check your own agent email inbox (receive-only) for messages sent to your @agents.getfreedomos.com address, and read them. Returns recent unread messages: sender, subject, a safe text snippet, any OTP codes, and login links that are safe to open — reads only YOUR mailbox. Use when a login, sign-in, or verification flow tells you it emailed a one-time code or magic link to your agent address and you need to retrieve it. [sensitive-tier — first use may require a manager's approval; a from-now-on approval makes future calls seamless, a just-once approval re-asks next time.] Input parameters: - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `from_domain` (string): Only return mail whose sender is at this domain (e.g. "getfreedomos.com"). - `limit` (number): Max messages to return (default 10, cap 25). - `since_minutes` (number): Only return mail received within the last N minutes (e.g. 15 for a fresh login code). ### `list_pipelines` (~144 tokens) List all content pipelines (changelogs, team updates, reports, customer newsletters, social posts). Use when user asks about their content automation, "what content am I publishing?", "show my pipelines", or "what outputs are configured". Output types: changelog (public product updates), team_update (internal team email via Freedom OS), report (email to specific recipients), customer_newsletter (external customers - requires user Email MCP like Mailchimp), social_post (x/linkedin/instagram/facebook/threads via the gated publish owner). Input parameters: - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. ### `get_pending_approvals` (~142 tokens) Get CONTENT PIPELINE outputs waiting for approval/publish (changelogs, newsletters, social drafts). IDs are pipeline_outputs UUIDs — use approve_pipeline_item / publish_pipeline_item / request_content_revision. NOT Command Center decision cards — those use get_command_center_items + get_command_center_item + decide_command_center_item. Use when user asks "what content needs my review?", "ready to publish?", or "approval queue" for content. Input parameters: - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `limit` (number): Maximum items to return (default: 10) ### `create_pipeline` (~280 tokens) Create a new content pipeline to automate content creation. Use when user says "set up a changelog", "create a newsletter pipeline", "send team updates", "automate my X posts", or describes input→output automation. Output types: changelog (public product updates), team_update (internal team email via Freedom OS), report (email to specific recipients), customer_newsletter (external customers - requires user Email MCP like Mailchimp), social_post (x/linkedin/instagram/facebook/threads via the gated publish owner). [write-tier — first use may require a manager's approval; a from-now-on approval makes future calls seamless, a just-once approval re-asks next time.] Input parameters: - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `inputs` (object): Input sources to listen to - `name` (string, required): Name for the pipeline (e.g., "Weekly Newsletter", "GitHub to Changelog") - `output` (string, required): Output type: changelog (public), team_update (internal team email), report (specific recipients), customer_newsletter (external - requires Email MCP), social_post (x/linkedin/instagram/facebook/threa… - `persona` (string): Marketing persona to use (alex, elon, or custom ID) ### `update_pipeline` (~258 tokens) Update an existing content pipeline. Use when user says "rename my pipeline", "change the pipeline name", "update pipeline settings", or wants to modify pipeline configuration. Can update name, persona, ICPs, output type, or destination. [write-tier — first use may require a manager's approval; a from-now-on approval makes future calls seamless, a just-once approval re-asks next time.] Input parameters: - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `destination` (string): Where to publish: freedom_os (auto-publish to platform), manual (copy/paste). Social platforms (x/linkedin/instagram/facebook/threads) publish via the gated owner after human approval — instagram ite… - `icp_ids` (array): New list of ICP IDs to target - `name` (string): New name for the pipeline - `output` (string): New output type - `persona` (string): New persona ID to use for transformations - `pipeline_id` (string, required): ID of the pipeline to update (get from list_pipelines) ### `archive_pipeline` (~205 tokens) Archive (or restore) a content pipeline — flips is_active off/on, mirroring the Content Pipeline UI's soft-delete/restore. No data is deleted or cascaded. Use when the user says "archive this pipeline", "pause my newsletter automation", "turn off this pipeline", or "bring back my archived pipeline" (pass restore:true). [write-tier — first use may require a manager's approval; a from-now-on approval makes future calls seamless, a just-once approval re-asks next time.] Input parameters: - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `pipeline_id` (string, required): ID of the pipeline to archive/restore (get from list_pipelines) - `reason` (string): Optional. Why this pipeline is being archived or restored. - `restore` (boolean): Set true to REACTIVATE an archived pipeline instead of archiving it. Default false (archive). ### `submit_content_to_pipeline` (~267 tokens) Submit manual content to a pipeline for transformation. Use when user says "add this to my changelog", "create a newsletter from this", "transform this content", or provides content to be processed. Content will be transformed using the pipeline's persona and ICPs. Social pipelines publish to the pipeline's declared destination (x/linkedin/instagram/facebook/threads — set via update_pipeline; undeclared defaults to x) after human approval; instagram items REQUIRE media_artifact_ids. [write-tier — first use may require a manager's approval; a from-now-on approval makes future calls seamless, a just-once approval re-asks next time.] Input parameters: - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `content` (string, required): Raw content to transform (updates, notes, announcements, etc.) - `media_artifact_ids` (array): Optional. Artifact IDs (image or video, from generate_image_xai / generate_video, same company) to attach as media on this post. Required for visual social posts — the post publishes with this media… - `pipeline_id` (string, required): ID of the pipeline to submit to (get from list_pipelines) ### `approve_pipeline_item` (~184 tokens) Approve a content item for publishing — or REJECT it with approved:false. Use when user says "approve it", "looks good", "publish that" (approve), or "reject it", "drop that duplicate", "don't publish" (approved:false). [sensitive-tier — first use may require a manager's approval; a from-now-on approval makes future calls seamless, a just-once approval re-asks next time.] Input parameters: - `approved` (boolean): Default true. Pass false to REJECT: the item is marked rejected and leaves the approval queue — it never publishes. An explicit false can never approve. - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `item_id` (string, required): ID of the pipeline output to approve (get from get_pending_approvals) ### `request_content_revision` (~165 tokens) Request changes to a content item. Use when user says "revise this", "change the tone", "make it shorter", or provides feedback on pending content. The content will be re-transformed with their feedback. [write-tier — first use may require a manager's approval; a from-now-on approval makes future calls seamless, a just-once approval re-asks next time.] Input parameters: - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `feedback` (string, required): User's feedback on what to change (e.g., "make it shorter", "more professional tone") - `item_id` (string, required): ID of the pipeline output to revise (get from get_pending_approvals) ### `publish_pipeline_item` (~283 tokens) Publish approved INTERNAL content to configured output. ROUTING: team_update sends to all team members via Freedom OS, report sends to specified team member emails, customer_newsletter requires user Email MCP connection (Mailchimp, Resend, etc.), changelog publishes to public changelog page. ⚠️ SOCIAL POSTS (x/linkedin/instagram/facebook/threads) never send from this tool: declare the pipeline destination via update_pipeline and submit via submit_content_to_pipeline — the post queues for operator approval and publishes through the single gated owner on approve (in FreedomOS app chat, send_to_user with intent "publish" queues the same approval). Use when an approved non-social item — changelog, team update, report, or newsletter — is ready to send. [outbound-tier — first use may require a manager's approval; a from-now-on approval makes future calls seamless, a just-once approval re-asks next time.] Input parameters: - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `item_id` (string, required): ID of the approved pipeline output to publish (get from get_pending_approvals, must be approved status) - `recipients` (array): Optional. Specific team member emails to send to (must be in company_members). If not specified, sends to all team members. ### `list_pipeline_learnings` (~141 tokens) Show the style guide and recent revision history for a content pipeline. Use when user asks "what are the learnings for my newsletter?", "show me the style guide", "what feedback have I given?", or "what does it know about my preferences?". Input parameters: - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `output_format` (string): Optional. Filter by output format: changelog, social_post, team_update, newsletter, report. If not specified, shows all formats. - `pipeline_id` (string, required): Pipeline ID (get from list_pipelines) ### `update_pipeline_style_guide` (~191 tokens) Manually add a style rule to a pipeline. Use when user says "always use bullet points", "never include hashtags", "keep it under 100 words", "use more casual tone", or gives general content preferences. [write-tier — first use may require a manager's approval; a from-now-on approval makes future calls seamless, a just-once approval re-asks next time.] Input parameters: - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `output_format` (string, required): Which format this rule applies to: changelog, social_post, team_update, newsletter, report - `pipeline_id` (string, required): Pipeline ID (get from list_pipelines) - `style_rule` (string, required): The style rule to add (e.g., "Use bullet points for lists", "Keep under 150 words") ### `clear_pipeline_learnings` (~155 tokens) Reset all learnings for a pipeline and start fresh. Use when user says "forget what you learned", "start fresh with the style", "reset the learnings", or "clear the feedback history". [write-tier — first use may require a manager's approval; a from-now-on approval makes future calls seamless, a just-once approval re-asks next time.] Input parameters: - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `output_format` (string): Optional. Only clear learnings for a specific format. If not specified, clears all formats. - `pipeline_id` (string, required): Pipeline ID (get from list_pipelines) ### `add_commitment` (~252 tokens) Track a personal commitment, deadline, birthday, appointment, or obligation. ALWAYS use this (not save_knowledge) when the user mentions: birthdays, due dates, deadlines, tax filings, events to plan, gifts to send, things they need to do by a certain date, or anything they want reminded about. Works across all life domains (work, personal, family, home). For supporting context (e.g. gift ideas, who the person is), pair this with save_knowledge scope="personal". [write-tier — first use may require a manager's approval; a from-now-on approval makes future calls seamless, a just-once approval re-asks next time.] Input parameters: - `companyId` (string): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `consequence` (string): What happens if this slips? (optional) - `description` (string): Additional details or notes (optional) - `domain` (string): Life domain: personal, family, home, w2, or company: - `due_date` (string): Due date in YYYY-MM-DD format (optional) - `title` (string, required): What needs to happen ### `list_commitments` (~100 tokens) List the user's active commitments. Shows what's on their plate across all life domains, sorted by due date. Input parameters: - `companyId` (string): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `domain` (string): Filter by domain (optional). E.g., "family", "home", "company:acme" - `include_completed` (boolean): Include completed commitments (default: false) ### `complete_commitment` (~125 tokens) Mark a commitment as completed. Use when the user says they finished something or a deadline has passed. [write-tier — first use may require a manager's approval; a from-now-on approval makes future calls seamless, a just-once approval re-asks next time.] Input parameters: - `commitment_id` (string): The UUID of the commitment to complete - `companyId` (string): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `title_search` (string): Search by title if ID not known (fuzzy match) ### `update_commitment` (~244 tokens) Update fields of an existing commitment — title, domain, due date, consequence, or description. Use when the user says "change the due date on...", "rename that commitment to...", "move X to next week", or otherwise edits something already tracked (not marking it done — use complete_commitment for that). [write-tier — first use may require a manager's approval; a from-now-on approval makes future calls seamless, a just-once approval re-asks next time.] Input parameters: - `commitment_id` (string): The UUID of the commitment to update. - `companyId` (string): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `consequence` (string): New consequence — what happens if this slips. - `description` (string): New additional details or notes. - `domain` (string): New life domain: personal, family, home, w2, or company:. - `due_date` (string): New due date in YYYY-MM-DD format. - `title` (string): New title. - `title_search` (string): Search by title if ID not known (fuzzy match). ### `cancel_commitment` (~168 tokens) Cancel a commitment without completing it — marks it cancelled. Use when the user says "cancel that", "never mind, drop it", or "that's not happening anymore" for something already tracked. For finished work, use complete_commitment instead. [write-tier — first use may require a manager's approval; a from-now-on approval makes future calls seamless, a just-once approval re-asks next time.] Input parameters: - `commitment_id` (string): The UUID of the commitment to cancel. - `companyId` (string): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `reason` (string): Optional. Why this is being cancelled. - `title_search` (string): Search by title if ID not known (fuzzy match). ### `get_executive_landscape` (~101 tokens) Get a cross-domain view of everything on the user's plate. Shows commitments from all life domains + promoted tactics from all workspaces, grouped by urgency. Use when the user asks "what should I focus on?", "what's on my plate?", "am I dropping anything?", or similar portfolio-level questions. Input parameters: - `companyId` (string): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. ### `share_commitment` (~160 tokens) Share a commitment with your spouse or partner so they can see it too. Use when the user says "share this with my wife/husband" or "let [name] see this". [write-tier — first use may require a manager's approval; a from-now-on approval makes future calls seamless, a just-once approval re-asks next time.] Input parameters: - `commitment_id` (string): The UUID of the commitment to share - `companyId` (string): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `share_with_email` (string, required): Email address of the person to share with - `title_search` (string): Search by title if ID not known (fuzzy match) ### `unshare_commitment` (~136 tokens) Stop sharing a commitment with someone. Removes their access. [write-tier — first use may require a manager's approval; a from-now-on approval makes future calls seamless, a just-once approval re-asks next time.] Input parameters: - `commitment_id` (string): The UUID of the commitment to unshare - `companyId` (string): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `title_search` (string): Search by title if ID not known (fuzzy match) - `unshare_email` (string, required): Email address of the person to remove sharing for ### `send_slack_message` (~233 tokens) Send a message to a Slack channel or direct message to a team member. Use when user asks to "message X on Slack", "send a Slack message", "DM someone on Slack", "post to #channel", etc. [outbound-tier — EVERY call needs a manager's approval (per-send human rail): each request queues its own approval card and sends exactly once on approve. There is no standing grant for this tool.] Input parameters: - `channel_name` (string): Slack channel name to post to (without #), e.g., "general", "engineering". Use this OR recipient_name, not both. - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `message` (string, required): The message text to send (supports Slack markdown: *bold*, _italic_, etc.) - `recipient_name` (string): Name of the person to DM (e.g., "Alex", "Jordan"). Will be looked up via linked accounts or Slack directory. - `thread_ts` (string): Optional thread timestamp to reply in a thread ### `get_brand_guidelines` (~146 tokens) Get the company's brand guidelines — name, tagline, colors (hex codes), typography, personality/tone, naming rules, and VISUAL + POSITIONING dos/donts. Call this first, and use it, before generating any image, banner, video, or visual asset (inject the exact brand colors + style), and for naming/positioning in copy. For HOW to WRITE (voice, cadence, word choice) use get_voice_profile — this brand guide governs how the brand LOOKS and what it stands for, not writing style. Input parameters: - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. ### `update_brand_guidelines` (~164 tokens) Update specific fields of the company's brand guidelines (visual identity, naming, positioning). Only modifies the fields you specify - all other data is preserved. Use when the user asks to change colors, tagline, typography, personality/tone, naming rules, or visual dos/donts. For changing how the brand WRITES (voice/cadence), use update_voice_profile instead. [write-tier — first use may require a manager's approval; a from-now-on approval makes future calls seamless, a just-once approval re-asks next time.] Input parameters: - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `updates` (object, required): Only the fields to update. Other fields are preserved automatically. ### `resolve_brand_guide` (~191 tokens) Draft a first brand guide (personality tone, visual/positioning dos and donts) EXTRACTED from the company's own canon documents, with a verified receipt (quote + source doc) on every proposed item. Proposes only — never saves anything; the user reviews the receipts and accepts, then the accepted items are applied via update_brand_guidelines. Use when the user accepts an offer to build their brand guide from existing material, or explicitly asks to assemble a brand guide from what is already on file. For a company with no material on file, this returns nothing — ask instead. [sensitive-tier — first use may require a manager's approval; a from-now-on approval makes future calls seamless, a just-once approval re-asks next time.] Input parameters: - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. ### `get_voice_profile` (~122 tokens) Get the company's VOICE PROFILE — the operator's real writing voice the drafting agents ground on (style descriptor, in-voice DOs, out-of-voice AVOIDs, real exemplars, target reading level). Use this before drafting any post, caption, email, or article, for any agent writing on this company's behalf, so the first draft is in-voice — do not rely on brand tone adjectives alone. Input parameters: - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. ### `update_voice_profile` (~151 tokens) Update the company's voice profile. Only modifies the fields you specify; all other data is preserved. Use when the operator wants to tune their voice — add/refine an in-voice DO or an out-of-voice AVOID, adjust the style descriptor, set a target reading level, or set whose voice it is. [write-tier — first use may require a manager's approval; a from-now-on approval makes future calls seamless, a just-once approval re-asks next time.] Input parameters: - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `updates` (object, required): Only the fields to update. Others are preserved. ### `ingest_voice_corpus` (~265 tokens) Build or refresh the company's voice profile from REAL writing. Use this when the operator wants agents to learn their voice from their actual work — pass a URL to their blog / newsletter / posts (or an admired creator's page), or paste sample text. The system fetches it safely, distills the STYLE (cadence, word choice, argument-building — never faith substance), and merges it into the voice profile all drafting agents ground on. For any operator/brand setting up or improving how their content sounds. [sensitive-tier — first use may require a manager's approval; a from-now-on approval makes future calls seamless, a just-once approval re-asks next time.] Input parameters: - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `faith_heavy` (boolean): Mark the sources faith-heavy (style learned, faith substance excluded). - `subject_kind` (string): Whose voice — 'person' (personal brand) or 'brand'. - `subject_name` (string): The person or brand name. - `text` (string): A pasted writing sample to learn from. - `urls` (array): Public URLs to learn the voice from (SSRF-guarded fetch). ### `get_reader_profile` (~119 tokens) Get a person's OPERATOR FLUENCY (reader profile) — overall character level + per-topic strengths (novice/fluent/expert). Follows them across companies. Use before writing cards/FYIs so speech matches their level. Defaults to the caller; pass member_id for another person. Input parameters: - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `member_id` (string): Optional UUID whose fluency to read. Defaults to you (ctx.userId). ### `update_reader_profile` (~219 tokens) Update a person's OPERATOR FLUENCY (baseline + per-topic strengths that follow them across companies). Use when the operator (or an admin) sets or corrects how agents should speak to them, or when seeding an empty profile with seed_if_empty for a first guess. Human door for edits; agents may seed empty self only. [write-tier — first use may require a manager's approval; a from-now-on approval makes future calls seamless, a just-once approval re-asks next time.] Input parameters: - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `default_level` (string) - `domains` (object): Topic → novice|fluent|expert (merged). - `glossary_seen` (array) - `member_id` (string): Optional target UUID. Defaults to you. - `seed_if_empty` (boolean): If true, agents may write only when the target has no profile yet (self only). Human doors may always write. ### `get_reader_expertise_interview` (~128 tokens) Get a fluency INTERVIEW kit (domain candidates + "which is clearest?" protocol) so a host CoS can gauge how FO should talk to this operator. Use when onboarding, partner MCP connect, or speech feels too dumbed-down or too jargony. After human yes, call update_reader_profile — fluency follows them across companies. Input parameters: - `companyId` (string): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `member_name` (string): Optional display name (defaults to "the operator"). ### `derive_from_website` (~219 tokens) SPIKE tool (.agent/design-docs/2026-07-09-magical-onboarding-buildout-mode.md, "The Assignment"). Give it a business's public URL; it reads the page and returns a derived ICP, a derived brand voice, and 3 ready-to-post drafts written in that voice — the onboarding lead magnet's engine, spike-grade. Nothing is persisted to any company. Use when your operator asks you to run the website-derivation spike against a real business URL, to show the operator what an agent team can already see about their business. [sensitive-tier — first use may require a manager's approval; a from-now-on approval makes future calls seamless, a just-once approval re-asks next time.] Input parameters: - `companyId` (string): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `url` (string, required): The business's public URL to derive from (must include https:// or http://) — their homepage or an About/product page. ### `browse_url` (~181 tokens) Browse a web page in a real browser and take a screenshot. Returns page content and a screenshot image. Use when you need to SEE what a page looks like (visual audit, brand check), interact with JavaScript-heavy pages, or capture visual evidence. The screenshot is returned as an image you can analyze directly with your vision. [sensitive-tier — first use may require a manager's approval; a from-now-on approval makes future calls seamless, a just-once approval re-asks next time.] Input parameters: - `actions` (array): Optional browser actions to perform before taking screenshot. Each action has a type and optional selector/value. - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `url` (string, required): The full URL to browse (must include https:// or http://) ### `save_artifact` (~197 tokens) Save an artifact (screenshot, analysis, report) to the company archive. Use after browse_url to persist visual evidence, or to save any agent-produced artifact for future reference. [write-tier — first use may require a manager's approval; a from-now-on approval makes future calls seamless, a just-once approval re-asks next time.] Input parameters: - `artifact_type` (string, required): Type of artifact being saved - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `description` (string): What this artifact shows or contains - `metadata_json` (string): Optional JSON-encoded metadata (scores, analysis results, etc.). - `source_url` (string): URL the artifact relates to (if applicable) - `storage_path` (string): Storage path where the file was uploaded - `title` (string, required): Short descriptive title for the artifact ### `get_artifacts` (~125 tokens) Get saved artifacts for the company. Use to review past screenshots, analyses, and reports. Filters by artifact type, source URL, or agent. Input parameters: - `artifact_type` (string): Filter by artifact type - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `created_by_agent` (string): Filter by agent that created the artifact - `limit` (number): Maximum artifacts to return (default: 10) - `source_url` (string): Filter by source URL (partial match) ### `create_master_plan` (~134 tokens) Initialize a new multi-step project with a persistent Master Plan artifact. Call this BEFORE starting any complex, multi-tool task. [write-tier — first use may require a manager's approval; a from-now-on approval makes future calls seamless, a just-once approval re-asks next time.] Input parameters: - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `initial_plan` (string, required): The high-level plan or blueprint for the task. - `task_title` (string, required): Short title for the task (e.g., "Influencer CRM Build") ### `create_google_doc` (~175 tokens) Create a new Google Doc in the user's Freedom OS folder. Use for JDs, deliverables, and shared documents. By default, creates beautifully formatted docs. [write-tier — first use may require a manager's approval; a from-now-on approval makes future calls seamless, a just-once approval re-asks next time.] Input parameters: - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `content` (string, required): Content for the document in markdown format - `folder` (string): Which folder to save in - `format_for_humans` (boolean): If true (default), converts markdown to rich formatting. Set false for agent-to-agent docs. - `title` (string, required): Document title (e.g., "Marketing Specialist JD") ### `read_google_doc` (~68 tokens) Read content from an existing Google Doc by its ID. Input parameters: - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `doc_id` (string, required): Google Doc ID (the long alphanumeric string from the URL) ### `update_google_doc` (~106 tokens) Append new content to an existing Google Doc. [write-tier — first use may require a manager's approval; a from-now-on approval makes future calls seamless, a just-once approval re-asks next time.] Input parameters: - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `content` (string, required): Content to append to the document - `doc_id` (string, required): Google Doc ID to update ### `list_google_drive_files` (~104 tokens) List files in the user's Google Drive. Can filter by type (spreadsheet, document) and search by name. Input parameters: - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `file_type` (string): Filter by file type - `max_results` (number): Maximum results to return (default: 10) - `query` (string): Search query to filter files by name ### `create_spreadsheet` (~103 tokens) Create a new Google Spreadsheet with optional headers. [write-tier — first use may require a manager's approval; a from-now-on approval makes future calls seamless, a just-once approval re-asks next time.] Input parameters: - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `headers` (array): Column headers for the first row - `title` (string, required): Spreadsheet title ### `read_sheet` (~81 tokens) Read data from a Google Spreadsheet. Input parameters: - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `range` (string): A1 notation range (e.g., "Sheet1!A1:D10"). Defaults to all data. - `spreadsheet_id` (string, required): Spreadsheet ID ### `append_to_sheet` (~100 tokens) Append rows to a Google Spreadsheet. [write-tier — first use may require a manager's approval; a from-now-on approval makes future calls seamless, a just-once approval re-asks next time.] Input parameters: - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `spreadsheet_id` (string, required): Spreadsheet ID - `values` (array, required): Array of rows to append ### `update_sheet` (~125 tokens) Update specific cells in a Google Spreadsheet. [write-tier — first use may require a manager's approval; a from-now-on approval makes future calls seamless, a just-once approval re-asks next time.] Input parameters: - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `range` (string, required): A1 notation range to update (e.g., "Sheet1!A1:B5") - `spreadsheet_id` (string, required): Spreadsheet ID - `values` (array, required): New values for the range ### `batch_update_spreadsheet` (~128 tokens) Perform batch operations on a Google Spreadsheet (formatting, merging, etc.). [write-tier — first use may require a manager's approval; a from-now-on approval makes future calls seamless, a just-once approval re-asks next time.] Input parameters: - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `requests_json` (string, required): JSON-encoded array of batch update request objects, e.g. "[{\"updateCells\":{...}}]". - `spreadsheet_id` (string, required): Spreadsheet ID ### `audit_brand_visibility` (~215 tokens) Audit whether Freedom OS appears in AI-generated search results. Sends a search query to external LLMs (Claude, Grok, Gemini, Perplexity) and checks each response for brand mentions. This is a competitive SEO/GEO auditing tool — like a mystery shopper for AI search engines. It does NOT answer questions or delegate work. Input parameters: - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `max_tokens` (number): Maximum response length per provider (default: 1000) - `prompt` (string, required): A search-style query to test (e.g., "What is the best AI operating system for solopreneurs?") - `providers` (array, required): Which AI search engines to audit. Options: anthropic (Claude), xai (Grok), google (Gemini), perplexity (Sonar Pro with live search) - `temperature` (number): Response variability 0-1 (default: 0.7) ### `posthog_query_trends` (~177 tokens) Query event trends from PostHog (pageviews, signups, DAU, etc. over time). Returns time-series data. Only works if PostHog is connected. Input parameters: - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `date_from` (string): Start date: "-7d", "-30d", "-90d", "2024-01-01" (default: -7d) - `date_to` (string): End date (default: now) - `events` (array): Events to query. Each: { id: "$pageview", name: "Page Views", math: "total" }. Defaults to $pageview. - `interval` (string): Grouping interval (default: day) ### `posthog_query_funnel` (~156 tokens) Build and run a funnel analysis in PostHog. Shows step-by-step conversion rates (e.g., signup → onboard → purchase). Only works if PostHog is connected. Input parameters: - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `date_from` (string): Start date (default: -30d) - `date_to` (string): End date (default: now) - `events` (array, required): Funnel steps (minimum 2). Each: { id: "event_name", name: "Display Name" } - `funnel_window_days` (number): Days a user has to complete the funnel (default: 14) ### `posthog_list_insights` (~92 tokens) List existing saved insights in PostHog. Shows names, types, and links. Only works if PostHog is connected. Input parameters: - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `limit` (number): Max insights to return (default: 20) - `search` (string): Search insights by name ### `posthog_hogql` (~100 tokens) Run an arbitrary HogQL (SQL) query against PostHog data. Use for custom analysis not covered by other tools. Only works if PostHog is connected. Input parameters: - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `limit` (number): Max rows to return (default: 100) - `query` (string, required): HogQL query string ### `posthog_list_events` (~110 tokens) List all event types tracked in PostHog, ordered by usage. Call this FIRST before building funnels or trends — it shows the actual event names in the user's PostHog. Only works if PostHog is connected. Input parameters: - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `limit` (number): Max events to return (default: 50) - `search` (string): Search events by name ### `get_credit_usage` (~115 tokens) Check credit balance, usage history, and cost breakdown. Shows remaining credits, usage by model/endpoint, and top cost drivers. Useful for cost optimization, budget monitoring, and reviewing whether activities are cost-effective. Input parameters: - `breakdown_by` (string): How to group the usage data. Default: "both" - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `period` (string): Time period for usage breakdown. Default: "month" ### `challenge_as_customer` (~190 tokens) Run your deliverable past the company's customer truth: REAL Customer Evidence first (when stored), then generated ICP as labeled simulation. Returns honest feedback — what would make them engage, scroll past, or what's missing. Use on customer-impact deliverables before sending. Input parameters: - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `context` (string): Optional additional context about what this deliverable is for, who will see it, or what outcome you want - `deliverable` (string, required): The content/report/strategy you want the simulated customer to evaluate - `deliverable_type` (string, required): What type of deliverable this is — helps the customer evaluate appropriately - `target_icp` (string): ICP ID to use (from get_icps), or "auto" to use the first available. Default: auto ### `deliberate` (~375 tokens) Run an adversarial deliberation on a decision. Multiple AI perspectives argue opposing positions over multiple rounds, iteratively strengthening arguments, and converge on a recommendation with confidence scoring. Use for important decisions where you want to stress-test options from multiple angles. Over MCP the deliberation runs in the background: the first call returns a run_id immediately; call deliberate again with { run_id } (plus the same companyId) after ~1-2 minutes to fetch the result. Routing: Important decision → deliberate for adversarial analysis Input parameters: - `companyId` (string): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `context` (string): Goals, constraints, values, and relevant data that should inform the deliberation. The more context, the better the arguments. - `criteria` (array): Optional weighted evaluation criteria. Each item should have "name" (string) and "weight" (number 0-1, should sum to ~1). If omitted, defaults are generated. - `max_rounds` (number): Maximum rounds of deliberation (default: 5). More rounds = better arguments but more compute. - `positions` (array): Two or more positions to argue. Each should be a clear, distinct option — e.g., ["Mobile app development", "API partnerships", "Content marketing"]. Required unless polling with run_id. - `question` (string): The decision or question to deliberate. Be specific — e.g., "Should we invest in mobile app development or API partnerships for growth in Q2?" Required unless polling with run_id. - `run_id` (string): Poll a background deliberation started earlier (MCP mode). Pass the run_id returned by the starting call, with the same companyId. Omit question/positions when polling. ### `get_decision_ledger` (~249 tokens) THE tool for what the Freedom Engine has DECIDED for this company — the audit feed of every autonomous decision: what it auto-ran, what it teed up for your approval, and what it refused (e.g. faith/values content), each with the reason, the profit at play, the founder-attention cost, and how fresh the inputs were. Use for "what did the engine do today", "what did it auto-run", "why did it hold that tactic", "show me the decision ledger / cockpit". This is the only tool with the engine's decision history — get_command_center_items shows open cards to act on, not the decision audit trail. Input parameters: - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `limit` (number): How many recent decisions to return, newest first (default 25, max 100). - `routing` (string): Optional filter: AUTO_RUN (the engine ran it autonomously), TEE_UP (held for your approval), or REFUSE_AND_SURFACE (refused — e.g. faith/values content the founder authors). ### `search_conversations` (~136 tokens) Search past conversations with the user. Use when the user says "remember when we talked about...", "haven't we discussed X before?", "what did we decide about...", or references any prior conversation. Returns matching conversations with relevant message snippets. Does NOT return the current conversation. Input parameters: - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `limit` (number): Max conversations to return (default: 5, max: 10) - `query` (string, required): Search terms — keywords, topics, or phrases from the conversation the user is referencing ### `manage_responsibilities` (~237 tokens) Assign, delegate, or revoke responsibility domains for team members. This controls routing — which user receives agent output for specific domains like marketing, finance, etc. [write-tier — first use may require a manager's approval; a from-now-on approval makes future calls seamless, a just-once approval re-asks next time.] Input parameters: - `action` (string, required): Action to perform - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `delegation_from_email` (string): Email of the user delegating their responsibilities. Only for delegate action. - `domains` (array): Domain names to assign (e.g., ["marketing", "content", "social"]). Use lowercase. - `reason` (string): Why the change is happening (e.g., "vacation", "new hire", "role change") - `target_user_email` (string): Email of the user to assign/delegate to. Required for assign and delegate. - `valid_until` (string): ISO date string when delegation expires. Only for delegate action. Omit for permanent assignments. ### `get_routing_overview` (~57 tokens) See how agent output is currently routed — who is responsible for which domains in the company. Input parameters: - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. ### `generate_video` (~582 tokens) Generate a video clip using AI (xAI Imagine, 3 credits). Supports text-to-video, image-to-video, MULTI-IMAGE video (up to 7 images combined), and video editing with native audio (voiceover, sound effects, music). Best for quick drafts, social clips, iterations, and audio-first content. For cinematic final deliverables, use generate_video_veo instead. [sensitive-tier, initiates a multi-step agent process — first use may require a manager's approval; a from-now-on approval makes future calls seamless, a just-once approval re-asks next time.] Input parameters: - `artifact_id` (string): ID of a single existing artifact from the MEDIA IN THIS CONVERSATION block. The system resolves a fresh signed URL and auto-detects: image artifacts → image-to-video, video artifacts → video editing.… - `artifact_ids` (array): Array of artifact IDs (up to 7) from the MEDIA IN THIS CONVERSATION block for multi-image video generation. The system resolves fresh signed URLs for each. Example: pass the mascot image artifact + f… - `aspect_ratio` (string): Aspect ratio. Default: 16:9. For image-to-video, defaults to the input image ratio. Not supported for video editing. - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `duration` (number): Video duration in seconds (1-15). Default: 5. Not supported for video editing. - `image_url` (string): URL of a single still image to animate (image-to-video mode). Use image_url from a previous generate_image result. For multiple images, use image_urls instead. - `image_urls` (array): Array of image URLs (up to 7) for multi-image video generation. Combine a mascot, a person, product shots, and brand assets into one cohesive video. Use signed URLs from the MEDIA IN THIS CONVERSATIO… - `prompt` (string, required): Detailed description of the video to generate. Include visual scene, audio/voice direction, mood, and brand elements. For multi-image: describe how the subjects from each image interact. For video ed… - `resolution` (string): Video resolution. 480p (default, faster) or 720p (HD). Not supported for video editing. - `save_to_drive` (boolean): If true, also save the video to Google Drive. Defaults to false. - `video_url` (string): URL of an existing video to edit (video editing mode). Describe the edits in the prompt. Input capped at 8.7 seconds. ### `generate_video_veo` (~292 tokens) Generate a high-fidelity cinematic video using Google Veo 3.1 (5 credits). Premium quality with realistic physics and cinematic lighting. Use ONLY for final deliverables — landing page videos, polished ad creatives, brand content. NEVER use for first drafts. Always iterate with generate_video first, then upgrade to Veo for the final version. [sensitive-tier, initiates a multi-step agent process — first use may require a manager's approval; a from-now-on approval makes future calls seamless, a just-once approval re-asks next time.] Input parameters: - `aspect_ratio` (string): Aspect ratio. 16:9 for landscape, 9:16 for vertical/Reels, 1:1 for square. - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `prompt` (string, required): Detailed cinematic description of the video. Include visual scene, camera direction, lighting, audio, and brand elements. - `quality` (string): Quality mode. "fast" for quick previews, "cinematic" (default) for premium quality. - `reference_image_url` (string): Optional URL of an image to animate (image-to-video). Use the image_url from a previous generate_image result. - `save_to_drive` (boolean): If true, also save the video to Google Drive. Defaults to false. ### `get_x_post_metrics` (~142 tokens) Get engagement metrics for a tweet on X (Twitter). Returns impressions, likes, retweets, replies, quotes, and bookmarks. Use when the user asks "how did my post do?", "check my tweet analytics", or to evaluate content performance. Input parameters: - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `pipeline_output_id` (string): Optional. The pipeline_output ID to write metrics back to the content card. - `tweet_id` (string, required): The tweet ID (numeric) or full tweet URL (e.g. https://x.com/user/status/123456) ### `list_ad_accounts` (~109 tokens) List the Meta (Facebook/Instagram) ad accounts on this company's connection, with status, currency, lifetime spend, and spend cap. Use first when the user asks about their FB/IG ads — the returned id feeds list_ad_campaigns and get_ads_performance. Routing: Meta/FB/IG ads questions → start here to find the ad account Input parameters: - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. ### `list_ad_campaigns` (~156 tokens) List campaigns in a Meta ad account: status, objective, budgets (major currency units), and schedule. Use when the user asks what ads/campaigns are running on Facebook or Instagram. Omit ad_account_id when the connection has exactly one ad account. Input parameters: - `ad_account_id` (string): Ad account id from list_ad_accounts (act_ or bare digits). Optional when the connection has exactly one ad account. - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `effective_status` (array): Optional filter, e.g. ["ACTIVE"], ["PAUSED"], ["ACTIVE","PAUSED"]. Omit for all campaigns. ### `get_ads_performance` (~268 tokens) Get Meta ads results: spend, impressions, clicks, CTR, CPC, CPM, reach, conversions (actions), cost per action, and purchase ROAS — at account, campaign, adset, or ad level over a chosen window. Use when the user asks how their Facebook/Instagram ads are doing, what they spent, or what it returned. Input parameters: - `ad_account_id` (string): Ad account id (act_ or bare digits). Optional when the connection has exactly one ad account. - `campaign_id` (string): Optional: scope the report to one campaign (id from list_ad_campaigns). - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `date_preset` (string): Reporting window preset, e.g. 'last_7d', 'last_30d' (default), 'this_month', 'lifetime'. Mutually exclusive with time_range. - `level` (string): Aggregation level: 'account', 'campaign' (default), 'adset', or 'ad'. - `time_range` (object): Exact window: { since: 'YYYY-MM-DD', until: 'YYYY-MM-DD' }. Mutually exclusive with date_preset. ### `search_ad_targeting` (~112 tokens) Search Meta's ad-interest targeting catalog (returns interest ids + audience sizes). Use when designing a Meta ad draft and you need valid {id, name} targeting pairs for create_meta_ad_draft — e.g. search "pharmacy" or "compounding". Input parameters: - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `query` (string, required): Interest keyword, e.g. "pharmacy", "healthcare compliance" ### `create_meta_ad_draft` (~341 tokens) Create a complete Meta (Facebook/Instagram) ad draft — campaign + ad set + creative + ad — ALL in PAUSED state, spending nothing. Use when the user wants to set up or draft an ad. Activation is a separate human-approved step (set_meta_ad_status). [sensitive-tier — first use may require a manager's approval; a from-now-on approval makes future calls seamless, a just-once approval re-asks next time.] Input parameters: - `ad_account_id` (string): Ad account (act_). Optional when the connection has exactly one. - `campaign_name` (string, required): Campaign name, e.g. "PCAI cold traffic — Compliance Crusader v1" - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `cta` (string): Optional call-to-action: LEARN_MORE, SIGN_UP, GET_STARTED, CONTACT_US, DOWNLOAD, SUBSCRIBE - `daily_budget` (number, required): Daily budget in the account currency, major units (e.g. 25 = 25 USD/day) - `image_artifact_id` (string): Optional agent_artifacts image id for the creative - `link_url` (string, required): https destination URL (landing page, with UTMs) - `objective` (string): OUTCOME_TRAFFIC (default) | OUTCOME_AWARENESS | OUTCOME_ENGAGEMENT - `primary_text` (string, required): The ad copy (primary text) - `targeting` (object): Audience: {countries: ["US"], age_min, age_max, interests: [{id, name}]} ### `preview_meta_ad` (~102 tokens) Get a facebook.com preview link for a drafted Meta ad, so the user can see exactly what it will look like before deciding to activate. Use after create_meta_ad_draft or when the user asks to see a drafted ad. Input parameters: - `ad_id` (string, required): Numeric ad id (from create_meta_ad_draft output) - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. ### `set_meta_ad_status` (~186 tokens) Activate or pause a Meta campaign, ad set, or ad. ACTIVATION STARTS REAL AD SPEND and always requires the human (live chat or an approved card) — agents cannot activate. Pausing stops spend. Use after the user has reviewed a draft and explicitly says to launch, or asks to stop a running ad. [outbound-tier — EVERY call needs a manager's approval (per-send human rail): each request queues its own approval card and sends exactly once on approve. There is no standing grant for this tool.] Input parameters: - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `object_id` (string, required): Numeric campaign / ad set / ad id - `status` (string, required): 'ACTIVE' (starts spend — human only) or 'PAUSED' (stops spend) ### `update_meta_ad_budget` (~176 tokens) Change the daily budget of a Meta ad set (account currency, major units; structural cap applies). Moves real money, so it always requires the human — agents cannot change budgets. Use when the user explicitly asks to raise or lower spend on a campaign. [outbound-tier — EVERY call needs a manager's approval (per-send human rail): each request queues its own approval card and sends exactly once on approve. There is no standing grant for this tool.] Input parameters: - `ad_account_id` (string): Optional — for currency resolution when several accounts exist - `adset_id` (string, required): Numeric ad set id - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `daily_budget` (number, required): New daily budget, account currency major units ### `get_site_list` (~62 tokens) List all verified sites/properties in Google Search Console. Use this first to discover which sites are available before querying search performance. Input parameters: - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. ### `get_search_performance` (~249 tokens) Get search performance data from Google Search Console — queries, clicks, impressions, CTR, and average position. Use when the user asks about SEO performance, keyword rankings, organic traffic, or search visibility. Input parameters: - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `dimensions` (array): Dimensions to group by. Options: "query", "page", "country", "device", "date". Defaults to ["query"]. - `end_date` (string): End date in YYYY-MM-DD format. Defaults to today. - `page_filter` (string): Optional filter: only include rows where the page URL contains this string. - `query_filter` (string): Optional filter: only include rows where the query contains this string. - `row_limit` (number): Max rows to return (1-100). Defaults to 25. - `site_url` (string, required): The site URL exactly as shown in Search Console (e.g., "sc-domain:example.com" or "https://example.com/") - `start_date` (string): Start date in YYYY-MM-DD format. Defaults to 28 days ago. ### `get_page_performance` (~176 tokens) Get per-page search performance from Google Search Console — which pages get the most clicks, impressions, and best positions. Use when analyzing content performance or identifying top-performing pages. Input parameters: - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `end_date` (string): End date in YYYY-MM-DD format. Defaults to today. - `page_filter` (string): Optional: only include pages whose URL contains this string (e.g., "/blog/"). - `row_limit` (number): Max rows to return (1-100). Defaults to 25. - `site_url` (string, required): The site URL exactly as shown in Search Console - `start_date` (string): Start date in YYYY-MM-DD format. Defaults to 28 days ago. ### `inspect_url` (~143 tokens) Inspect a URL in Google Search Console — check indexing status, crawl errors, mobile usability, and rich results. Use for technical SEO audits, diagnosing why pages aren't appearing in search, or checking mobile-friendliness. Input parameters: - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `inspection_url` (string, required): The full URL to inspect (e.g., "https://getfreedomos.com/features") - `site_url` (string, required): The site URL as shown in Search Console (e.g., "sc-domain:getfreedomos.com" or "https://getfreedomos.com/") ### `get_sitemaps` (~108 tokens) List all sitemaps submitted to Google Search Console for a property — shows submission status, indexing coverage, errors, and warnings. Use for technical SEO audits and crawl coverage analysis. Input parameters: - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `site_url` (string, required): The site URL exactly as shown in Search Console (e.g., "sc-domain:example.com" or "https://example.com/") ### `get_xero_report` (~191 tokens) Get a LIVE financial report straight from the company's connected Xero ledger: ProfitAndLoss, BalanceSheet, BankSummary, TrialBalance, or ExecutiveSummary. Source of truth for current numbers — prefer this over get_financial_summary (which reads the periodically-processed snapshot) when the user asks about current/live financial position. Routing: LIVE ledger (Xero): balance sheet / P&L / bank summary straight from the books → use over get_financial_summary for current numbers Input parameters: - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `from_date` (string): Period start, YYYY-MM-DD (period reports: ProfitAndLoss, BankSummary) - `kind` (string, required): Which report to pull - `to_date` (string): Period end / as-at date, YYYY-MM-DD. Defaults to today. ### `list_xero_bank_transactions` (~144 tokens) List LIVE bank transactions from the company's connected Xero ledger (paged, 100 per page, newest first). Use for "current bank activity", reconciliation questions, or verifying a specific payment hit the bank. Routing: LIVE bank transactions from Xero (newest first) → use for current bank activity questions Input parameters: - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `from_date` (string): Only transactions on/after this date, YYYY-MM-DD - `page` (number): Page number, 1-based (Xero pages at 100). Default 1. ### `list_xero_contacts` (~139 tokens) List contacts (customers/suppliers) from the company's connected Xero ledger, optionally filtered by a search term (paged, 100 per page). Use when the user or an activity needs who the company invoices or pays — customer/supplier lookups, receivables context, or verifying a counterparty exists in the books. Input parameters: - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `page` (number): Page number, 1-based. Default 1. - `search_term` (string): Filter by name/email fragment (Xero searchTerm) ### `run_quality_check` (~227 tokens) Evaluate content or media against your ICP persona using Gemini 3.1 Pro vision. Actually SEES images and WATCHES videos. Returns quality scores (1-10) across 6 dimensions + specific ICP feedback. Use after generating media or drafting content to validate quality before delivering to the user. [sensitive-tier — first use may require a manager's approval; a from-now-on approval makes future calls seamless, a just-once approval re-asks next time.] Input parameters: - `artifact_id` (string): ID of a specific artifact to evaluate (from generate_image or generate_video result). If omitted, auto-finds the most recent media artifact. - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `content` (string): Text content to evaluate (X post copy, email draft, newsletter). Can be combined with artifact_id for text + visual evaluation. - `task` (string): What this deliverable is for (e.g. "X post about Freedom OS launch"). Gives the ICP evaluator context. ### `configure_dashboard` (~612 tokens) Create or update a widget on your agent dashboard. Use this to display key metrics, charts, tables, or timelines that help the user understand your work at a glance. Each call creates or updates one widget. [write-tier — first use may require a manager's approval; a from-now-on approval makes future calls seamless, a just-once approval re-asks next time.] Input parameters: - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `config` (object): Widget configuration. Shape depends on widget_type: - metric: { value, previous_value, format ("number"|"currency"|"percent"|"text"), trend_direction ("up"|"down"|"flat"), suffix } - chart: { chart_t… - `data` (array): Data rows for chart/table/list/gantt widgets. Each item is an object. - chart: [{ label: "Jan", value: 100 }, ...] - table: [{ col1: "val", col2: "val" }, ...] - list: [{ label: "Item", status: "done… - `is_visible` (boolean): Whether the widget is visible on the dashboard. Default: true - `position` (number): Display order (0 = first, higher = later). Default: 0 - `title` (string, required): Display title for the widget (e.g., "Monthly Revenue", "Content Pipeline") - `widget_id` (string): UUID of existing widget to update. Omit to create a new widget. - `widget_type` (string, required): Type of widget to create ### `list_dashboard_widgets` (~79 tokens) List all dashboard widgets for a specific agent. Use to see what widgets are currently configured before making changes. Input parameters: - `agent_id` (string): UUID of the agent whose widgets to list. Defaults to current agent. - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. ### `remove_dashboard_widget` (~93 tokens) Remove a widget from an agent dashboard. [write-tier — first use may require a manager's approval; a from-now-on approval makes future calls seamless, a just-once approval re-asks next time.] Input parameters: - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `widget_id` (string, required): UUID of the widget to remove ### `generate_vector_image` (~350 tokens) Generate a native SVG vector image using Recraft V4 Pro Vector. The ONLY tool that outputs true SVG with editable paths. Best for logos, icons, brand marks, vector illustrations, and scalable graphics for Framer animations. Routing: SVG/vector/logo/icon/brand mark/scalable graphics → use this (3 credits) [sensitive-tier — first use may require a manager's approval; a from-now-on approval makes future calls seamless, a just-once approval re-asks next time.] Input parameters: - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `folder` (string): Optional Media gallery folder to file this into (freeform name, e.g. "q3-campaign" or "brand-assets"). Shown as a folder chip on the /media page. Reuse an existing folder name when the work belongs t… - `folder_name` (string): Subfolder name for Drive save (e.g., "Logos", "Icons", "Brand"). Only used when save_to_drive is true. - `prompt` (string, required): Detailed description of the vector image. Include style, colors, subject, composition. Be specific about the visual style — "minimalist line art logo", "flat vector icon", "geometric brand mark". - `save_to_drive` (boolean): If true, also save the SVG to Google Drive for permanent storage. Defaults to false. - `size` (string): Size in WxH format (e.g., "1024x1024") or aspect ratio (e.g., "1:1", "16:9"). Defaults to 1024x1024. ### `vectorize_image` (~346 tokens) Convert an existing raster image (PNG, JPG, WebP) to SVG vector format using Recraft. Preserves details and creates clean vector paths. Routing: "vectorize this", "convert to SVG", "make scalable" → use this (1 credit) [sensitive-tier — first use may require a manager's approval; a from-now-on approval makes future calls seamless, a just-once approval re-asks next time.] Input parameters: - `artifact_id` (string): ID of an existing artifact from the MEDIA IN THIS CONVERSATION block. The system will resolve a fresh signed URL automatically. - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `folder` (string): Optional Media gallery folder to file this into (freeform name, e.g. "q3-campaign" or "brand-assets"). Shown as a folder chip on the /media page. Reuse an existing folder name when the work belongs t… - `folder_name` (string): Subfolder name for Drive save. Only used when save_to_drive is true. - `image_url` (string): URL of the raster image to vectorize. Use a signed URL from the MEDIA IN THIS CONVERSATION block or any accessible image URL. - `isolate_subject` (boolean): Smart Workflow: If true, the tool will automatically remove the background to isolate the subject BEFORE vectorizing. Defaults to true. Set to false ONLY if you want to vectorize the entire scene inc… - `save_to_drive` (boolean): If true, also save the vectorized SVG to Google Drive. Defaults to false. ### `remove_background` (~233 tokens) Remove the background from an existing image, leaving the main subject isolated on a transparent background (PNG). Routing: "isolate the subject", "make background transparent", "remove background" → use this (1 credit) [sensitive-tier — first use may require a manager's approval; a from-now-on approval makes future calls seamless, a just-once approval re-asks next time.] Input parameters: - `artifact_id` (string): ID of an existing artifact from the MEDIA block. - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `folder` (string): Optional Media gallery folder to file this into (freeform name, e.g. "q3-campaign" or "brand-assets"). Shown as a folder chip on the /media page. Reuse an existing folder name when the work belongs t… - `folder_name` (string): Subfolder name for Drive save. - `image_url` (string): URL of the raster image to process. - `save_to_drive` (boolean): If true, saves to Drive. ### `save_knowledge` (~451 tokens) Save a Markdown knowledge file. Use for guidelines, SOPs, strategies, playbooks, meeting notes, contact lists, trackers, or any reference material that agents read and update over time. Pass scope="personal" to save private notes visible only to the current user (e.g., notes tied to their commitments). [write-tier — first use may require a manager's approval; a from-now-on approval makes future calls seamless, a just-once approval re-asks next time.] Input parameters: - `companyId` (string): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `content` (string, required): The knowledge content in Markdown format. FORMATTING RULES: Use ## headers for sections (NOT **bold**). Put a blank line between every paragraph and before/after lists. Use - for list items. Structur… - `folder` (string): Optional folder to save the file in (e.g., "acme-deal", "partners/acme"). Folders are auto-created. Use for organizing related files, especially for deal rooms or shared contexts. - `override_duplicate_reason` (string): ONLY after the canon gate refused this save as a duplicate: a specific reason why this file is NOT a duplicate of the canonical file the refusal named. Overrides are logged and visible to the operato… - `scope` (string): Where to save: "company" (default) = shared with the whole company; "personal" = private to the current user only. Use "personal" for notes tied to a specific person (e.g., context for the user's com… - `slug` (string): Optional custom slug for the filename. If omitted, auto-generated from the title. - `title` (string, required): Descriptive title for this knowledge file (e.g., "Acme Mascot Guidelines", "Content Strategy Q1") ### `read_knowledge` (~203 tokens) Read a Markdown knowledge file by slug. Slugs are folder-qualified with NO file extension (e.g. "canon/tim-voice-guide", "content-captures/2026-07-06-forgiveness-and-the-debt") — never repo-style paths, never ".md". Returns the full content plus a list of available sections. Use this to load guidelines, SOPs, or strategies before doing work that needs to reference them. Input parameters: - `companyId` (string): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `scope` (string): "company" (default) reads a company-shared file; "personal" reads from the current user's private notes. - `slug` (string, required): Folder-qualified slug with no extension, e.g. "canon/tim-voice-guide" (from list_knowledge or a save_knowledge result). Never a repo-style path, never ".md". ### `update_knowledge_section` (~224 tokens) Update a specific section of a knowledge file by its ## header. If the section exists, its content is replaced. If it doesn't exist, it's appended as a new section. Use this for surgical edits to guidelines or strategies without rewriting the entire file. [write-tier — first use may require a manager's approval; a from-now-on approval makes future calls seamless, a just-once approval re-asks next time.] Input parameters: - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `new_content` (string, required): The new Markdown content for this section (replaces everything between this ## and the next ##). Use proper Markdown: blank lines between paragraphs, - for list items, ### for sub-headers. Never use… - `section_header` (string, required): The ## section header to find and replace (case-insensitive). If not found, appended as a new section. - `slug` (string, required): The slug of the knowledge file to update ### `list_knowledge` (~122 tokens) List all knowledge files and folders saved for this company. Returns file names, slugs, sizes, and folder structure. Use this to discover what knowledge is available before reading or updating. Input parameters: - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `folder` (string): Optional folder to list contents of (e.g., "acme-deal", "partners"). Omit to list the root level. - `search` (string): Optional search term to filter files by name ### `delete_knowledge` (~123 tokens) Archive a knowledge file by slug (soft delete). The file is moved to _archived/ and can be restored later. Use when the user explicitly asks to remove a knowledge document. [write-tier — first use may require a manager's approval; a from-now-on approval makes future calls seamless, a just-once approval re-asks next time.] Input parameters: - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `slug` (string, required): The slug of the knowledge file to delete ### `share_knowledge` (~204 tokens) Share a knowledge file or folder with a specific user. Creates a per-user access grant. The shared user's agent will also be able to read the files. Front matter is auto-updated with audience metadata so agents know the content is restricted. [write-tier — first use may require a manager's approval; a from-now-on approval makes future calls seamless, a just-once approval re-asks next time.] Input parameters: - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `path` (string, required): The file or folder path to share. Use trailing "/" for folders (e.g., "acme-deal/"). Use no trailing "/" for files (e.g., "acme-deal/term-sheet"). - `permission` (string): Permission level: "read" (default) or "write". - `user_email` (string, required): Email of the FreedomOS user to share with. ### `unshare_knowledge` (~124 tokens) Revoke a user's access to a shared knowledge file or folder. [write-tier — first use may require a manager's approval; a from-now-on approval makes future calls seamless, a just-once approval re-asks next time.] Input parameters: - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `path` (string, required): The file or folder path to unshare. Must match exactly what was originally shared. - `user_email` (string, required): Email of the user to revoke access from. ### `create_folder` (~136 tokens) Create a folder in the knowledge base for organizing files. Folders can be nested (e.g., "partners/acme"). Use for deal rooms, topic grouping, or any organizational structure. [write-tier — first use may require a manager's approval; a from-now-on approval makes future calls seamless, a just-once approval re-asks next time.] Input parameters: - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `name` (string, required): Folder name (e.g., "acme-deal", "partners/acme"). Nested paths are supported. ### `list_shared_with_me` (~67 tokens) List all knowledge files and folders that have been shared with the current user. Shows who shared them, from which company, and the permission level. Input parameters: - `companyId` (string): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. ### `query_sme` (~332 tokens) Query an external Subject Matter Expert (SME) AI for verified domain knowledge. The SME's answers are grounded in verified rules and go through a rigorous verification pipeline — this is NOT a general search, it's consulting a domain expert. Use this when: \- You need factual, verified information for content creation (social media, blog posts, newsletters) \- You want to fact-check a claim before publishing \- You need talking points grounded in domain expertise \- You're creating content about a domain the SME covers Available SME sources: \- "conduit" — Pharmaceutical compounding compliance expert (USP 795/797/800, state regulations) Routing: pharma / USP 795·797·800 / sterile·non-sterile compounding / BUD / board-of-pharmacy compliance fact you must get right → call query_sme (the verified Conduit SME) to fact-check it BEFORE escalating to a human or deriving the rule yourself; cite its sources Input parameters: - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `context` (string): Optional context about why you're asking — helps the SME give a more relevant answer. E.g., "I'm creating a social media post about cleanroom best practices" - `question` (string, required): The question to ask the subject matter expert. Be specific and clear. - `sme_source` (string): Which Expert to consult, by key. "conduit" (pharmaceutical compounding compliance) is always available; your company may have additional Experts configured. Defaults to "conduit". ### `report_feedback` (~397 tokens) Report an error, issue, observation, or suggestion you encountered during your work. Use this proactively when you notice something noteworthy — tool failures, recurring problems, quality issues, or improvement ideas. This helps the founder track and act on agent insights over time. Routing: For issues YOU observe doing tenant work (tool failures, quality patterns) — lands in the operator's own observability feed. If the operator is reporting that FreedomOS ITSELF (platform UI/MCP/runtime) is broken or missing a capability, route to submit_product_request instead — FO product inbox only. Do NOT use submit_product_request for the tenant's own app/product/KB/retrieval gaps. [write-tier — first use may require a manager's approval; a from-now-on approval makes future calls seamless, a just-once approval re-asks next time.] Input parameters: - `category` (string, required): Type of feedback. error = something broke. warning = something might break. observation = pattern noticed. suggestion = improvement idea. blocker = cannot complete task. - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `context_json` (string): Optional JSON-encoded structured context (error codes, retry counts, URLs, timestamps, etc.). Example: "{\"status\":429,\"retries\":3}". - `description` (string, required): Detailed explanation. Include: what happened, what you expected, what you tried, and any error messages or codes. - `severity` (string): How urgent this is. Default: medium. Use critical only for data loss or security issues. - `title` (string, required): Short summary of the issue (1 line). Be specific — "Buffer API returns 429 on image posts" not "API error". - `tool_name` (string): The tool that was involved, if applicable (e.g., "generate_image_xai", "post_to_x"). ### `add_customer_evidence` (~362 tokens) Store one piece of REAL Customer Evidence for this company (paying-customer words/behavior, telemetry, review, operator-relayed quote, prospect signal, or agent-as-user). Evidence outranks generated ICP simulation. Use when the operator pastes a real customer quote, a call note, a review, or a provenanced usage signal — NOT for inventing personas (use Customer Hunter / create_icp for hypotheses). [write-tier — first use may require a manager's approval; a from-now-on approval makes future calls seamless, a just-once approval re-asks next time.] Input parameters: - `claim` (string, required): Short observation / takeaway (required, ≥8 chars). - `class` (string, required): Evidence class (determines rank weight). - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `may_not_auto_act` (boolean): If true (default), evidence must not auto-act without human/graduated path. - `may_open_loop` (boolean): If true, may open a work loop from this signal. Default false. - `may_refine_icp` (boolean): If true, may seed an ICP-delta offer later (never silent rewrite). Default false. - `may_steer_copy` (boolean): If true, may inform copy/messaging. Default true. - `observed_at` (string): Optional ISO timestamp when observed (default: now). - `quote` (string): Optional verbatim quote. - `source` (string, required): Provenance: "operator paste", "support ticket #…", "Amazon review", … - `subject_label` (string): Optional human label (e.g. Kendall) — not a global identity system. ### `list_customer_evidence` (~128 tokens) List ranked REAL Customer Evidence for this company (paying > telemetry > review > relayed > agent_as_user > prospect). Use before customer-facing work or when asked what real customers have said. Empty + company has ICPs = LOUD EMPTY (sim only — do not treat generated ICP as a customer). Input parameters: - `class` (string): Optional filter by class. - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `limit` (number): Max rows (default 25, max 100). ### `submit_product_request` (~782 tokens) File a bug report or feature request about FreedomOS the platform (FO UI, MCP tools, Command Center, auth, connectors, FO agents runtime) with the FreedomOS product team. Creates a FO product-inbox Command Center card and returns a request_id you can poll with get_product_request_status. ONLY for FreedomOS itself broken, missing, or confusing. Do NOT use for: (1) tenant ops (hire agents, send email, OKRs, content); (2) YOUR OWN company product — app code, domain knowledge base, chatbot/SME retrieval, compliance corpus, state/regulatory overlays, or anything your team can ship without FO engineers. Own-product gaps stay on YOUR company Command Center (decision/report card, collaboration, knowledge pipeline, or escalate to your human as product work). Example misroute: Conduit agent filing PCAI state-overlay KB work here — wrong inbox; file on Conduit instead. Routing: When the USER says something in FreedomOS itself is broken, missing, or confusing ("this button does nothing", "I wish it could…", "this is a bug", "can you debug this?" about FO product), this is the tool — FILE FIRST. Bias: submit_product_request(kind:"bug"|feature) before opening a live coding host or Send-to-Grok/Claude. REFUSE this tool for own-product / domain work: knowledge corpus, retrieval quality, compliance packs, chatbot answers for YOUR product (e.g. Compounding AI / PCAI), marketing claims about your app — keep those on the source company rail (Command Center card for your operator, suggest_collaboration, save_knowledge, Compliance Check), never FO product inbox. TRIAGE FIRST, briefly: if your own tools can resolve it right now (a reconnect, a setting, the wrong page), fix it and say so instead of filing — filing is never an exit from work you can finish yourself. Cap triage at one or two quick checks, never a debugging quest in chat. An explicit "file it" from the user always wins: file immediately, no pushback — and fold whatever you ruled out into the description. Pull title/repro fr… Input parameters: - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `description` (string, required): What happened / what you need. Include repro steps, expected vs actual, company name, agent name if relevant. - `kind` (string, required): bug = FO broken; feature = FO missing capability; question = how-to for the FreedomOS team. Not for your own app/product backlog. - `repro_steps` (string): Optional numbered repro steps. - `severity` (string): Default medium. critical = data loss / security / blocked onboarding. - `source_agent_name` (string): Optional: which of the operator's agents hit this (e.g. "Linnet", "Morgan"). - `suggested_fix` (string): Optional: what a good fix would look like (agent hypothesis — product team decides). - `title` (string, required): One-line summary. Specific: "Connect CTA dumps to Smart Tools instead of OAuth" not "bug". ### `get_product_request_status` (~110 tokens) Check status of a product request you previously filed with submit_product_request for your operator. Returns pending | approved | denied | dismissed | completed so you can tell your human when FreedomOS product team decides. Use when you hold a request_id and need an update for the filer. Input parameters: - `companyId` (string): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `request_id` (string, required): The request_id UUID returned by submit_product_request ### `open_product_request_draft_pr` (~166 tokens) Open a draft GitHub PR shell for an approved FreedomOS product request (work ticket branch, no auto-code). Use when product team accepted a low-stakes bug/feature and wants a tracking PR. Do NOT use for questions or high/critical items that need design first. [write-tier — first use may require a manager's approval; a from-now-on approval makes future calls seamless, a just-once approval re-asks next time.] Input parameters: - `companyId` (string): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `force` (boolean): Re-dispatch even if a draft_pr is already stamped (default false). - `request_id` (string, required): request_id UUID from submit_product_request ### `attach_product_request_pr` (~173 tokens) Attach an existing freedom-ai GitHub PR URL to a product request and **resolve it by construction** (card → approved, product_status=fixed, history comment, filer resolution notify). Use when you (or a coding agent) opened a real PR for the fix — no separate human close step. [write-tier — first use may require a manager's approval; a from-now-on approval makes future calls seamless, a just-once approval re-asks next time.] Input parameters: - `companyId` (string): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `pr_url` (string, required): https://github.com/linnetlegacies/freedom-ai/pull/NNNN - `request_id` (string, required): request_id UUID from submit_product_request ### `claim_product_request_for_builder` (~199 tokens) Mint a paste-ready Builder claim recipe for a FreedomOS product request so a host coding agent (Grok Build / Claude Code) with Harness + gstack can implement the class fix. Pins the FreedomOS frontier coding model (TIER_ROLES.frontier). Does NOT run the coding agent or open a PR by itself — use after product team accepted the request. FreedomOS product-inbox members only. [write-tier — first use may require a manager's approval; a from-now-on approval makes future calls seamless, a just-once approval re-asks next time.] Input parameters: - `companyId` (string): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `request_id` (string, required): request_id UUID from submit_product_request - `stamp_claim` (boolean): If true (default), stamp context_payload.builder_claim {claimed_at, frontier_model, by} on the card. ### `scan_product_signals` (~254 tokens) Scan a company for product-system bugs and unlocks (failed/timed-out activity runs, blocked_on_you cards, open error agent_feedback) and return ranked product-request candidates for the FreedomOS product team. Use when the product team is hunting class bugs/unlocks across a portfolio tenant (dry-run by default; set file_top_n to file up to 5 bug cards). Does NOT invent feature fantasy — bias is bugs/unlocks only. For FreedomOS product-inbox members only. [write-tier — first use may require a manager's approval; a from-now-on approval makes future calls seamless, a just-once approval re-asks next time.] Input parameters: - `companyId` (string): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `company_id` (string, required): Tenant company_id to scan (e.g. …_the-optimal-company- or a portfolio co). - `file_top_n` (number): If >0, file the top N signals as product_request decision cards (max 5). Default 0 = dry-run only. - `lookback_days` (number): How far back to look (1–60, default 14). ### `create_attention_directive` (~325 tokens) Queue a short instruction for an external coding/builder session (Grok terminal, Claude Code, or future FreedomOS runtime). Does NOT type into their UI — the session must poll FreedomOS (poll-fo-directives.sh or list_attention_directives) and act. Use when the operator says "tell Grok…", "have Claude…", or CoS should route reversible work off the call. Pass the same target_session_id the host polls (e.g. grok-, claude-). [write-tier — first use may require a manager's approval; a from-now-on approval makes future calls seamless, a just-once approval re-asks next time.] Input parameters: - `companyId` (string): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `company_id` (string): Optional company context (portfolio id). Does not change auth — row stays operator-scoped. - `instruction` (string, required): One clear instruction for that session (1–4000 chars). Imperative, not a transcript dump. - `source` (string): Optional provenance: voice_cos | chat | api | system. Default derived from door. - `target_host` (string): Host adapter: claude-code | claude-desktop | grok | manual | slack | github | freedomos | other - `target_session_id` (string, required): Stable id the host polls (1–200 chars). Examples: grok-$SESSION, claude-code-$SESSION. Must match the poller. ### `list_attention_directives` (~120 tokens) List pending attention directives for THIS operator (optionally filtered by target_session_id). Hosts (Grok/Claude) and CoS use this to see what is waiting. Does not ack — use ack_attention_directive after acting. Input parameters: - `companyId` (string): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `limit` (number): Max rows (1–50, default 20). - `target_session_id` (string): If set, only pending directives for this session id. ### `ack_attention_directive` (~152 tokens) Mark a pending attention directive as acked after the host session has taken the instruction. Use when YOU are Grok/Claude/a host builder and you just executed (or deliberately skipped) a directive you polled — for the same operator who owns the queue. Idempotent on already-acked → not found. [write-tier — first use may require a manager's approval; a from-now-on approval makes future calls seamless, a just-once approval re-asks next time.] Input parameters: - `companyId` (string): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `id` (string, required): Directive UUID from list_attention_directives or create response. ### `cancel_attention_directive` (~137 tokens) Cancel a pending attention directive (operator changed mind / wrong target). Use when the operator says drop/cancel that instruction to Grok or Claude, or CoS realizes the target_session_id was wrong — for THIS operator only. Does not reverse work the host already did. [write-tier — first use may require a manager's approval; a from-now-on approval makes future calls seamless, a just-once approval re-asks next time.] Input parameters: - `companyId` (string): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `id` (string, required): Directive UUID to cancel. ### `list_attention_sessions` (~161 tokens) List THIS operator's coding/builder sessions (status, goal, ask). Hygiene: drops stale hosts (no recent heartbeat) and blocked rows without a real ask. Use needs_me=true for "what needs me?" (blocked only). Use before create_attention_directive or when attending a blocked session. Input parameters: - `companyId` (string): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `include_stale` (boolean): If true, include sessions that failed freshness hygiene (default false). - `limit` (number): Max sessions (1–50, default 30). - `needs_me` (boolean): If true, only return blocked_on_operator sessions with a real fresh ask (attend targets). ### `request_attention_spawn` (~282 tokens) Request a NEW local coding session from voice/chat (tab spawn). Queues a sticky for the desk launcher on THIS operator's machine (host must run attention-launcher). Use when they say "start a Grok/Claude on …", "new build for …", "open a session for …". Does not open a cloud IDE — the local launcher opens Terminal + announces + optional first directive. [write-tier — first use may require a manager's approval; a from-now-on approval makes future calls seamless, a just-once approval re-asks next time.] Input parameters: - `companyId` (string): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `cwd` (string): Working directory on the operator machine (e.g. /Users/…/GitHub/freedom-ai). Prefer absolute paths they already use. - `first_instruction` (string): Optional first work sticky delivered after the new session announces (imperative). - `goal` (string, required): One-line goal for the new session (1–500 chars). - `host` (string, required): Which builder to open: grok (Terminal) | claude-desktop (Claude.app Code — preferred) | claude-code (Terminal CLI) - `session_id` (string): Optional stable session id; default auto-derived from host + project. ### `upsert_attention_session` (~271 tokens) Emit or update thin session telemetry for THIS operator (host coding agent self-announce). Use when YOU are Grok or Claude Code at session start / status change so voice CoS can list_attention_sessions and target you. Prefer tiny goals; never dump transcripts. [write-tier — first use may require a manager's approval; a from-now-on approval makes future calls seamless, a just-once approval re-asks next time.] Input parameters: - `ask_for_operator` (string): If blocked: one sentence the operator must answer - `companyId` (string): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `company_id` (string): Optional company id - `cwd` (string): Optional working directory - `goal` (string): One-line goal - `host` (string): claude-code | claude-desktop | grok | manual | slack | github | freedomos | other - `priority` (number): Optional priority (higher = sooner) - `project` (string): Optional project name - `session_id` (string, required): Stable session id (same string used as target_session_id for directives). - `status` (string): running | blocked_on_operator | done | parked | unknown (blocked_on_tim accepted as alias) ### `append_cos_preference` (~179 tokens) Append one durable speech/taste preference for THIS operator only (re-injected on their next voice session mint). Use when they say something was hard to follow, how cards should sound, or "remember I prefer…". For this user_id only — does not edit the shared FreedomOS CoS template. Apply the note in the current call when you can. [write-tier — first use may require a manager's approval; a from-now-on approval makes future calls seamless, a just-once approval re-asks next time.] Input parameters: - `companyId` (string): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `note` (string, required): One short preference (≤500 chars), e.g. "When describing cards, paraphrase titles — do not read dashes or ids aloud." ### `set_cos_preferences` (~129 tokens) Replace THIS operator's full CoS preference block (or clear with empty). Use when they want a full rewrite of saved preferences. Per user_id only — not a global product prompt edit. [write-tier — first use may require a manager's approval; a from-now-on approval makes future calls seamless, a just-once approval re-asks next time.] Input parameters: - `companyId` (string): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `cos_preferences` (string, required): Full preferences text (≤2000 chars). Empty string clears. ### `get_cos_preferences` (~68 tokens) Read THIS operator's saved CoS speech/taste preferences (user-scoped). Use when confirming what you will remember about how they like cards and talk. Input parameters: - `companyId` (string): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. ### `confirm_mcp_approval` (~269 tokens) Confirm a pending MCP capability approval by spoken (or chat) yes/no. Pass approval_id from the approval_required tool result. decision: approve | reject | later. Runs the SAME process-approval pipeline as tapping Approve on the card — does not bypass integrity rails. Use on voice when the operator says approve/yes or reject/no after a capability ask. Do NOT invent an approval_id. [write-tier — first use may require a manager's approval; a from-now-on approval makes future calls seamless, a just-once approval re-asks next time.] Input parameters: - `approval_id` (string, required): UUID of the pending mcp_tool_call approval card (from approval_required.approval_id) - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `decision` (string, required): approve | reject | later (yes/no/go also accepted) - `grant_mode` (string): approve only: 'once' runs without standing grant (default for spoken path); 'standing' also grants future calls - `utterance_snippet` (string): Optional short quote of what the operator said (audit; ≤200 chars) - `voice_session_id` (string): Optional voice session id if known (audit only) ### `add_lead` (~276 tokens) Add a new lead to the Leads CRM (crm_leads) — the table the Leads tab, triage, and outreach all use. Idempotent on (company, email) when an email is given. Provide at least an email OR a name. The lead appears on the Leads tab and is auto-triaged. Routing: CRM/sales → add a lead or prospect → use this [write-tier — first use may require a manager's approval; a from-now-on approval makes future calls seamless, a just-once approval re-asks next time.] Input parameters: - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `company_name` (string): Company they work for (optional) - `email` (string): Lead email (unique within company). Provide email or name. - `name` (string): Full name. Provide email or name. - `notes` (string): Initial notes about the lead (optional) - `phone` (string): Phone number (optional) - `source` (string): Where the lead came from (e.g. "linkedin", "referral", "website"). Defaults to "manual". - `tags` (array): Tags for filtering (optional) - `title` (string): Job title (optional) ### `update_lead` (~576 tokens) Edit an existing lead in the Leads CRM (crm_leads): name, email, phone, location, do-not-contact flag/reason, lifecycle state (new/active/flagged/archived), or the synopsis fields (title, company_name, tags, notes). Identify the lead with lead_id or email_lookup. Moving state to 'flagged' or 'archived' REQUIRES state_reason. Archiving sets archived_at (safe-archive, reversible — move state off archived to restore it). If the lead's outreach is set to auto and you move it off 'active', outreach is demoted back to manual (auto-outreach is only valid while active). Use when the operator or an agent needs to fix or maintain lead data — wrong email, bad name, DNC request, or a lifecycle move — instead of telling the user to edit it in the UI. Routing: CRM/sales → edit a lead's fields, status, or DNC flag → use this (NOT update_lead_status/log_activity — those are removed) [write-tier — first use may require a manager's approval; a from-now-on approval makes future calls seamless, a just-once approval re-asks next time.] Input parameters: - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `company_name` (string): Company they work for — folded into synopsis_jsonb.manual_entry. - `do_not_contact` (boolean): Set true to flag the lead do-not-contact (excluded from outreach); false to clear it. - `do_not_contact_reason` (string): Reason for do_not_contact, e.g. 'customer', 'churned', 'opted_out'. - `email` (string): New email (normalized to lowercase/trim). Rejected if it already belongs to another lead in this company. - `email_lookup` (string): The lead's CURRENT email, used to find it. Provide this OR lead_id. - `lead_id` (string): UUID of the lead to update. Provide this OR email_lookup. - `location` (string): New location. - `name` (string): New full name. - `notes` (string): Notes about the lead — folded into synopsis_jsonb.manual_entry. - `phone` (string): New phone number. - `state` (string): New lifecycle state. state_reason is REQUIRED when moving to 'flagged' or 'archived'. - `state_reason` (string): Reason for the state change. Required when state is 'flagged' or 'archived'. - `tags` (array): Replacement tag list — folded into synopsis_jsonb.manual_entry. - `title` (string): Job title — folded into synopsis_jsonb.manual_entry (other manual_entry keys are preserved). ### `list_deals` (~118 tokens) List CRM deals for the current company. Filter by stage and limit. Returns deals with their associated contacts. Routing: CRM/sales → see open pipeline → use this Input parameters: - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `include_closed` (boolean): Include closed deals (default false) - `limit` (number): Max number of deals to return (default 20, max 100) - `stage` (string): Filter by stage (optional) ### `get_lead_pipeline_snapshot` (~145 tokens) Aggregate counts of the Leads CRM (crm_leads) for the current company: active leads by temperature (warm/cold/…/unset) and lifecycle stage, plus do-not-contact and archived totals. THE source of truth for "how many leads do we have and how warm are they" — never estimate or zero-fill lead counts; call this instead. Read-only. Note: paying customers live in Stripe (get_subscription_stats), not here. Routing: CRM/sales → lead counts or pipeline temperature snapshot → use this Input parameters: - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. ### `segment_leads` (~267 tokens) Organize, select, or clear a lead segment on the Leads tab by its exact source tag (e.g. 'csv:apc-cch-2024'). Validates the tag against the company's live segment tags and returns the exact-token filter plus a server-computed lead count (excluding do-not-contact, archived, and test leads). Read-only: the Leads tab applies the action; this tool changes no data and CANNOT enroll anyone — enrollment only happens via the Enroll button on the Leads tab. Use when the operator wants to focus the Leads tab on one segment or event — group it, select all its leads for enrollment, or clear that selection. Routing: CRM/sales → select or organize leads by segment/event tag → use this Input parameters: - `action` (string, required): 'organize' = group Leads tab by this segment; 'select' = select all leads in it; 'clear' = clear that selection. - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `segment_tag` (string, required): Exact segment tag token from crm_leads.source, e.g. 'csv:apc-cch-2024'. No substring matching — must match a live tag exactly. ### `list_segments` (~146 tokens) List the live lead segment tags for the current company with server-computed lead counts (excluding do-not-contact, archived, and test leads). Segments are the exact comma-separated tokens in crm_leads.source (CSV event imports, website, etc.). Read-only — returns tags and counts only, never lead names/emails. Use when the operator asks which lead segments or event tags exist, or before segment_leads to resolve a loosely-named segment to its exact tag. Routing: CRM/sales → what lead segments/events exist → use this Input parameters: - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. ### `send_email` (~654 tokens) Send an outbound email via the company's Resend connection. Resolves the per-company Resend API key + from identity, then sends to a single recipient. Honors the do_not_contact suppression list (crm_leads): if the recipient is marked do_not_contact, the send is refused. RECIPIENT RULE: when emailing a CRM LEAD, do NOT type their address yourself — draft with draft_lead_email/draft_outreach and deliver with send_lead_draft, which reads the lead's real email from the database. Only pass `to` directly for a non-lead recipient whose exact address the operator literally provided in this conversation. NEVER guess, infer, or fabricate an email address — a wrong guess sends a real email to a stranger. Use when the operator gives you an exact non-lead recipient address to email; for CRM leads use send_lead_draft instead. Routing: Send an outbound email to an operator-given address → use this; for CRM leads use send_lead_draft (DB-derived recipient, respects do_not_contact) [outbound-tier — EVERY call needs a manager's approval (per-send human rail): each request queues its own approval card and sends exactly once on approve. There is no standing grant for this tool.] Input parameters: - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `company_id` (string): Company UUID. Optional — defaults to the caller's company context. Used to resolve the Resend key and scope the do_not_contact check. - `draft_id` (string): Optional UUID of the lead_drafts row being sent. If provided, the Resend email id returned by the send is recorded onto that draft (resend_email_id) so engagement webhook events (opens/clicks/replies… - `from` (string): Optional explicit from address (e.g. "Jane "). If omitted, defaults to no-reply@. - `html` (string): HTML body of the email. Provide html and/or text (at least one is required). - `lead_id` (string): Optional UUID of the crm_leads row this email targets. Used for telemetry/linking; the do_not_contact check is keyed on (company_id, to) regardless. - `reply_to` (string): Optional Reply-To address. - `sequence_id` (string): Optional UUID of the outreach_sequences row backing an autonomous warm send. Required ONLY on the outreach-autosend path (executionSource=autonomous_warm); the warm-send gate verifies the sequence is… - `subject` (string, required): Email subject line. - `text` (string): Plain-text body of the email. Provide text and/or html (at least one is required). - `to` (string, required): Recipient email address (single recipient). ### `sync_stripe_conversions` (~172 tokens) Record won deals from the company's connected Stripe so lead→paid conversion becomes measurable. Reads paid Stripe customers (read-only), matches them to leads by email, and records a closed_won deal per paying customer (idempotent — re-running is safe, never double-counts). Only works if Stripe is connected. Use when conversion "isn't measured yet" or to refresh the conversion picture. Routing: CRM/sales/revenue → measure conversion / record won deals from Stripe → use this [write-tier — first use may require a manager's approval; a from-now-on approval makes future calls seamless, a just-once approval re-asks next time.] Input parameters: - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. ### `query_lead_journey` (~119 tokens) Reconstruct the full journey of a lead — what they did on the site, what they signaled, what we have already sent them. Returns structured data that downstream synthesis or drafting tools consume. Use this as the first step before synthesizing a hypothesis about why a lead behaved a certain way or drafting outreach to them. Input parameters: - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `lead_id` (string, required): UUID of the lead in the leads table. ### `synthesize_lead_hypothesis` (~233 tokens) Given a lead journey (from query_lead_journey), produce a structured hypothesis: intent score, conversion-failure mode, suggested outreach angle, and notes for drafting. Writes the synthesis back to leads.synopsis_jsonb so the Leads tab UI sees it. Use this after journey reconstruction, before draft_outreach. [write-tier — first use may require a manager's approval; a from-now-on approval makes future calls seamless, a just-once approval re-asks next time.] Input parameters: - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `company_context` (string): Optional short summary of the company the lead arrived at (e.g., 'Acme Health — pharmacy compounding compliance consulting for US pharmacies'). Helps the model evaluate fit. - `journey_json` (string, required): JSON-encoded journey object returned by query_lead_journey. Caller should JSON.stringify the journey output before passing. - `lead_id` (string, required): UUID of the lead. Used to persist synthesis back to leads.synopsis_jsonb. ### `draft_outreach` (~862 tokens) Produce two outreach draft variants (A/B) for a lead given an angle. Both drafts are warm and kind by design (P10) — variants differ in angle of helpfulness (subject hook, opening framing, call-to-action) not in tone. Drafts are written to lead_drafts as pending_review. Returns IDs + previews. Use after synthesize_lead_hypothesis to draft initial outreach. [write-tier — first use may require a manager's approval; a from-now-on approval makes future calls seamless, a just-once approval re-asks next time.] Input parameters: - `angle` (string, required): The outreach angle to use (e.g., 'deeper_lp3_discovery', 'lighter_touch_different_hook', 'jurisdiction_clarification', 'kind_check_in'). Take from synthesize_lead_hypothesis.suggested_angle if unsure. - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `company_context` (string): Optional short summary of the company the lead arrived at (e.g., 'Acme Health — pharmacy compounding compliance consulting'). Helps the model pitch correctly. - `eligible_at` (string): Optional ISO timestamp — the earliest real time this draft may be sent (2026-07-13 send-timing gate). For a sequence step, pass now + that step's delay_hours (an ESTIMATE; the send-gate re-stamps it… - `from_name` (string): Optional sender display name (e.g., 'Acme Team', 'Alex at Acme'). Used in draft signature. When omitted, the CONTRACT-5 chain resolves it: the company's mcp_connections.resend.auth_config.from_name,… - `journey_summary` (string, required): Short prose summary of what we know about this lead (their state, recent activity, what they engaged with). Used as context for the draft. Synthesis.intent_summary + 1-2 notes works well. - `lead_id` (string, required): UUID of the lead. - `regenerated_reason` (string): Optional (regenerate-on-signal, 2026-07-15). When the sequencer re-drafts a not-yet-sent step after a meaningful lead signal (temperature flip to hot, a click), it passes a short human-readable reaso… - `reply_to` (string): Optional Reply-To address to carry on the eventual send (CONTRACT-1 agent thread address). Stamped into both drafts' metadata (best-effort — the metadata column is additive); send_lead_draft reads it… - `sequence_id` (string): Optional. The outreach_sequences.id the step belongs to. Pass it together with sequence_step_id to enable the A/B prior-stats bias — step ids repeat across sequences (step1…stepN), so stats are only… - `sequence_step_id` (string): Optional. If this draft is part of an auto-mode sequence step, pass the step_id from outreach_sequences. Otherwise omit (manual one-off draft). - `variant_b_guidance` (string): Optional (CONTRACT-3). Sequence-designed seed for the B variant — a distilled subject+body angle persisted on the sequence step (steps jsonb, additive variant_b_guidance key). When present, variant_b… ### `send_lead_draft` (~210 tokens) Send an approved outreach draft to its lead via the company's Resend connection, then mark the draft 'sent'. This is the manual human-in-the-loop send: it delivers exactly one lead_drafts row (by id) to the lead's email and records sent_at + resend_message_id. Honors the do_not_contact suppression list (the send is refused if the lead is suppressed). Use after an operator approves a draft in the Leads tab. Routing: Operator approved an outreach draft and wants to send it → use this [outbound-tier — first use may require a manager's approval; a from-now-on approval makes future calls seamless, a just-once approval re-asks next time.] Input parameters: - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `draft_id` (string, required): UUID of the lead_drafts row to send. - `reply_to` (string): Optional Reply-To address for the outbound email. ### `get_product_context` (~150 tokens) Returns THIS company's product truth — the operator-authored offer + the SHIPPED, marketable capabilities (what the product does, and what it cannot do). Call this before describing, marketing, pricing, positioning, or selling the product. Ground every product claim in what this returns; never invent capabilities or an offer. If it reports the product is not defined, escalate to the operator instead of guessing. Routing: product / offer / what we sell / pricing / positioning / marketing or sales copy → call get_product_context FIRST; never fabricate capabilities or an offer Input parameters: - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. ### `get_grain_policy` (~121 tokens) Read the content-grain (wisdom-layer) publish policy for the current company. For each content grain it returns whether an agent may publish that grain autonomously (gate_mode 'autonomous') or must route to a human (gate_mode 'human_pre_gate'), plus curate_only and source_corpus_ref. Use this to understand which content you may publish on your own vs. send for human pre-approval. Input parameters: - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. ### `set_grain_policy` (~292 tokens) Create or update the wisdom-layer publish policy for ONE content grain in the current company. gate_mode 'human_pre_gate' reserves the grain for human approval; 'autonomous' lets an agent publish it directly. A brand-new grain defaults to human_pre_gate (fail-safe). Because this governs an agent's own publishing autonomy, the change routes to operator approval — it does not take effect silently. [sensitive-tier — first use may require a manager's approval; a from-now-on approval makes future calls seamless, a just-once approval re-asks next time.] Input parameters: - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `curate_only` (boolean): If true, an agent may only assemble this grain from source_corpus_ref, never originate de-novo content. - `gate_mode` (string): 'autonomous' = an agent may auto-publish this grain; 'human_pre_gate' = it must route to a human first. - `grain` (string, required): The content grain key, lowercase_with_underscores (e.g. faith_values, harness_education, professional). - `note` (string): Human-readable note on why this grain has this policy. - `source_corpus_ref` (string): For curate_only grains: the corpus an agent may assemble from (e.g. a knowledge collection key). ### `get_check_telemetry` (~239 tokens) Read recent quality-check telemetry for the current company. Returns per-(run,check) verdicts (pass/fail/flag/hold/error/skipped) across the brand/legal/ethics/security gates, the Pledge stamp, the ICP consult, and the craft gate — so you can see which checks fire findings, which HOLD content (false-hold rate), and which run clean. Use it to answer 'which gate holds the most for this company' or 'has the security gate ever fired on these posts'. Free-text preview fields are tagged as data. Input parameters: - `check_name` (string): Optional filter: brand | legal | ethics | security | pledge_stamp | icp_quality | craft. - `companyId` (string, required): FreedomOS company id to act within (you must be a member). Required for company-scoped tools. - `content_grain` (string): Optional filter by content grain (the safety/topic axis). - `limit` (number): Max rows to return (default 50, hard cap 200). - `verdict` (string): Optional filter: pass | fail | flag | hold | error | skipped. ## Diagnostics Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-getfreedomos-freedom-mcp/functions-v1-freedom-mcp#diagnostics ## Score history - 2026-08-04: 67 - 2026-08-03: 66 - 2026-08-02: 66 - 2026-08-01: 65 - 2026-07-31: 64 - 2026-07-30: 47 - 2026-07-29: 57 - 2026-07-28: 57 - 2026-07-27: 56 - 2026-07-26: 56 ## Links - Remote endpoint: https://twuluxmoognlwtmaoqgo.supabase.co/functions/v1/freedom-mcp - Authorisation metadata: https://twuluxmoognlwtmaoqgo.supabase.co/.well-known/oauth-protected-resource/functions/v1/freedom-mcp - Website: https://getfreedomos.com/ - Changelog RSS feed: https://verifymcp.io/servers/com-getfreedomos-freedom-mcp/functions-v1-freedom-mcp/changelog.xml - Changelog JSON feed: https://verifymcp.io/servers/com-getfreedomos-freedom-mcp/functions-v1-freedom-mcp/changelog.json - HTML version of this page: https://verifymcp.io/servers/com-getfreedomos-freedom-mcp/functions-v1-freedom-mcp