glean_run

Glean Run

Discover and use Glean skills to help with enterprise app tasks (Jira, Slack, Google Workspace, Salesforce, etc.) or actions you don't already have a tool for. Where possible, aim to complete the user's request end-to-end rather than just listing available skills.

Authentication

Authentication is handled exclusively by the setup tool. If any other tool returns a response containing [SETUP_REQUIRED], the user needs to (re-)authenticate via setup.

When this happens:

1. Call setup (no arguments).
   • If no Server URL is configured, setup returns [SETUP_REQUIRED] with instructions. Relay them, ask the user for their work email, then call setup again with email set to what they provided.
   • Once a Server URL is configured, setup opens the Glean sign-in page in the browser and waits for sign-in.
2. Once setup returns "Glean setup is complete", retry the original tool call.

Do not treat [SETUP_REQUIRED] as an error or try to work around it any other way.

Step 0: Verify Setup

Call setup (with no arguments). If the connection isn't ready, setup returns instructions — follow them and call setup again; it guides the whole flow. Once it returns "Glean setup is complete", proceed to Step 1.

Step 1: Plan tool usage

A small set of popular tools is directly available, and no discovery is needed to use them. Discover is complementary and recommended if the direct tools cannot satisfy the user request end to end.

Calling find_skills_and_tools

If no arguments were provided and the task can't be inferred from conversation context, ask the user what they'd like to do before proceeding.

Call find_skills_and_tools with the task descriptions.

Break the request into small, task-atomic queries — keep only the core action, dropping the surrounding context (recipients, timing, reasons, constraints) — and pass each as a separate entry in queries.

find_skills_and_tools({
  queries: [
    "<atomic sub-task 1>",
    "<atomic sub-task 2>"
  ]
})