@projectsolo/solo-mission-mcp 0.21.9 → 0.21.10

package/dist/index.js

@@ -19,25 +19,25 @@ import {
 var RESPONSE_SCHEMA_PROPERTY = {
   type: "array",
   maxItems: 20,
-  description: "Structured completion questions a human answers to complete the mission. 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 {rating (stars), comment (long, optional)} schema when this is omitted at creation; every other type has no default (stays fully manual/chat-based unless you set this).",
+  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." },
+      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=5-point agreement scale, stars=1-5 rating, 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."
+        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)." },
+      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 for single/multi/dropdown/likert (max 20 options, 50 chars each). Not accepted by other kinds."
+        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 meaningful for the 'long' kind." }
+      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"]
   }
@@ -90,7 +90,7 @@ var missionTools = [
   },
   {
     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). Replaces the entire schema, not a merge.",
+    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: {
@@ -1155,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.9",
+  "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/tools/missions.ts

@@ -11,33 +11,42 @@ const RESPONSE_SCHEMA_PROPERTY = {
   type: 'array' as const,
   maxItems: 20,
   description:
-    'Structured completion questions a human answers to complete the mission. 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 ' +
-    '{rating (stars), comment (long, optional)} schema when this is omitted at creation; every ' +
-    'other type has no default (stays fully manual/chat-based unless you set this).',
+    '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.' },
+      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=5-point agreement scale, stars=1-5 rating, ' +
-          '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.',
+          '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).' },
+      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 for single/multi/dropdown/likert (max 20 options, 50 chars each). Not accepted by other kinds.',
+        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 meaningful for the 'long' kind." },
+      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'],
   },
@@ -94,7 +103,10 @@ export const missionTools: Tool[] = [
     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). Replaces the entire schema, not a merge.',
+      '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: {

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