@phenomenalorg/mcp 0.5.155 → 0.5.156

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@phenomenalorg/mcp",
-  "version": "0.5.155",
+  "version": "0.5.156",
   "type": "module",
   "description": "Phenomenal MCP bridge — connects a stdio-only MCP client to the Phenomenal MCP server over Streamable HTTP, with browser sign-in.",
   "license": "MIT",

package/skill/SKILL.md

@@ -8,7 +8,7 @@ description: Use when the user wants to manage a PTO, school or club in Phenomen
 <!-- Generated from the Phenomenal tool registry. Do not edit by hand: a drift
      gate fails when these files are not what the registry currently says. -->
 
-_Tool surface: 51 tools · 285 actions · 5 prompts · fingerprint `2b71c10d`._
+_Tool surface: 51 tools · 288 actions · 5 prompts · fingerprint `2a2ce58b`._
 
 You are connected to Phenomenal, the platform for this organization's site, members, events, tickets, email, forms, store and money.
 

package/skill/references/mutations.md

@@ -3,7 +3,7 @@
 <!-- Generated from the Phenomenal tool registry. Do not edit by hand: a drift
      gate fails when these files are not what the registry currently says. -->
 
-_Tool surface: 51 tools · 285 actions · 5 prompts · fingerprint `2b71c10d`._
+_Tool surface: 51 tools · 288 actions · 5 prompts · fingerprint `2a2ce58b`._
 
 The curated tools in `references/tools.md` cover the work an officer does most days. Everything else Phenomenal can do is reachable by name:
 
@@ -15,7 +15,7 @@ Prefer a curated tool when one covers what you need: it is one call instead of t
 
 **(confirm)** marks an action that sends mail, moves money, publishes something publicly, deletes something, changes who can do what, or changes the organization's web address. Those change nothing until a person has said yes in words. Every action is subject to your role in the organization regardless; the confirm gate is about being asked, not about being allowed.
 
-Areas: account, billing, brand, broadcasts, connections, domains, drive, email-preferences, events, forms, groups, inbox, inventory, knowledge, looks, media, meetings, members, money, notebook, orders, organization, pages, requests, reusable-content, store, tasks, tickets.
+Areas: account, automations, billing, brand, broadcasts, connections, domains, drive, email-preferences, events, forms, groups, inbox, inventory, knowledge, looks, media, meetings, members, money, notebook, orders, organization, pages, requests, reusable-content, store, tasks, tickets.
 
 ## account
 
@@ -236,6 +236,7 @@ Areas: account, billing, brand, broadcasts, connections, domains, drive, email-p
 - `setMeetingSecretary` **(confirm)** — Hand a meeting to another admin or owner to run.
 - `setMeetingSpeakerName` — Name one diarized voice in a meeting transcript (spanId + provider label) as an org member or a typed guest name; it applies to every line with that label in that stream.
 - `setMinutesReadyNotify` — Ask, or stop asking, to be emailed a link when an adjourned meeting's minutes draft finishes compiling.
+- `setOpenItemsSettings` — Change the organization’s open-items choices: whether a tabled motion joins the open items, whether the Unfinished Business agenda item lists them, and what a new agenda calls the section.
 - `setOrgRecordingStatement` **(confirm)** — Set the organization’s own recording/consent statement, in English and Spanish, that the Secretary reads aloud and attendees see before a meeting is recorded.
 - `startMeeting` **(confirm)** — Start a meeting.
 - `suggestPoll` — Suggest a poll question and options from the recent meeting transcript.
@@ -370,6 +371,8 @@ Areas: account, billing, brand, broadcasts, connections, domains, drive, email-p
 
 - `createTask` — Prefer the `create_task` tool. Create a follow-up task, optionally assigned to a member and tied to a meeting.
 - `setTaskStatus` — Prefer the `set_task_status` tool. Mark a task open or done.
+- `translateOpenItems` — Fill in the missing translations of every open item’s title.
+- `updateTask` — Edit an open item (a task): its title, owner or due date.
 
 ## tickets
 

package/skill/references/schema.md

@@ -3,7 +3,7 @@
 <!-- Generated from the Phenomenal tool registry. Do not edit by hand: a drift
      gate fails when these files are not what the registry currently says. -->
 
-_Tool surface: 51 tools · 285 actions · 5 prompts · fingerprint `2b71c10d`._
+_Tool surface: 51 tools · 288 actions · 5 prompts · fingerprint `2a2ce58b`._
 
 Two tools answer questions no curated tool anticipated.
 

package/skill/references/starting-doc.md

@@ -3,7 +3,7 @@
 <!-- Generated from the Phenomenal tool registry. Do not edit by hand: a drift
      gate fails when these files are not what the registry currently says. -->
 
-_Tool surface: 51 tools · 285 actions · 5 prompts · fingerprint `2b71c10d`._
+_Tool surface: 51 tools · 288 actions · 5 prompts · fingerprint `2a2ce58b`._
 
 Phenomenal runs a school's PTO: its public website, its member roster, its events and tickets, its email to families, its forms, its store and its money. It exposes all of that over the Model Context Protocol, so an assistant an officer already uses can do the work with them.
 

package/skill/references/tools.md

@@ -3,7 +3,7 @@
 <!-- Generated from the Phenomenal tool registry. Do not edit by hand: a drift
      gate fails when these files are not what the registry currently says. -->
 
-_Tool surface: 51 tools · 285 actions · 5 prompts · fingerprint `2b71c10d`._
+_Tool surface: 51 tools · 288 actions · 5 prompts · fingerprint `2a2ce58b`._
 
 Every tool the Phenomenal MCP server offers, in the order a client lists them. `list_my_orgs` is first because every other tool needs an organization id from it.
 
@@ -466,7 +466,7 @@ Refund an event ticket purchase in Phenomenal in full and void its tickets. Mone
 
 - `orgId` (string) — The organization to act for — an id from list_my_orgs. Never invent one; if you are unsure which, ask the person.
 - `purchaseId` (string, required) — The ticket order id.
-- `eventId` (string) — The event the purchase belongs to, from list_events. Optional, and worth passing: with it the preview can name the buyer and the amount.
+- `eventId` (string) — The event the purchase belongs to, from list_events. Optional, and worth passing: with it the preview can name the event and the amount. Who bought it stays in Phenomenal.
 - `reason` (string) — Why it is being refunded, in a sentence the buyer will read.
 - `confirm` (boolean) — First call without confirm. Present the returned action, target and effect, END THE TURN, and wait for a NEW explicit user message approving that exact preview. Only then set true for the same action/target. Initial requests and client/native tool-permission approvals do not count.
 
@@ -493,7 +493,7 @@ Pay a Phenomenal organization's available Stripe balance out to its bank account
 
 ### `list_tasks`
 
-The follow-up tasks in a Phenomenal organization — who owes what, and by when.
+The organization’s open items: the running list of follow-up tasks a board carries between meetings — who owes what, and by when. Open items also show on the next agenda’s Unfinished Business.
 
 **Hints:** read-only, idempotent. **Confirm:** not required.
 
@@ -611,7 +611,7 @@ Every action Phenomenal can take that the curated tools do not already cover, as
 
 **Arguments**
 
-- `area` (string (account | billing | brand | broadcasts | connections | domains | drive | email-preferences | events | forms | groups | inbox | inventory | knowledge | looks | media | meetings | members | money | notebook | orders | organization | pages | requests | reusable-content | store | tasks | tickets)) — Only actions in this part of Phenomenal.
+- `area` (string (account | automations | billing | brand | broadcasts | connections | domains | drive | email-preferences | events | forms | groups | inbox | inventory | knowledge | looks | media | meetings | members | money | notebook | orders | organization | pages | requests | reusable-content | store | tasks | tickets)) — Only actions in this part of Phenomenal.
 - `search` (string) — Only actions whose name or summary contains this word.
 
 ### `describe_mutation`