@vruum/mcp 0.10.1 → 0.11.0

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.
Files changed (3) hide show
  1. package/README.md +9 -2
  2. package/package.json +1 -1
  3. package/tools.json +1 -1
package/README.md CHANGED
@@ -135,12 +135,19 @@ Keep the same request UUID and all four inputs after an uncertain acknowledgemen
135
135
  The saved task owns model and delivery recovery; an unknown outcome does not
136
136
  authorize a replacement task or a second send.
137
137
 
138
- Use `manage_assistant action=follow_up` to continue completed private analysis.
138
+ Use `manage_assistant action=follow_up` to continue completed private analysis
139
+ or eligible private email work. A pending unapproved email revision retires the
140
+ old draft atomically. Completed email work prepares a new email, not a mail-thread
141
+ reply. The server retains the original contact and mailbox; a new draft requires
142
+ its own approval. Approved or uncertain delivery keeps its original recovery.
139
143
  Retain the same request UUID, parent Action, displayed revision, and message on
140
144
  an uncertain retry. The server creates one new Action and reconstructs permitted
141
145
  history with fresh company context. Read earlier turns through the
142
146
  `previous_action_id` returned by `fetch assistant_task`; each turn retains its
143
- own complete content references. Opening or reading work never starts analysis.
147
+ own complete content references. Earlier email drafts keep their canonical review
148
+ links. The server retains permitted draft/research context and reconstructs it
149
+ when one model request cannot hold it. Exact current delivery state stays outside
150
+ working notes. Opening or reading work never starts a model purchase.
144
151
 
145
152
  ## Configuration
146
153
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@vruum/mcp",
3
- "version": "0.10.1",
3
+ "version": "0.11.0",
4
4
  "mcpName": "ai.vruum/mcp",
5
5
  "description": "Stdio MCP bridge for the hosted Vruum revenue-platform MCP (https://api.vruum.ai/mcp): serves the advertised tool surface for credential-free introspection and proxies tool calls with your Vruum token.",
6
6
  "license": "MIT",
package/tools.json CHANGED
@@ -1140,7 +1140,7 @@
1140
1140
  "readOnlyHint": false,
1141
1141
  "title": "Manage Saved Assistant Tasks"
1142
1142
  },
1143
- "description": "Manage Assistant\n\nStart private saved analysis or one reviewed email, or cancel saved work.\n\n- start_analysis: no id; payload={request_id (UUID), message}. Call only\n after the user requests this analysis. This call explicitly grants\n revenue_operator.read_analysis.v1: paid model work using permitted reads,\n without tool writes or external effects. Keep the exact request UUID and\n message on retries; the saved task journal owns request identity and\n recovery. An uncertain response never authorizes a replacement task.\n- start_email: no id; payload={request_id (UUID), message, person_id,\n sender_config_id}. Call only after the user requests this email work.\n Authorizes paid model work, permitted reads and one retained email draft\n for that workspace contact and an eligible mailbox available to the\n current actor. It does not approve or send. Read the returned email_scope\n and linked review_message_id. Review the exact sender, recipient, subject\n and complete body through the existing message review before approving.\n Keep the same request UUID, message, person and mailbox on retries;\n uncertain acknowledgement never authorizes another task or delivery.\n- cancel: id=the saved task's Action UUID; payload={expected_version} from\n a fresh fetch assistant_task. The original current actor or a current\n workspace owner/operator may cancel future continuation. An in-flight\n effect or provider call may still finish; cancellation cannot recall it.\n- follow_up: id=the completed analysis Action UUID; payload={request_id,\n expected_version, message}. Only its current original actor/login can\n continue the latest turn. This explicitly buys a new analysis Action in\n the same private conversation. Keep the exact UUID, parent, revision and\n message on retries, including an uncertain acknowledgement. The server\n reconstructs permitted history and refreshes company context. Historical\n answers are not current facts or approval for effects.\n\nAll actions are scalar: no id arrays or items. No caller history, imported\nthread, email-scope edits, additional effects, actor transfer, or worker\ncontrol fields are accepted. This facade adds no authority to its target.\nThe task is private to its original current actor and login; owner/operator\noversight gives metadata and cancellation, never another member's content.\nExisting retained email work uses its exact linked review without changing\nthe sender. Inspect fetch assistant_task, page fetch assistant_task_events,\nand retrieve full content with fetch assistant_task_content. Read prior\nturns by following previous_action_id from fetch assistant_task until it is\nnull, then order by conversation_turn. Follow next_action_id to newer work. There is no steering of active work or shared conversation. Public chat\ncompletion limits remain active.\n\n### Responses:\n\n**200**: Successful Response (Success Response)\nContent-Type: application/json\n\nPrivate saved email support (assistant_saved_email):\nProduct support is not permission. Inspect current work and follow the domain's authorization and review rules.\n- start_email: manage_assistant action=start_email. An explicit request grants paid model work, permitted reads and one retained draft for the exact workspace person and eligible mailbox. Keep the request UUID and all inputs unchanged on retry. Inspect email_scope and review_message_id on the saved task. The exact sender, recipient, subject and body require separate human review before sending. Approval does not prove delivery.\n- scope_edit: unsupported. No sender, recipient, or task-instruction changes after start. Cancel unused work and create a new request for changed scope.\n- delivery_replacement: unsupported. An unknown model or delivery outcome never authorizes replacement work. The original saved task owns recovery and receipt checks.\n\nPrivate saved conversations support (assistant_saved_conversations):\nProduct support is not permission. Inspect current work and follow the domain's authorization and review rules.\n- follow_up: manage_assistant action=follow_up. Continue the latest completed private analysis at its current revision. Exact request UUID retries return the same child Action. Use existing fetch assistant_task links to read every permitted prior turn. Historical answers are not current facts or execution authority.\n- active_steering: unsupported. A running task cannot accept new messages. Complete it before following up.\n- sharing: unsupported. No shared participants, source publication, or actor transfer.\n\nSaved assistant tasks support (assistant_saved_tasks):\nProduct support is not permission. Inspect current work and follow the domain's authorization and review rules.\n- start: manage_assistant action=start_analysis. An explicit request grants paid read_analysis.v1 only. Exact request UUID retries recover the same task.\n- list: fetch type=assistant_tasks. Page own work or authorized workspace metadata with next_cursor.\n- inspect: fetch type=assistant_task. Read current state, Action version and exact review links.\n- events: fetch type=assistant_task_events. Page journal events by sequence; no raw worker state or hidden reasoning.\n- content: fetch type=assistant_task_content. Read complete immutable content pages under the original current actor and login.\n- cancel: manage_assistant action=cancel. Cancel at the current Action version; in-flight effects may still finish.\n- conversation_import: unsupported. No caller history, thread import, or appended task messages.\n- email_activation: unsupported. This analysis capability cannot start email work. Use the separate assistant_saved_email start_email capability for one reviewed email.\n- executor_transfer: unsupported. No actor, sender, or harness/worker authority transfer.",
1143
+ "description": "Manage Assistant\n\nStart, continue, or cancel private analysis and reviewed email work.\n\n- start_analysis: no id; payload={request_id (UUID), message}. Call only\n after the user requests this analysis. This call explicitly grants\n revenue_operator.read_analysis.v1: paid model work using permitted reads,\n without tool writes or external effects. Keep the exact request UUID and\n message on retries; the saved task journal owns request identity and\n recovery. An uncertain response never authorizes a replacement task.\n- start_email: no id; payload={request_id (UUID), message, person_id,\n sender_config_id}. Call only after the user requests this email work.\n Authorizes paid model work, permitted reads and one retained email draft\n for that workspace contact and an eligible mailbox available to the\n current actor. It does not approve or send. Read the returned email_scope\n and linked review_message_id. Review the exact sender, recipient, subject\n and complete body through the existing message review before approving.\n Keep the same request UUID, message, person and mailbox on retries;\n uncertain acknowledgement never authorizes another task or delivery.\n- cancel: id=the saved task's Action UUID; payload={expected_version} from\n a fresh fetch assistant_task. The original current actor or a current\n workspace owner/operator may cancel future continuation. An in-flight\n effect or provider call may still finish; cancellation cannot recall it.\n- follow_up: id=the latest eligible saved Action UUID; payload={request_id,\n expected_version, message}. Only its current original actor/login can\n continue. This buys a new Action in the same private conversation. Completed\n analysis or email can continue. Revising an unapproved email atomically\n retires that draft; the new draft requires its own exact approval. Contact,\n sender and the complete email envelope stay fixed. Approved, dispatching,\n unresolved, cancelled or blocked work cannot continue. Keep the exact UUID,\n parent, revision and message on retries, including an uncertain response.\n The server reconstructs permitted history and refreshes company context.\n Historical answers and delivery receipts never authorize another send.\n\nAll actions are scalar: no id arrays or items. No caller history, imported\nthread, email-scope edits, additional effects, actor transfer, or worker\ncontrol fields are accepted. This facade adds no authority to its target.\nThe task is private to its original current actor and login; owner/operator\noversight gives metadata and cancellation, never another member's content.\nExisting retained email work uses its exact linked review without changing\nthe sender. Inspect fetch assistant_task, page fetch assistant_task_events,\nand retrieve full content with fetch assistant_task_content. Read prior\nturns by following previous_action_id from fetch assistant_task until it is\nnull, then order by conversation_turn. Follow next_action_id to newer work. There is no steering of running work or shared conversation. Public chat\ncompletion limits remain active.\n\n### Responses:\n\n**200**: Successful Response (Success Response)\nContent-Type: application/json\n\nPrivate saved email support (assistant_saved_email):\nProduct support is not permission. Inspect current work and follow the domain's authorization and review rules.\n- start_email: manage_assistant action=start_email. An explicit request grants paid model work, permitted reads and one retained draft for the exact workspace person and eligible mailbox. Keep the request UUID and all inputs unchanged on retry. Inspect email_scope and review_message_id on the saved task. The exact sender, recipient, subject and body require separate human review before sending. Approval does not prove delivery.\n- scope_edit: unsupported. No sender or recipient changes after start. Cancel unused work and create a new request for changed scope.\n- delivery_replacement: unsupported. An unknown model or delivery outcome never authorizes replacement work. The original saved task owns recovery and receipt checks.\n\nPrivate saved conversations support (assistant_saved_conversations):\nProduct support is not permission. Inspect current work and follow the domain's authorization and review rules.\n- follow_up: manage_assistant action=follow_up. Continue completed private analysis or email, or revise an unapproved email. Its contact and full envelope stay fixed. A revision retires the old draft and requires a new approval. Exact request UUID retries recover the same child Action. Historical receipts never approve a send.\n- active_steering: unsupported. A running task cannot accept new messages. Complete it before following up.\n- sharing: unsupported. No shared participants, source publication, or actor transfer.\n\nSaved assistant tasks support (assistant_saved_tasks):\nProduct support is not permission. Inspect current work and follow the domain's authorization and review rules.\n- start: manage_assistant action=start_analysis. An explicit request grants paid read_analysis.v1 only. Exact request UUID retries recover the same task.\n- list: fetch type=assistant_tasks. Page own work or authorized workspace metadata with next_cursor.\n- inspect: fetch type=assistant_task. Read current state, Action version and exact review links.\n- events: fetch type=assistant_task_events. Page journal events by sequence; no raw worker state or hidden reasoning.\n- content: fetch type=assistant_task_content. Read complete immutable content pages under the original current actor and login.\n- cancel: manage_assistant action=cancel. Cancel at the current Action version; in-flight effects may still finish.\n- conversation_import: unsupported. No caller history, thread import, or appended task messages.\n- email_activation: unsupported. This analysis capability cannot start email work. Use the separate assistant_saved_email start_email capability for one reviewed email.\n- executor_transfer: unsupported. No actor, sender, or harness/worker authority transfer.",
1144
1144
  "inputSchema": {
1145
1145
  "properties": {
1146
1146
  "action": {