@projectsolo/solo-mission-mcp 0.21.8 → 0.21.10

package/dist/{chunk-NXOOPOSF.js → chunk-TKRT2V2W.js}

@@ -51,6 +51,16 @@ async function apiPost(path, body) {
   if (!response.ok) return parseErrorResponse(response);
   return response.json();
 }
+async function apiPatch(path, body) {
+  const response = await fetch(`${config.apiUrl}${path}`, {
+    method: "PATCH",
+    headers: DEFAULT_HEADERS,
+    body: body !== void 0 ? JSON.stringify(body) : void 0,
+    signal: AbortSignal.timeout(3e4)
+  });
+  if (!response.ok) return parseErrorResponse(response);
+  return response.json();
+}
 async function apiDelete(path) {
   const response = await fetch(`${config.apiUrl}${path}`, {
     method: "DELETE",
@@ -74,6 +84,7 @@ async function publicApiPost(path, body) {
 export {
   apiGet,
   apiPost,
+  apiPatch,
   apiDelete,
   publicApiPost
 };

package/dist/{client-2NLDPRAH.js → client-LDWK5HLP.js}

@@ -1,12 +1,14 @@
 import {
   apiDelete,
   apiGet,
+  apiPatch,
   apiPost,
   publicApiPost
-} from "./chunk-NXOOPOSF.js";
+} from "./chunk-TKRT2V2W.js";
 export {
   apiDelete,
   apiGet,
+  apiPatch,
   apiPost,
   publicApiPost
 };

package/dist/index.js

@@ -2,9 +2,10 @@
 import {
   apiDelete,
   apiGet,
+  apiPatch,
   apiPost,
   publicApiPost
-} from "./chunk-NXOOPOSF.js";
+} from "./chunk-TKRT2V2W.js";
 
 // src/index.ts
 import { Server } from "@modelcontextprotocol/sdk/server/index.js";
@@ -15,6 +16,32 @@ import {
 } from "@modelcontextprotocol/sdk/types.js";
 
 // src/tools/missions.ts
+var RESPONSE_SCHEMA_PROPERTY = {
+  type: "array",
+  maxItems: 20,
+  description: 'Structured completion questions a human answers to complete the mission. Question ids must be unique within one schema \u2014 a duplicate id is rejected at creation/update, not merged or silently overwritten. When set, finalize_qualification auto-derives qualified UIDs from completion instead of requiring an explicit qualified_human_uids list \u2014 same mechanism media_review has always used for track ratings, generalized to any mission type. media_review defaults to a canonical two-question schema when this is omitted at creation \u2014 literally { id: "rating", kind: "stars", required: true } and { id: "comment", kind: "long", required: false } \u2014 so read/append against those exact ids if you rely on the default rather than supplying your own schema. Every other type has no default (stays fully manual/chat-based unless you set this).',
+  items: {
+    type: "object",
+    properties: {
+      id: { type: "string", description: "Unique id within this schema \u2014 the key answers are stored under. Duplicates are rejected, not merged." },
+      kind: {
+        type: "string",
+        enum: ["single", "multi", "likert", "stars", "short", "long", "dropdown", "consent"],
+        description: 'single=one choice, multi=several choices, likert=a scale rendered as a row of buttons (NOT fixed at 5 points \u2014 the number of options you supply IS the number of points, so give exactly as many option labels as the scale should have; a common convention is 5 labels like "1 Strongly disagree".."5 Strongly agree" but nothing enforces that), stars=1-5 rating (fixed, no options), short=one line of text, long=paragraph text (see min_length), dropdown=one choice from a long list, consent=a checkbox that must be explicitly true \u2014 the checkbox\'s own clickable text is `label` itself (there is no separate heading rendered above it, unlike every other kind); use `help` for any additional wording you want shown near it.'
+      },
+      label: { type: "string", description: "Question text shown to the human (max 200 chars). For the consent kind this is the checkbox's own clickable text, not a separate heading." },
+      help: { type: "string", description: "Optional helper text shown under the label (max 500 chars)." },
+      required: { type: "boolean", description: "Whether this question must be answered to complete the mission." },
+      options: {
+        type: "array",
+        items: { type: "string" },
+        description: "Required (non-empty) for single/multi/dropdown/likert (max 20 options, 50 chars each). Not accepted by other kinds."
+      },
+      min_length: { type: "number", description: "Minimum answer length. Only read for the 'long' kind \u2014 silently ignored (not rejected) if set on any other kind." }
+    },
+    required: ["id", "kind", "label", "required"]
+  }
+};
 var missionTools = [
   {
     name: "create_mission",
@@ -55,11 +82,24 @@ var missionTools = [
         lottery_prize_per_winner: { type: "number", minimum: 0, description: "Additional prize in USDC paid to each lottery winner on top of base_reward. Must be paired with lottery_winner_count." },
         hiring_duration_hours: { type: "number", minimum: 0.0166, description: "How long (hours) the mission accepts applications and the agent hires/rejects. The hiring window closes at now + hiring_duration_hours. Finalize-qualification cannot be called before this. Backend floor is 60s (0.0166h), same for every chain \u2014 see work_duration_hours for the reasoning." },
         work_duration_hours: { type: "number", minimum: 0.0166, description: "How long (hours) hired participants have to complete the work. Agent must call settle_mission before this period ends. Backend floor is 60s (0.0166h) for every chain \u2014 this is a flat sanity check against a near-zero window, not a guarantee of a legal settlement window on every chain: Base's own EscrowVault contract separately enforces its own fixed 1-hour minimum regardless of what this floor allows through, so a too-short Base mission still fails downstream (at finalize_qualification, or on-chain) instead of being caught at creation." },
-        auto_accept_applicants: { type: "boolean", description: "When true, applicants are automatically hired when they apply \u2014 no manual hire_participant call needed. First-come first-served up to max_humans. Face verification is still required. Ideal for open media_review missions." }
+        auto_accept_applicants: { type: "boolean", description: "When true, applicants are automatically hired when they apply \u2014 no manual hire_participant call needed. First-come first-served up to max_humans. Face verification is still required. Ideal for open media_review missions." },
+        response_schema: RESPONSE_SCHEMA_PROPERTY
       },
       required: ["type", "title", "description"]
     }
   },
+  {
+    name: "update_mission_questions",
+    description: "Set or replace a mission's response_schema after creation. Locked once hiring starts \u2014 same window as add_mission_track (on-chain: only before funding; off-chain: only while active with zero hired participants yet). This window is what makes a schema replacement safe: a human can only submit answers once hired, and the schema can no longer change once anyone has been hired \u2014 there is no state where a human has answered under one schema and the mission later presents a different one. Replaces the entire schema, not a merge.",
+    inputSchema: {
+      type: "object",
+      properties: {
+        mission_id: { type: "string" },
+        response_schema: RESPONSE_SCHEMA_PROPERTY
+      },
+      required: ["mission_id", "response_schema"]
+    }
+  },
   {
     name: "list_missions",
     description: "List missions created by this agent. Filter by status to manage your mission portfolio.",
@@ -125,7 +165,7 @@ var missionTools = [
   },
   {
     name: "finalize_qualification",
-    description: "Lock in the qualified participants after reviewing their work. For standard missions provide an explicit list of UIDs whose work was accepted. For media_review missions pass an empty body \u2014 qualified_human_uids is ignored and the backend auto-qualifies anyone who rated every track. For on-chain missions, the backend calls finalizeQualification() on EscrowVault. Mission transitions to qualifying. If you never call this, the platform does it for you shortly after the hiring window closes, qualifying every hired participant you did not explicitly reject_participant (silence = go) \u2014 call reject_participant first for anyone whose work should NOT be paid.",
+    description: "Lock in the qualified participants after reviewing their work. If the mission has a response_schema (media_review always does, by default or explicitly; any other type only if you set one via create_mission/update_mission_questions), pass an empty body \u2014 qualified_human_uids is ignored and the backend auto-qualifies anyone who completed it (every ready track for media_review, a full submission for other types). Otherwise provide an explicit list of UIDs whose work was accepted. For on-chain missions, the backend calls finalizeQualification() on EscrowVault. Mission transitions to qualifying. If you never call this, the platform does it for you shortly after the hiring window closes, qualifying every hired participant you did not explicitly reject_participant (silence = go) \u2014 call reject_participant first for anyone whose work should NOT be paid.",
     inputSchema: {
       type: "object",
       properties: {
@@ -133,7 +173,7 @@ var missionTools = [
         qualified_human_uids: {
           type: "array",
           items: { type: "string" },
-          description: "Firebase UIDs of humans whose work was accepted. Ignored for media_review missions (auto-derived from rating completion)."
+          description: "Firebase UIDs of humans whose work was accepted. Ignored for any mission with a response_schema (auto-derived from completion instead)."
         }
       },
       required: ["mission_id"]
@@ -258,6 +298,8 @@ async function handleMissionTool(name, args) {
     }
     case "get_mission":
       return apiGet(`/agent/missions/${args.mission_id}`);
+    case "update_mission_questions":
+      return apiPatch(`/agent/missions/${args.mission_id}/questions`, { response_schema: args.response_schema });
     case "confirm_funding":
       return apiPost(`/agent/missions/${args.mission_id}/confirm-funding`, { tx_hash: args.tx_hash });
     case "hire_participant":
@@ -999,7 +1041,7 @@ function toRawAmount(amount, decimals) {
 }
 var SOLANA_TOOL_NAMES = new Set(solanaTools.map((t) => t.name));
 async function handleSolanaTool(name, args) {
-  const { apiGet: apiGet2, apiPost: apiPost2 } = await import("./client-2NLDPRAH.js");
+  const { apiGet: apiGet2, apiPost: apiPost2 } = await import("./client-LDWK5HLP.js");
   switch (name) {
     case "get_solana_config":
       return apiGet2("/agent/solana/config");
@@ -1113,7 +1155,14 @@ async function handleSolanaTool(name, args) {
       const { loadSolanaWallet, associatedTokenAddress, signTransaction } = await import("./wallet-IUQWBW6F.js");
       const wallet = await loadSolanaWallet();
       const cfg = await apiGet2("/agent/solana/config");
-      const mint = cfg.mints.TEST_USDC ?? Object.values(cfg.mints)[0];
+      const mission = await apiGet2(`/agent/missions/${args.mission_id}`);
+      const mint = mission.mission?.token_address;
+      if (!mint) {
+        return {
+          refunded: false,
+          error: `Could not resolve mission ${args.mission_id}'s token_address \u2014 call get_mission to check it exists and is funded.`
+        };
+      }
       const tokenAccount = await associatedTokenAddress(mint, wallet.publicKey);
       if (!args.action) {
         try {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@projectsolo/solo-mission-mcp",
-  "version": "0.21.8",
+  "version": "0.21.10",
   "description": "MCP server for Solo Mission Platform — lets AI agents create missions, browse humans, and chat.",
   "type": "module",
   "main": "dist/index.js",

package/src/api/client.ts

@@ -48,6 +48,17 @@ export async function apiPost<T>(path: string, body?: unknown): Promise<T> {
   return response.json() as Promise<T>;
 }
 
+export async function apiPatch<T>(path: string, body?: unknown): Promise<T> {
+  const response = await fetch(`${config.apiUrl}${path}`, {
+    method: 'PATCH',
+    headers: DEFAULT_HEADERS,
+    body: body !== undefined ? JSON.stringify(body) : undefined,
+    signal: AbortSignal.timeout(30_000),
+  });
+  if (!response.ok) return parseErrorResponse(response);
+  return response.json() as Promise<T>;
+}
+
 export async function apiDelete<T>(path: string): Promise<T> {
   const response = await fetch(`${config.apiUrl}${path}`, {
     method: 'DELETE',

package/src/tools/missions.ts

@@ -1,5 +1,56 @@
 import { Tool } from '@modelcontextprotocol/sdk/types.js';
-import { apiGet, apiPost } from '../api/client.js';
+import { apiGet, apiPatch, apiPost } from '../api/client.js';
+
+/**
+ * Shared JSON-schema for Mission.response_schema, used by both create_mission (set at creation)
+ * and update_mission_questions (set/replace afterward, pre-hiring). v1 kinds only — text/choice/
+ * rating input; kinds needing video-stimulus/gating infra (ab/slider/rank/tags/timestamps/upload)
+ * aren't supported yet.
+ */
+const RESPONSE_SCHEMA_PROPERTY = {
+  type: 'array' as const,
+  maxItems: 20,
+  description:
+    'Structured completion questions a human answers to complete the mission. Question ids must ' +
+    'be unique within one schema — a duplicate id is rejected at creation/update, not merged or ' +
+    'silently overwritten. When set, finalize_qualification auto-derives qualified UIDs from ' +
+    'completion instead of requiring an explicit qualified_human_uids list — same mechanism ' +
+    'media_review has always used for track ratings, generalized to any mission type. ' +
+    'media_review defaults to a canonical two-question schema when this is omitted at creation — ' +
+    'literally { id: "rating", kind: "stars", required: true } and { id: "comment", kind: "long", ' +
+    'required: false } — so read/append against those exact ids if you rely on the default rather ' +
+    'than supplying your own schema. Every other type has no default (stays fully manual/chat-based ' +
+    'unless you set this).',
+  items: {
+    type: 'object',
+    properties: {
+      id: { type: 'string', description: 'Unique id within this schema — the key answers are stored under. Duplicates are rejected, not merged.' },
+      kind: {
+        type: 'string',
+        enum: ['single', 'multi', 'likert', 'stars', 'short', 'long', 'dropdown', 'consent'],
+        description:
+          'single=one choice, multi=several choices, likert=a scale rendered as a row of buttons (NOT ' +
+          'fixed at 5 points — the number of options you supply IS the number of points, so give exactly ' +
+          'as many option labels as the scale should have; a common convention is 5 labels like "1 ' +
+          'Strongly disagree".."5 Strongly agree" but nothing enforces that), stars=1-5 rating (fixed, ' +
+          'no options), short=one line of text, long=paragraph text (see min_length), dropdown=one ' +
+          'choice from a long list, consent=a checkbox that must be explicitly true — the checkbox\'s ' +
+          'own clickable text is `label` itself (there is no separate heading rendered above it, unlike ' +
+          'every other kind); use `help` for any additional wording you want shown near it.',
+      },
+      label: { type: 'string', description: 'Question text shown to the human (max 200 chars). For the consent kind this is the checkbox\'s own clickable text, not a separate heading.' },
+      help: { type: 'string', description: 'Optional helper text shown under the label (max 500 chars).' },
+      required: { type: 'boolean', description: 'Whether this question must be answered to complete the mission.' },
+      options: {
+        type: 'array',
+        items: { type: 'string' },
+        description: 'Required (non-empty) for single/multi/dropdown/likert (max 20 options, 50 chars each). Not accepted by other kinds.',
+      },
+      min_length: { type: 'number', description: "Minimum answer length. Only read for the 'long' kind — silently ignored (not rejected) if set on any other kind." },
+    },
+    required: ['id', 'kind', 'label', 'required'],
+  },
+};
 
 export const missionTools: Tool[] = [
   {
@@ -42,10 +93,29 @@ export const missionTools: Tool[] = [
         hiring_duration_hours: { type: 'number', minimum: 0.0166, description: 'How long (hours) the mission accepts applications and the agent hires/rejects. The hiring window closes at now + hiring_duration_hours. Finalize-qualification cannot be called before this. Backend floor is 60s (0.0166h), same for every chain — see work_duration_hours for the reasoning.' },
         work_duration_hours: { type: 'number', minimum: 0.0166, description: 'How long (hours) hired participants have to complete the work. Agent must call settle_mission before this period ends. Backend floor is 60s (0.0166h) for every chain — this is a flat sanity check against a near-zero window, not a guarantee of a legal settlement window on every chain: Base\'s own EscrowVault contract separately enforces its own fixed 1-hour minimum regardless of what this floor allows through, so a too-short Base mission still fails downstream (at finalize_qualification, or on-chain) instead of being caught at creation.' },
         auto_accept_applicants: { type: 'boolean', description: 'When true, applicants are automatically hired when they apply — no manual hire_participant call needed. First-come first-served up to max_humans. Face verification is still required. Ideal for open media_review missions.' },
+        response_schema: RESPONSE_SCHEMA_PROPERTY,
       },
       required: ['type', 'title', 'description'],
     },
   },
+  {
+    name: 'update_mission_questions',
+    description:
+      "Set or replace a mission's response_schema after creation. Locked once hiring starts — " +
+      'same window as add_mission_track (on-chain: only before funding; off-chain: only while ' +
+      'active with zero hired participants yet). This window is what makes a schema replacement ' +
+      'safe: a human can only submit answers once hired, and the schema can no longer change once ' +
+      'anyone has been hired — there is no state where a human has answered under one schema and ' +
+      'the mission later presents a different one. Replaces the entire schema, not a merge.',
+    inputSchema: {
+      type: 'object',
+      properties: {
+        mission_id: { type: 'string' },
+        response_schema: RESPONSE_SCHEMA_PROPERTY,
+      },
+      required: ['mission_id', 'response_schema'],
+    },
+  },
   {
     name: 'list_missions',
     description: 'List missions created by this agent. Filter by status to manage your mission portfolio.',
@@ -111,7 +181,7 @@ export const missionTools: Tool[] = [
   },
   {
     name: 'finalize_qualification',
-    description: 'Lock in the qualified participants after reviewing their work. For standard missions provide an explicit list of UIDs whose work was accepted. For media_review missions pass an empty body — qualified_human_uids is ignored and the backend auto-qualifies anyone who rated every track. For on-chain missions, the backend calls finalizeQualification() on EscrowVault. Mission transitions to qualifying. If you never call this, the platform does it for you shortly after the hiring window closes, qualifying every hired participant you did not explicitly reject_participant (silence = go) — call reject_participant first for anyone whose work should NOT be paid.',
+    description: 'Lock in the qualified participants after reviewing their work. If the mission has a response_schema (media_review always does, by default or explicitly; any other type only if you set one via create_mission/update_mission_questions), pass an empty body — qualified_human_uids is ignored and the backend auto-qualifies anyone who completed it (every ready track for media_review, a full submission for other types). Otherwise provide an explicit list of UIDs whose work was accepted. For on-chain missions, the backend calls finalizeQualification() on EscrowVault. Mission transitions to qualifying. If you never call this, the platform does it for you shortly after the hiring window closes, qualifying every hired participant you did not explicitly reject_participant (silence = go) — call reject_participant first for anyone whose work should NOT be paid.',
     inputSchema: {
       type: 'object',
       properties: {
@@ -119,7 +189,7 @@ export const missionTools: Tool[] = [
         qualified_human_uids: {
           type: 'array',
           items: { type: 'string' },
-          description: 'Firebase UIDs of humans whose work was accepted. Ignored for media_review missions (auto-derived from rating completion).',
+          description: 'Firebase UIDs of humans whose work was accepted. Ignored for any mission with a response_schema (auto-derived from completion instead).',
         },
       },
       required: ['mission_id'],
@@ -248,6 +318,9 @@ export async function handleMissionTool(name: string, args: Record<string, any>)
     case 'get_mission':
       return apiGet(`/agent/missions/${args.mission_id}`);
 
+    case 'update_mission_questions':
+      return apiPatch(`/agent/missions/${args.mission_id}/questions`, { response_schema: args.response_schema });
+
     case 'confirm_funding':
       return apiPost(`/agent/missions/${args.mission_id}/confirm-funding`, { tx_hash: args.tx_hash });
 

package/src/tools/solana.ts

@@ -282,7 +282,22 @@ export async function handleSolanaTool(
         program_id: string;
         mints: Record<string, string>;
       };
-      const mint = cfg.mints.TEST_USDC ?? Object.values(cfg.mints)[0];
+      // The mission's ACTUAL mint, not a guessed default — get_solana_config's mints always
+      // includes both the production payout mint (USDC) and TEST_USDC, and a mission is funded
+      // in exactly one of them. Guessing (the previous code preferred TEST_USDC whenever present)
+      // computes the wrong associated-token-account for any mission funded in the other one, and
+      // the refund/cancel/emergency-refund transaction then fails on-chain with
+      // AccountNotInitialized — confirmed live against a real USDC-funded mission.
+      const mission = (await apiGet(`/agent/missions/${args.mission_id}`)) as {
+        mission?: { token_address?: string };
+      };
+      const mint = mission.mission?.token_address;
+      if (!mint) {
+        return {
+          refunded: false,
+          error: `Could not resolve mission ${args.mission_id}'s token_address — call get_mission to check it exists and is funded.`,
+        };
+      }
       const tokenAccount = await associatedTokenAddress(mint, wallet.publicKey);
 
       // No action: ask what is legal rather than guessing and getting a 409. Uses a deliberately