← WebMCP Directory

Tool tree

leia-theta.vercel.app

AI & AgentsTools verified
Website
Seven AI specialists, one orchestrator — a shared workspace you and your agent command together. WebMCP-enabled.
Explore capabilities
    delegate_taskAction

    Give a task to Leia's team of AI specialists. Leia (the orchestrator) picks the best-suited companion, that companion does the work, and you get the result plus who handled it. Use this when you don't know or don't care which specialist should do the job. Note: this costs real money on a real API key, so it doesn't run immediately — it waits for the human using this page to approve it. You'll get back a "pending" response, not the result; check get_team_status later to see if it ran.

    View tool JSON
    {
      "name": "delegate_task",
      "kind": "act",
      "impl": "imperative",
      "description": "Give a task to Leia's team of AI specialists. Leia (the orchestrator) picks the best-suited companion, that companion does the work, and you get the result plus who handled it. Use this when you don't know or don't care which specialist should do the job. Note: this costs real money on a real API key, so it doesn't run immediately — it waits for the human using this page to approve it. You'll get back a \"pending\" response, not the result; check get_team_status later to see if it ran.",
      "inputSchema": {
        "type": "object",
        "properties": {
          "task": {
            "type": "string",
            "description": "The task to hand over, in plain language. Any language works."
          }
        },
        "required": [
          "task"
        ]
      }
    }
    ask_companionAction

    Ask one specific companion directly, bypassing Leia's routing. Companions: Smith (code), Scout (research with live web search), Keeper (session context & memory), Scribe (writing), Planner (plans & estimates), Warden (critical review), Analyst (numbers & data). Use list_companions for full roles. Note: this costs real money on a real API key, so it doesn't run immediately — it waits for the human using this page to approve it. You'll get back a "pending" response, not the answer; check get_team_status later to see if it ran.

    View tool JSON
    {
      "name": "ask_companion",
      "kind": "act",
      "impl": "imperative",
      "description": "Ask one specific companion directly, bypassing Leia's routing. Companions: Smith (code), Scout (research with live web search), Keeper (session context & memory), Scribe (writing), Planner (plans & estimates), Warden (critical review), Analyst (numbers & data). Use list_companions for full roles. Note: this costs real money on a real API key, so it doesn't run immediately — it waits for the human using this page to approve it. You'll get back a \"pending\" response, not the answer; check get_team_status later to see if it ran.",
      "inputSchema": {
        "type": "object",
        "properties": {
          "companion": {
            "type": "string",
            "description": "Name of the companion, e.g. \"Scout\"."
          },
          "question": {
            "type": "string",
            "description": "What to ask them."
          }
        },
        "required": [
          "companion",
          "question"
        ]
      }
    }
    list_companionsAnswer

    List Leia's team: every companion's name and specialty. Call this first if you're unsure who does what.

    View tool JSON
    {
      "name": "list_companions",
      "kind": "answer",
      "impl": "imperative",
      "description": "List Leia's team: every companion's name and specialty. Call this first if you're unsure who does what.",
      "inputSchema": {
        "type": "object",
        "properties": {}
      }
    }
    get_team_statusAnswer

    See what the team is doing right now in this session: which companions are busy with what, plus the most recent completed work. The human sees the same thing in the 3D scene.

    View tool JSON
    {
      "name": "get_team_status",
      "kind": "answer",
      "impl": "imperative",
      "description": "See what the team is doing right now in this session: which companions are busy with what, plus the most recent completed work. The human sees the same thing in the 3D scene.",
      "inputSchema": {
        "type": "object",
        "properties": {}
      }
    }
    recall_workspace_memoryAnswer

    Search the shared session workspace — everything the human and you have done here so far (tasks, who handled them, outcomes). The workspace is per-session and shared between the human user and their agent, so use this to build on earlier work instead of repeating it.

    View tool JSON
    {
      "name": "recall_workspace_memory",
      "kind": "answer",
      "impl": "imperative",
      "description": "Search the shared session workspace — everything the human and you have done here so far (tasks, who handled them, outcomes). The workspace is per-session and shared between the human user and their agent, so use this to build on earlier work instead of repeating it.",
      "inputSchema": {
        "type": "object",
        "properties": {
          "query": {
            "type": "string",
            "description": "What to look for, e.g. \"the plan Planner made\" or \"pricing research\"."
          }
        },
        "required": [
          "query"
        ]
      }
    }
    list_boardAnswer

    Read the shared workspace board — the CURRENT PLAN both the human and you edit together. Items have an id (like b1), a title, an optional note, and a status: todo, doing or done. Always read the board before adding or changing items, so you build on the human's plan instead of duplicating it. This is real state on the page, not generated text.

    View tool JSON
    {
      "name": "list_board",
      "kind": "answer",
      "impl": "imperative",
      "description": "Read the shared workspace board — the CURRENT PLAN both the human and you edit together. Items have an id (like b1), a title, an optional note, and a status: todo, doing or done. Always read the board before adding or changing items, so you build on the human's plan instead of duplicating it. This is real state on the page, not generated text.",
      "inputSchema": {
        "type": "object",
        "properties": {}
      }
    }
    add_board_itemAction

    Add an item to the shared workspace board the human is looking at. Use this to lay out a plan, capture decisions, or queue work — each item appears instantly in the human's UI and in the 3D scene. Prefer several small, concrete items over one vague one.

    View tool JSON
    {
      "name": "add_board_item",
      "kind": "act",
      "impl": "imperative",
      "description": "Add an item to the shared workspace board the human is looking at. Use this to lay out a plan, capture decisions, or queue work — each item appears instantly in the human's UI and in the 3D scene. Prefer several small, concrete items over one vague one.",
      "inputSchema": {
        "type": "object",
        "properties": {
          "title": {
            "type": "string",
            "description": "Short, concrete item title (max 140 chars)."
          },
          "note": {
            "type": "string",
            "description": "Optional context or detail for the item."
          },
          "status": {
            "type": "string",
            "enum": [
              "todo",
              "doing",
              "done"
            ],
            "description": "Initial status. Defaults to todo."
          }
        },
        "required": [
          "title"
        ]
      }
    }
    update_board_itemAction

    Update a board item: change its status (todo → doing → done), retitle it, or attach a note. Use the id from list_board (e.g. b2). Moving items is how you and the human keep a shared picture of progress.

    View tool JSON
    {
      "name": "update_board_item",
      "kind": "act",
      "impl": "imperative",
      "description": "Update a board item: change its status (todo → doing → done), retitle it, or attach a note. Use the id from list_board (e.g. b2). Moving items is how you and the human keep a shared picture of progress.",
      "inputSchema": {
        "type": "object",
        "properties": {
          "id": {
            "type": "string",
            "description": "Item id, e.g. \"b2\"."
          },
          "status": {
            "type": "string",
            "enum": [
              "todo",
              "doing",
              "done"
            ],
            "description": "New status."
          },
          "title": {
            "type": "string",
            "description": "New title (optional)."
          },
          "note": {
            "type": "string",
            "description": "New note (optional, replaces the old one)."
          }
        },
        "required": [
          "id"
        ]
      }
    }
    remove_board_itemAction

    Remove an item from the shared board by id. Only remove items that are obsolete or were added by mistake — completed work should be marked done, not removed, so the human keeps the picture of what happened.

    View tool JSON
    {
      "name": "remove_board_item",
      "kind": "act",
      "impl": "imperative",
      "description": "Remove an item from the shared board by id. Only remove items that are obsolete or were added by mistake — completed work should be marked done, not removed, so the human keeps the picture of what happened.",
      "inputSchema": {
        "type": "object",
        "properties": {
          "id": {
            "type": "string",
            "description": "Item id, e.g. \"b3\"."
          }
        },
        "required": [
          "id"
        ]
      }
    }
    delegate_board_itemAction

    Send one board item to Leia's team to actually get done: the item moves to "pending", a human approves it, then Leia routes it to the right specialist, and when they finish the item flips to "done" with the outcome attached as its note. The human watches all of it happen live. This is the bridge between the shared plan (board) and the team doing the work. Note: this costs real money, so it does NOT run immediately — it waits for the human's approval first. You'll get back a "pending" response; check list_board later to see if it was approved and completed.

    View tool JSON
    {
      "name": "delegate_board_item",
      "kind": "act",
      "impl": "imperative",
      "description": "Send one board item to Leia's team to actually get done: the item moves to \"pending\", a human approves it, then Leia routes it to the right specialist, and when they finish the item flips to \"done\" with the outcome attached as its note. The human watches all of it happen live. This is the bridge between the shared plan (board) and the team doing the work. Note: this costs real money, so it does NOT run immediately — it waits for the human's approval first. You'll get back a \"pending\" response; check list_board later to see if it was approved and completed.",
      "inputSchema": {
        "type": "object",
        "properties": {
          "id": {
            "type": "string",
            "description": "Board item id to execute, e.g. \"b1\"."
          }
        },
        "required": [
          "id"
        ]
      }
    }