Search across all documents using semantic search.

Use this to find documents relevant to a topic, question, or keyword. Returns ranked results with snippets and source paths.

Args: query: The search query (natural language or keywords) folder_path: Optional folder path to scope the search (e.g. "/contracts") top_k: Max number of results to return (default 10)

Grep across document content using pattern matching (like ripgrep).

Use this to find exact text matches, regex patterns, or specific strings across all documents. Returns line-level matches with context.

Args: pattern: The search pattern (regex by default, or exact string) regex: Whether to use regex matching (default True) case_sensitive: Whether the search is case-sensitive (default False) folder_path: Optional folder path to scope the search top_k: Max number of chunk results to return (default 20)

List documents in a folder or the entire document library.

Use this to browse the document library, see what files exist, and explore folder structures.

Args: folder_path: Folder path to list (default "/" for root) source_system: Filter by source (e.g. "google_drive", "microsoft_graph", "workspace") max_items: Max number of items to return (default 100)

Search within a specific folder using semantic or keyword matching.

Combines folder-scoped search with AI-synthesized answers. Good for asking questions about documents in a specific folder.

Args: query: The search query or question folder_path: Folder path to search within search_mode: "semantic" (default) or "exact" or "regex"

Create a new document (report, memo, brief, etc.).

Generates and stores a document in the specified format and target.

Args: title: Document title body: Document content/body text format: Output format — "docx", "pdf", "xlsx", "pptx", "gdoc", "gsheet", "gslides", "md" target_suite: Where to store — "internal_library", "google_workspace", "microsoft_365"

Create a new spreadsheet.

Args: title: Spreadsheet title body: Optional initial content or description target_suite: Where to store — "internal_library", "google_workspace", "microsoft_365"

Create a new presentation / slide deck.

Args: title: Presentation title body: Optional content description or outline target_suite: Where to store — "internal_library", "google_workspace", "microsoft_365"

Send a message to the document intelligence agent.

Use this for general document questions, analysis, comparisons, or any document operation not covered by the specific tools above.

Args: message: Your message or question for the document agent action: Agent action — "chat", "compare_versions", "export_evidence_pack", etc.

Dispatch a message to any domain agent on the platform.

Available domains: finance, crm, engineering, legal, hr, it_ops, content, commerce, product, document_intelligence.

Args: domain: The domain agent to talk to message: Your message or objective action: The action to perform (default "chat") inputs: Optional JSON string of additional structured inputs

Get the Lightbulb software-delivery context packet before editing code.

Use this from Claude Code, Codex, or Cursor before making a repo change. It gathers IT/Ops, coding workspace, project-management, deployment, CloudOps, connector, memory, and approval context under the authenticated user's RBAC scope.

Run the governed software loop from MCP: feedback/SDLC -> coding -> PR -> deploy.

This is the main bridge for external coding tools. It routes through Lightbulb's IT/Ops orchestrator so repo binding, SDLC context, CloudOps, GitHub, HITL, tests, container release, and deployment gates travel together.

Request a bounded urgent production/cloud fix through the Lightbulb loop.

Defaults are intentionally conservative: preview mode on, PR on, deploy off. Production or cloud-impacting fixes are routed with approval gates and CloudOps/deployment context rather than direct mutation.

Create a new page builder session to build a website or landing page.

Returns a session ID you can use with page_builder_chat to iteratively design and build pages.

Args: brand_name: The brand/company name for the site initial_prompt: Optional initial instruction (e.g. "Build a landing page for our SaaS product") force_page_builder: If true, create a pure Page Builder design session instead of routing project-build intent to consulting workflow.

List existing page builder sessions.

Send a message to a page builder session to design or modify pages.

The page builder agent generates HTML/CSS/JS for your website. Use iterative messages to refine the design.

Args: session_id: The session ID from page_builder_create message: Your instruction (e.g. "Add a pricing section with 3 tiers")

Deploy a page builder session to make the site live.

Args: session_id: The session ID page_key: Optional specific page to deploy (deploys all if empty)

Get the preview URL for a page builder session.

Args: session_id: The session ID

Execute a research, analysis, or code generation task via the backbone agent.

The backbone agent runs server-side, scoped to your tenant — it has a Python REPL, web search, and access to your account's connectors, all operating under your JWT and the platform's RBAC. This is not local code execution on the customer's machine; nothing leaves the platform's scope.

Use it for complex multi-step analysis, data processing, or generating code/scripts.

Args: objective: What you want the backbone agent to do inputs: Optional JSON string of structured inputs

Start or continue the Lightbulb consulting project workflow through Backbone.

Use this instead of jumping directly to coding, GitHub, deployment, connector mutation, or external communications when a user has a project idea, custom agent request, workflow automation request, SOP/process change, modernization request, or build request that still needs discovery, requirements, scope, SOP impact or referenced SOPs, approval gates, and execution work packets.

Args: objective: The project idea or business outcome the user wants to achieve. project_context: Optional JSON object with known facts, current systems, requirements, constraints, uploaded-doc references, or host context. project_id: Optional existing Lightbulb project identifier to continue. source: Host/source string such as codex, claude_code, chatgpt, cursor, or mcp.

List all code workspaces available to you.

Code workspaces are persistent environments with file systems, git, and execution capabilities.

Send a message to a code workspace — ask it to write code, run commands, analyze files.

Args: workspace_id: The workspace ID to interact with message: Your instruction or question action: Optional coding action such as chat, explain_code, or propose_changes. propose_changes is normalized to preview chat mode for backend compatibility. conversation_id: Optional conversation/thread ID for continuity active_file: Optional active file path to bias the coding agent history: Optional JSON array of prior chat messages attachments: Optional JSON array of attachments context: Optional JSON object with structured coding context policy: Optional JSON object with workspace policy overrides preview_mode: If true, return proposed changes without mutating files auto_push: If true, allow the coding run to auto-push after verification

Get the active coding run for a workspace, if one exists.

Get the details for a specific coding run.

Wait for a coding run to finish and return its latest status.

If run_id is omitted, the tool waits for the current active run.

List artifacts — charts, reports, analyses, code, and other outputs from agent runs.

Args: artifact_type: Optional filter by type (e.g. "chart", "report", "code", "csv")

Get the full content of a specific artifact.

Args: artifact_id: The artifact UUID

Register an artifact you created OUTSIDE Lightbulb so Lightbulb's domain agents can discover, reference, and work on it.

Use this whenever you (Claude, Claude Code, ChatGPT, Codex, Hermes, etc.) produce something external while orchestrating Lightbulb — a code repository, document, slide deck, spreadsheet, report, or any URL — and you want it to become a first-class, discoverable Lightbulb artifact (searchable via list_artifacts and routable to domain agents / code workspaces).

Args: type: Artifact class — one of: codebase, document, slide_deck, spreadsheet, report, url. title: Human-readable title. summary: Short description of what it is and why it matters. uri: External reference (e.g. a GitHub repo URL, Google Doc URL, file link). Provide this OR content. content: Inline text content (for documents/reports) when there is no external URL. project_id: Optional Lightbulb project UUID to associate the artifact with. source_agent: The agent that created it (e.g. "claude_code", "codex", "chatgpt", "hermes"). attach_workspace: For a codebase artifact with a repo uri, also clone it into a Lightbulb Code Workspace so domain agents can work on it (not just discover it).

List workflow definitions available on the platform.

Trigger a workflow execution.

Args: workflow_type: The workflow type to trigger (e.g. "enterprise_document_intelligence") objective: What the workflow should accomplish inputs: Optional JSON string of structured inputs

Query the RAG knowledge base directly with a question.

Returns relevant passages from indexed documents with citations.

Args: question: Your question top_k: Number of results to return (default 5)

Upload a document to the RAG knowledge base for indexing.

Args: filename: The filename (e.g. "meeting-notes.md") content: The document content (text)

List all available connectors and their connection status.

Shows which integrations (Slack, HubSpot, Stripe, etc.) are connected.

Invoke a platform tool directly by name.

Tools include connector operations (e.g. "hubspot.list_contacts"), utility tools, and more. Use list_connectors to see available tools.

Args: tool_name: The tool to invoke (e.g. "slack.post_message") arguments: JSON string of tool arguments

List CRM contacts, optionally filtered by search query.

Args: search: Optional search term to filter contacts limit: Max results (default 20)

List CRM deals/opportunities.

Args: search: Optional search term limit: Max results (default 20)

List recent notifications — HITL decisions, workflow alerts, system messages.

Args: limit: Max results (default 20)

List all pending approval tasks waiting for your decision.

These are human-in-the-loop (HITL) decisions from agent workflows — things like purchase approvals, content sign-offs, or deployment gates that require a human to approve or reject before the agent continues.

Get full details of a pending approval task before deciding.

Shows the agent's reasoning, proposed action, risk assessment, and any supporting evidence.

Args: task_id: The approval task UUID

Approve a pending HITL task, allowing the agent workflow to continue.

This is a real decision — the agent will proceed with the proposed action. Review the task details first with get_approval_details.

Args: task_id: The approval task UUID comments: Optional reason for approval

Reject a pending HITL task, stopping the agent workflow.

The agent will not proceed with the proposed action.

Args: task_id: The approval task UUID comments: Reason for rejection

Store a value in the platform's agent memory.

Use this to persist information across conversations and sessions.

Args: key: Memory key (e.g. "user_preferences", "project_context") value: The value to store namespace: Memory namespace (default "default")

Recall a value from agent memory.

Args: key: Memory key to recall namespace: Memory namespace (default "default")

Search agent memory semantically.

Args: query: What to search for namespace: Memory namespace (default "default") top_k: Number of results (default 5)

List companies in the user's tenant.

ADMIN and TENANT users need to select a company before using domain agents, CRM, finance, or other company-scoped operations. COMPANY users already have a company set automatically.

Select a company context for subsequent operations.

ADMIN and TENANT users must select a company before using domain agents or other company-scoped features. This determines which CRM data, financial accounts, connectors, etc. you're working with.

Args: company_id: The company UUID from list_companies

Show your identity, role, tenant, company, and what you can access.

Use this to understand your current context — especially useful for debugging permission issues or confirming which company is selected.

List connected integrations for the current company context.

Shows what data sources are connected — QuickBooks, Stripe, HubSpot, Google Drive, Slack, etc. Helps you understand what data is available before running domain agent actions.

List all available domain agents and their capabilities.

Shows every domain agent on the platform with their supported actions.

List available actions for a specific domain agent.

Args: domain: The domain name (e.g. "finance", "crm", "legal")

Run any Stripe-orchestrator (resource, verb) op.

Routes through the policy → simulator → Merkle audit → execute/queue chokepoint, exactly like our internal agents.

Args: resource: e.g. "customers", "subscriptions", "refunds", "tax_calculations" verb: e.g. "create", "retrieve", "update", "list", "cancel" op_inputs: JSON object of operation inputs as string. stripe_account_id: Optional connected-account id.

Governed long-tail Stripe API request for /v1 or /v2 endpoints.

Non-GET requests still route through the platform's simulator, audit, idempotency, and human-approval gate before execution.

Args: api_path: Stripe API path, e.g. "/v1/setup_intents". method: GET, POST, or DELETE. params: JSON object of request parameters. stripe_account_id: Optional connected-account id. base_address: Optional Stripe base address, e.g. "api", "connect", "files".

Fast Postgres-backed read of the Stripe Digital Twin (no Stripe RTT).

Args: resource_kind: e.g. "customer", "subscription", "invoice", "charge" limit: Max rows to return (default 50, cap 100).

List Stripe-orchestrator approvals waiting for human action.

Approve a pending Stripe orchestrator decision so it can execute.

Reject a pending Stripe orchestrator decision.

Execute a previously-approved Stripe decision (idempotent replay safe).

Predictive forecast for the merchant: MRR, failed-payment rate, dispute risk band, payout cashflow band. Server-computed; no Stripe RTT.

Composite health score per connected Stripe account, plus the at-risk subset (score < 60) for direct triage.

Run a high-level composite workflow.

Args: workflow: One of workflow.failed_payment_recovery, workflow.churn_save_outreach, workflow.dispute_evidence_drafting, workflow.subscription_health_audit

Multi-org Xero financial snapshot (cash, AR, AP, payroll, taxes).

Args: body: Optional JSON object of filters (e.g. {"xero_tenant_ids": ["..."]})

Generate Xero proposals (reconciliation, AP, payroll, etc.).

Args: body: Optional JSON object (e.g. {"kind": "bank_reconciliation"})

Create a Xero proposal (queues an HITL approval). Body is JSON.

Approve a Xero proposal so it can execute.

Reject a Xero proposal.

Trigger a Xero data sync (orgs, AR/AP, payroll, ledger).

Run a Xero playbook.

Args: playbook_id: month_end_close, ar_followup, ap_intake_to_pay, bank_reconciliation, payroll_trueup, reporting_pack, consolidation. body: Optional JSON object of inputs.

Get the Xero org profile (chart of accounts, tax rates, branding).

Propose an AR invoice into Xero (HITL-gated). Body is JSON.

Propose an AP bill into Xero (HITL-gated). Body is JSON.

Propose a manual journal into Xero (HITL-gated). Body is JSON.

Propose a payroll true-up into Xero (HITL-gated). Body is JSON.

List voice agent executions (live and historical phone calls).

Args: status: Optional filter (active, completed, failed, transferred) limit: Max results

Get a voice execution detail (transcript, status, agent decisions).

List in-call HITL approvals waiting for caller-side decision.

Approve a pending in-call voice action.

Reject a pending in-call voice action.

Approve a voice action with modifications. modifications is a JSON object.

BambooHR who's-out roster (current and upcoming time-off).

BambooHR leave balance for an employee.

Monday.com board for an HR onboarding checklist.

HR case-board items from Monday.com.

List Greenhouse jobs.

List Greenhouse applications.

Advance a Greenhouse candidate to the next stage (HITL-gated).

Reject a Greenhouse application (HITL-gated).

Health check for HR connector tokens (BambooHR / Greenhouse / Monday).

Get collaboration info (members, share-links, pending requests).

Add a collaborator to a workspace (role: viewer | editor | admin).

Change a collaborator's role.

Revoke a collaborator's access.

Create a share-link token granting access to the workspace.

Revoke a share link.

Approve a pending access request.

Deny a pending access request.

Append a note to a workspace (visible to collaborators).

List historical coding runs for a workspace.

Aggregate run-quality insights for a workspace.

Submit a human review verdict for a run (accept | reject | request_changes).

Apply review-suggested changes to the workspace.

List code-change proposals for a workspace.