@avallon-labs/mcp 52.0.0 → 52.1.0

package/dist/index.js

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

package/dist/{server-N7T5ZAC6.js → server-CABXCD7A.js}

@@ -11287,7 +11287,7 @@ var listDispatchesQueryOffsetMin = 0;
 var listDispatchesQuerySortByDefault = `due_at`;
 var listDispatchesQuerySortOrderDefault = `desc`;
 var ListDispatchesQueryParams = zod.object({
-  "trigger_type": zod.enum(["schedule", "email", "information_request"]).optional().describe("Only dispatches produced by this kind of trigger"),
+  "trigger_type": zod.enum(["schedule", "email", "information_request", "manual"]).optional().describe("Only dispatches produced by this kind of trigger"),
   "trigger_id": zod.string().uuid().optional().describe("Only dispatches produced by this trigger. Requires `trigger_type`."),
   "count": zod.number().min(1).max(listDispatchesQueryCountMax).default(listDispatchesQueryCountDefault),
   "offset": zod.number().min(listDispatchesQueryOffsetMin).default(listDispatchesQueryOffsetDefault),
@@ -11300,7 +11300,7 @@ var ListDispatchesResponse = zod.object({
   "data": zod.array(zod.object({
     "id": zod.string(),
     "trigger": zod.object({
-      "type": zod.enum(["schedule", "email", "information_request"]),
+      "type": zod.enum(["schedule", "email", "information_request", "manual"]),
       "id": zod.string()
     }),
     "target": zod.union([zod.object({
@@ -14444,7 +14444,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, and a resolved information request produces one that restarts the worker that asked. 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.\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. It is null until the dispatch is carried out, and stays null on one that was abandoned.\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. `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, 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. 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. `trigger_id` requires `trigger_type`.",
       inputSchema: {
         queryParams: ListDispatchesQueryParams
       },
@@ -15022,4 +15022,4 @@ var transport = new StdioServerTransport();
 server.connect(transport).then(() => {
   console.error("MCP server running on stdio");
 }).catch(console.error);
-//# sourceMappingURL=server-N7T5ZAC6.js.map
+//# sourceMappingURL=server-CABXCD7A.js.map