@projectsolo/solo-mission-mcp 0.21.3 → 0.21.6

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/dist/index.js CHANGED
@@ -78,7 +78,7 @@ var missionTools = [
78
78
  },
79
79
  {
80
80
  name: "get_mission",
81
- description: 'Get details of a specific mission by ID, including all participants. Each participant includes a conversation_id once the human has tapped "Say Hi" \u2014 use it directly with watch_conversation or send_message. Each participant also includes an agent_rating field ({ rating: 1\u20135, comment?: string, updated_at }) if that human has rated the agent; null if not rated or if the 7-day rating window after mission completion has closed.',
81
+ description: `Get details of a specific mission by ID, including all participants. Each participant includes a conversation_id once the human has tapped "Say Hi" \u2014 use it directly with watch_conversation or send_message. Each participant also includes an agent_rating field ({ rating: 1\u20135, comment?: string, updated_at }) if that human has rated the agent; null if not rated or if the 7-day rating window after mission completion has closed. Once settled, a settlement_outcome field ('completed' / 'completed_refundable' / 'no_payout_refunded') tells you whether anyone was actually paid \u2014 see settle_mission's description; don't infer that from status alone.`,
82
82
  inputSchema: {
83
83
  type: "object",
84
84
  properties: {
@@ -141,7 +141,7 @@ var missionTools = [
141
141
  },
142
142
  {
143
143
  name: "settle_mission",
144
- description: "Settle the mission after finalize_qualification. For on-chain missions, calls settleTask() on EscrowVault only (aggregate payout numbers, no per-wallet computation); mission transitions to completed or refundable. Rewards are NOT immediately claimable \u2014 a separate batched process publishes the Merkle root that makes them claimable, which can take anywhere from minutes to over an hour depending on the review window. For free (off-chain) missions, marks qualified participants as completed \u2014 no payment is involved.",
144
+ description: "Settle the mission after finalize_qualification. For on-chain missions, calls settleTask() on EscrowVault only (aggregate payout numbers, no per-wallet computation); mission transitions to completed or refundable. IMPORTANT: status alone cannot tell you whether anyone was paid \u2014 a mission with 8/10 slots filled (2 slots' budget refunded) and one with 0/10 filled (the whole budget refunded) both land on 'refundable'/'refunded'. Check the settlement_outcome field on the response instead: 'completed' (fully spent, no refund), 'completed_refundable' (real participants were paid, only the unfilled slots refund), or 'no_payout_refunded' (nobody qualified, the entire budget bounces). Rewards are NOT immediately claimable \u2014 a separate batched process publishes the Merkle root that makes them claimable, gated by a review window currently defaulting to about 10 seconds (minimized pre-launch; will lengthen to an hour or more once real funds are at stake). Check GET /human/rewards for actual claimable status rather than assuming a fixed delay. For free (off-chain) missions, marks qualified participants as completed \u2014 no payment is involved; settlement_outcome is always 'completed' there.",
145
145
  inputSchema: {
146
146
  type: "object",
147
147
  properties: {
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@projectsolo/solo-mission-mcp",
3
- "version": "0.21.3",
3
+ "version": "0.21.6",
4
4
  "description": "MCP server for Solo Mission Platform — lets AI agents create missions, browse humans, and chat.",
5
5
  "type": "module",
6
6
  "main": "dist/index.js",
@@ -64,7 +64,7 @@ export const missionTools: Tool[] = [
64
64
  },
65
65
  {
66
66
  name: 'get_mission',
67
- description: 'Get details of a specific mission by ID, including all participants. Each participant includes a conversation_id once the human has tapped "Say Hi" — use it directly with watch_conversation or send_message. Each participant also includes an agent_rating field ({ rating: 1–5, comment?: string, updated_at }) if that human has rated the agent; null if not rated or if the 7-day rating window after mission completion has closed.',
67
+ description: 'Get details of a specific mission by ID, including all participants. Each participant includes a conversation_id once the human has tapped "Say Hi" — use it directly with watch_conversation or send_message. Each participant also includes an agent_rating field ({ rating: 1–5, comment?: string, updated_at }) if that human has rated the agent; null if not rated or if the 7-day rating window after mission completion has closed. Once settled, a settlement_outcome field (\'completed\' / \'completed_refundable\' / \'no_payout_refunded\') tells you whether anyone was actually paid — see settle_mission\'s description; don\'t infer that from status alone.',
68
68
  inputSchema: {
69
69
  type: 'object',
70
70
  properties: {
@@ -127,7 +127,7 @@ export const missionTools: Tool[] = [
127
127
  },
128
128
  {
129
129
  name: 'settle_mission',
130
- description: 'Settle the mission after finalize_qualification. For on-chain missions, calls settleTask() on EscrowVault only (aggregate payout numbers, no per-wallet computation); mission transitions to completed or refundable. Rewards are NOT immediately claimable — a separate batched process publishes the Merkle root that makes them claimable, which can take anywhere from minutes to over an hour depending on the review window. For free (off-chain) missions, marks qualified participants as completed — no payment is involved.',
130
+ description: 'Settle the mission after finalize_qualification. For on-chain missions, calls settleTask() on EscrowVault only (aggregate payout numbers, no per-wallet computation); mission transitions to completed or refundable. IMPORTANT: status alone cannot tell you whether anyone was paid — a mission with 8/10 slots filled (2 slots\' budget refunded) and one with 0/10 filled (the whole budget refunded) both land on \'refundable\'/\'refunded\'. Check the settlement_outcome field on the response instead: \'completed\' (fully spent, no refund), \'completed_refundable\' (real participants were paid, only the unfilled slots refund), or \'no_payout_refunded\' (nobody qualified, the entire budget bounces). Rewards are NOT immediately claimable — a separate batched process publishes the Merkle root that makes them claimable, gated by a review window currently defaulting to about 10 seconds (minimized pre-launch; will lengthen to an hour or more once real funds are at stake). Check GET /human/rewards for actual claimable status rather than assuming a fixed delay. For free (off-chain) missions, marks qualified participants as completed — no payment is involved; settlement_outcome is always \'completed\' there.',
131
131
  inputSchema: {
132
132
  type: 'object',
133
133
  properties: {