@avallon-labs/mcp 56.0.0 → 57.0.0-staging.1288

package/dist/index.js

@@ -46,5 +46,5 @@ function setupFetch() {
 
 // src/index.ts
 setupFetch();
-await import("./server-BWBH4XI6.js");
+await import("./server-4SR55G26.js");
 //# sourceMappingURL=index.js.map

package/dist/{server-BWBH4XI6.js → server-4SR55G26.js}

@@ -12058,11 +12058,14 @@ var createScheduleBodyRuleTwoPatternsItemWeekdaysDefault = null;
 var createScheduleBodyRuleTwoPatternsMax = 10;
 var createScheduleBodyNameMax = 200;
 var CreateScheduleBody = zod.object({
-  "action": zod.object({
+  "action": zod.union([zod.object({
     "type": zod.literal("trigger_worker"),
     "worker_id": zod.string().uuid(),
     "scope": zod.union([zod.record(zod.string(), zod.union([zod.string(), zod.number(), zod.boolean(), zod.null()])), zod.null()]).optional().describe("Scope of the runs this schedule creates. Omit or send null to run without artifacts.")
-  }).describe("What the schedule does every time it fires"),
+  }), zod.object({
+    "type": zod.literal("execute_tool"),
+    "tool_id": zod.string().uuid()
+  })]).describe("What the schedule does every time it fires"),
   "rule": zod.union([zod.object({
     "type": zod.literal("once"),
     "at": zod.string().datetime({ "offset": true }).describe('The moment it fires, in UTC, e.g. "2026-09-01T14:00:00Z"')
@@ -12075,7 +12078,7 @@ var CreateScheduleBody = zod.object({
       "weekdays": zod.union([zod.array(zod.number().int().min(1).max(createScheduleBodyRuleTwoPatternsItemWeekdaysOneItemMax).describe("ISO-8601 weekday, 1 = Monday through 7 = Sunday")).min(1).max(createScheduleBodyRuleTwoPatternsItemWeekdaysOneMax), zod.null()]).default(createScheduleBodyRuleTwoPatternsItemWeekdaysDefault).describe("Local ISO-8601 weekdays the pattern may fire on. Omit or send null to fire every day.")
     }).describe("One set of local times a schedule fires at")).min(1).max(createScheduleBodyRuleTwoPatternsMax).describe("The schedule fires whenever any of these patterns comes round, all read in the rule's time zone.")
   })]).describe("When the schedule fires"),
-  "environments": zod.array(zod.enum(["live", "test"])).optional().describe("Environments the schedule fires in. `live` resolves the worker at its live version, `test` at its test version. Listing both fires every occurrence twice, once per version."),
+  "environments": zod.array(zod.enum(["live", "test"])).optional().describe("Environments the schedule fires in. `live` resolves the worker or tool at its live version, `test` at its test version. Listing both fires every occurrence twice, once per version."),
   "name": zod.string().min(1).max(createScheduleBodyNameMax).optional().describe('Human-readable name, e.g. "Nightly claim sweep"'),
   "enabled": zod.boolean().optional().describe("Whether the schedule starts firing right away. Defaults to true. Must be omitted or true for `once` rules.")
 });
@@ -12093,11 +12096,14 @@ var CreateScheduleResponse = zod.object({
   "data": zod.object({
     "id": zod.string().describe("Unique identifier for the schedule"),
     "name": zod.union([zod.string(), zod.null()]).describe("Optional human-readable name"),
-    "action": zod.object({
+    "action": zod.union([zod.object({
       "type": zod.literal("trigger_worker"),
       "worker_id": zod.string().uuid(),
       "scope": zod.union([zod.record(zod.string(), zod.union([zod.string(), zod.number(), zod.boolean(), zod.null()])), zod.null()]).optional().describe("Scope of the runs this schedule creates. Omit or send null to run without artifacts.")
-    }).describe("What the schedule does every time it fires"),
+    }), zod.object({
+      "type": zod.literal("execute_tool"),
+      "tool_id": zod.string().uuid()
+    })]).describe("What the schedule does every time it fires"),
     "rule": zod.union([zod.object({
       "type": zod.literal("once"),
       "at": zod.string().datetime({ "offset": true }).describe('The moment it fires, in UTC, e.g. "2026-09-01T14:00:00Z"')
@@ -12149,11 +12155,14 @@ var ListSchedulesResponse = zod.object({
   "data": zod.array(zod.object({
     "id": zod.string().describe("Unique identifier for the schedule"),
     "name": zod.union([zod.string(), zod.null()]).describe("Optional human-readable name"),
-    "action": zod.object({
+    "action": zod.union([zod.object({
       "type": zod.literal("trigger_worker"),
       "worker_id": zod.string().uuid(),
       "scope": zod.union([zod.record(zod.string(), zod.union([zod.string(), zod.number(), zod.boolean(), zod.null()])), zod.null()]).optional().describe("Scope of the runs this schedule creates. Omit or send null to run without artifacts.")
-    }).describe("What the schedule does every time it fires"),
+    }), zod.object({
+      "type": zod.literal("execute_tool"),
+      "tool_id": zod.string().uuid()
+    })]).describe("What the schedule does every time it fires"),
     "rule": zod.union([zod.object({
       "type": zod.literal("once"),
       "at": zod.string().datetime({ "offset": true }).describe('The moment it fires, in UTC, e.g. "2026-09-01T14:00:00Z"')
@@ -12195,11 +12204,14 @@ var GetScheduleResponse = zod.object({
   "data": zod.object({
     "id": zod.string().describe("Unique identifier for the schedule"),
     "name": zod.union([zod.string(), zod.null()]).describe("Optional human-readable name"),
-    "action": zod.object({
+    "action": zod.union([zod.object({
       "type": zod.literal("trigger_worker"),
       "worker_id": zod.string().uuid(),
       "scope": zod.union([zod.record(zod.string(), zod.union([zod.string(), zod.number(), zod.boolean(), zod.null()])), zod.null()]).optional().describe("Scope of the runs this schedule creates. Omit or send null to run without artifacts.")
-    }).describe("What the schedule does every time it fires"),
+    }), zod.object({
+      "type": zod.literal("execute_tool"),
+      "tool_id": zod.string().uuid()
+    })]).describe("What the schedule does every time it fires"),
     "rule": zod.union([zod.object({
       "type": zod.literal("once"),
       "at": zod.string().datetime({ "offset": true }).describe('The moment it fires, in UTC, e.g. "2026-09-01T14:00:00Z"')
@@ -12248,7 +12260,7 @@ var UpdateScheduleBody = zod.object({
       "weekdays": zod.union([zod.array(zod.number().int().min(1).max(updateScheduleBodyRuleTwoPatternsItemWeekdaysOneItemMax).describe("ISO-8601 weekday, 1 = Monday through 7 = Sunday")).min(1).max(updateScheduleBodyRuleTwoPatternsItemWeekdaysOneMax), zod.null()]).default(updateScheduleBodyRuleTwoPatternsItemWeekdaysDefault).describe("Local ISO-8601 weekdays the pattern may fire on. Omit or send null to fire every day.")
     }).describe("One set of local times a schedule fires at")).min(1).max(updateScheduleBodyRuleTwoPatternsMax).describe("The schedule fires whenever any of these patterns comes round, all read in the rule's time zone.")
   })]).optional().describe("When the schedule fires"),
-  "environments": zod.array(zod.enum(["live", "test"])).optional().describe("Environments the schedule fires in. `live` resolves the worker at its live version, `test` at its test version. Listing both fires every occurrence twice, once per version."),
+  "environments": zod.array(zod.enum(["live", "test"])).optional().describe("Environments the schedule fires in. `live` resolves the worker or tool at its live version, `test` at its test version. Listing both fires every occurrence twice, once per version."),
   "name": zod.union([zod.string().min(1).max(updateScheduleBodyNameOneMax), zod.null()]).optional().describe("Human-readable name. Send null to clear it."),
   "enabled": zod.boolean().optional().describe("Whether the schedule fires. Disabled never fires. Must be omitted or true for `once` rules.")
 });
@@ -12266,11 +12278,14 @@ var UpdateScheduleResponse = zod.object({
   "data": zod.object({
     "id": zod.string().describe("Unique identifier for the schedule"),
     "name": zod.union([zod.string(), zod.null()]).describe("Optional human-readable name"),
-    "action": zod.object({
+    "action": zod.union([zod.object({
       "type": zod.literal("trigger_worker"),
       "worker_id": zod.string().uuid(),
       "scope": zod.union([zod.record(zod.string(), zod.union([zod.string(), zod.number(), zod.boolean(), zod.null()])), zod.null()]).optional().describe("Scope of the runs this schedule creates. Omit or send null to run without artifacts.")
-    }).describe("What the schedule does every time it fires"),
+    }), zod.object({
+      "type": zod.literal("execute_tool"),
+      "tool_id": zod.string().uuid()
+    })]).describe("What the schedule does every time it fires"),
     "rule": zod.union([zod.object({
       "type": zod.literal("once"),
       "at": zod.string().datetime({ "offset": true }).describe('The moment it fires, in UTC, e.g. "2026-09-01T14:00:00Z"')
@@ -12323,7 +12338,7 @@ var ListDispatchesResponse = zod.object({
       "id": zod.string()
     }),
     "target": zod.union([zod.object({
-      "type": zod.enum(["worker_run", "extractor_job"]),
+      "type": zod.enum(["worker_run", "extractor_job", "tool_call"]),
       "id": zod.string()
     }), zod.null()]),
     "due_at": zod.string().datetime({ "offset": true }),
@@ -16029,7 +16044,7 @@ var createMcpServer = (options) => {
     "createSchedule",
     {
       title: "Create a schedule",
-      description: "Create a schedule that performs an action, either repeatedly or once.\n\n`action` describes **what** happens \u2014 today only `trigger_worker`, which starts a worker run with the given scope. `rule` describes **when**: `recurring` carries one or more `patterns`, and fires whenever any of them comes round. A pattern fires every hour at `minute`, narrowed by `hours` and `weekdays` \u2014 so `hours: [9]` is daily at 09:00, `hours: [12], weekdays: [1]` is Mondays at noon, and `hours: [9, 13, 17], weekdays: [1, 2, 3, 4, 5]` is three times a day on weekdays. Give a second pattern to mix cadences: hourly on weekdays plus 09:00, 11:00 and 18:00 at weekends is two patterns on one schedule. Patterns overlap harmlessly \u2014 two that land on the same minute fire once. Every set is read in the schedule's own time zone \u2014 an IANA identifier such as `America/Chicago`, resolved across DST transitions. `once` fires a single time at a UTC instant.\n\n`environments` says **which worker version** each occurrence runs: `live` resolves the worker at its live version, `test` at its test version. Give both to soak a candidate version on the same cadence and scope as production \u2014 every occurrence then fires twice, producing one run per environment. Omit it to fire in `live` only.\n\nThe response's `next_run_at` is the first occurrence strictly after the moment of creation; a rule that resolves to no such occurrence is rejected. Create with `enabled: false` to stage a recurring schedule without letting it fire. A one-off is always enabled: delete it to cancel it, and its `next_run_at` becomes null once it has fired.\n\nRequires the `schedules:write` permission.",
+      description: "Create a schedule that performs an action, either repeatedly or once.\n\n`action` describes **what** happens: `trigger_worker` starts a worker run with the given scope, and `execute_tool` executes a tool without parameters. `rule` describes **when**: `recurring` carries one or more `patterns`, and fires whenever any of them comes round. A pattern fires every hour at `minute`, narrowed by `hours` and `weekdays` \u2014 so `hours: [9]` is daily at 09:00, `hours: [12], weekdays: [1]` is Mondays at noon, and `hours: [9, 13, 17], weekdays: [1, 2, 3, 4, 5]` is three times a day on weekdays. Give a second pattern to mix cadences: hourly on weekdays plus 09:00, 11:00 and 18:00 at weekends is two patterns on one schedule. Patterns overlap harmlessly \u2014 two that land on the same minute fire once. Every set is read in the schedule's own time zone \u2014 an IANA identifier such as `America/Chicago`, resolved across DST transitions. `once` fires a single time at a UTC instant.\n\n`environments` says **which version** of the worker or tool each occurrence runs: `live` resolves it at its live version, `test` at its test version. Give both to soak a candidate version on the same cadence as production \u2014 every occurrence then fires twice, once per environment. Omit it to fire in `live` only.\n\nThe response's `next_run_at` is the first occurrence strictly after the moment of creation; a rule that resolves to no such occurrence is rejected. Create with `enabled: false` to stage a recurring schedule without letting it fire. A one-off is always enabled: delete it to cancel it, and its `next_run_at` becomes null once it has fired.\n\nRequires the `schedules:write` permission, and `tools:execute` for an `execute_tool` action.",
       inputSchema: {
         bodyParams: CreateScheduleBody.optional()
       },
@@ -16110,7 +16125,7 @@ var createMcpServer = (options) => {
     "listDispatches",
     {
       title: "List dispatches",
-      description: "List the organization's dispatches, newest occurrence first.\n\nA dispatch is one occurrence of a trigger in one environment, carried out on its own: a schedule produces one per environment it runs in every time it fires, an inbound email produces one for the environment its inbox received it in, a resolved information request produces one that restarts the worker that asked, an ended call produces one that runs its voice agent's post-call processor once its transcript is ready, and creating a worker run through the API produces a `manual` one, carried out before the request returns. Listing them shows what a trigger has actually done, including occurrences that never produced anything.\n\n- `pending` \u2014 not carried out yet: waiting to be picked up, in flight, or waiting on a retry after an earlier pickup did not complete.\n- `dispatched` \u2014 carried out.\n- `abandoned` \u2014 gave up, because the occurrence passed its `expires_at` deadline before it could be carried out, or, for a `manual` dispatch, because the request that created it failed.\n\n`attempts` counts how many times the occurrence has been picked up, not how many times it failed: a dispatch carried out on the first pickup ends at `attempts: 1`, and a higher count means earlier pickups did not complete.\n\n`target` is what the occurrence produced \u2014 a worker run, or an extractor job for an email whose inbox extracts or a call whose voice agent extracts. It is null until the dispatch is carried out.\n\nNarrow to one trigger with `trigger_type` and `trigger_id` \u2014 the schedule's ID for a schedule, the email's ID for an email, the request's ID for an information request, the call's ID for a call. `trigger_id` requires `trigger_type`.",
+      description: "List the organization's dispatches, newest occurrence first.\n\nA dispatch is one occurrence of a trigger in one environment, carried out on its own: a schedule produces one per environment it runs in every time it fires, an inbound email produces one for the environment its inbox received it in, a resolved information request produces one that restarts the worker that asked, an ended call produces one that runs its voice agent's post-call processor once its transcript is ready, and creating a worker run through the API produces a `manual` one, carried out before the request returns. Listing them shows what a trigger has actually done, including occurrences that never produced anything.\n\n- `pending` \u2014 not carried out yet: waiting to be picked up, in flight, or waiting on a retry after an earlier pickup did not complete.\n- `dispatched` \u2014 carried out.\n- `abandoned` \u2014 gave up, because the occurrence passed its `expires_at` deadline before it could be carried out, or, for a `manual` dispatch, because the request that created it failed.\n\n`attempts` counts how many times the occurrence has been picked up, not how many times it failed: a dispatch carried out on the first pickup ends at `attempts: 1`, and a higher count means earlier pickups did not complete.\n\n`target` is what the occurrence produced: a worker run, an extractor job (for an email whose inbox extracts or a call whose voice agent extracts), or a tool call (for an `execute_tool` schedule). It is null until the dispatch is carried out, and for a tool call until the tool has run.\n\nNarrow to one trigger with `trigger_type` and `trigger_id` \u2014 the schedule's ID for a schedule, the email's ID for an email, the request's ID for an information request, the call's ID for a call. `trigger_id` requires `trigger_type`.",
       inputSchema: {
         queryParams: ListDispatchesQueryParams
       },
@@ -16819,4 +16834,4 @@ var transport = new StdioServerTransport();
 server.connect(transport).then(() => {
   console.error("MCP server running on stdio");
 }).catch(console.error);
-//# sourceMappingURL=server-BWBH4XI6.js.map
+//# sourceMappingURL=server-4SR55G26.js.map