@phenomenalorg/mcp 0.5.135 → 0.5.137

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@phenomenalorg/mcp",
-  "version": "0.5.135",
+  "version": "0.5.137",
   "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 · 254 actions · 5 prompts · fingerprint `459df39a`._
+_Tool surface: 51 tools · 263 actions · 5 prompts · fingerprint `4e7e4652`._
 
 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 · 254 actions · 5 prompts · fingerprint `459df39a`._
+_Tool surface: 51 tools · 263 actions · 5 prompts · fingerprint `4e7e4652`._
 
 The curated tools in `references/tools.md` cover the work an officer does most days. Everything else Phenomenal can do is reachable by name:
 
@@ -249,15 +249,18 @@ Areas: account, billing, brand, broadcasts, connections, domains, drive, email-p
 
 - `addBillingNote` — Add a shared staff note to a billing account: a note, a logged call, “calling now” to claim the call, or the day the family got in touch before a due date.
 - `attributeBillingPayment` — Say which payer made a payment that was recorded as “not sure”.
+- `authorizeReimbursement` **(confirm)** — Authorize or deny a reimbursement request before the purchase (optionally for a different amount than the estimate), or again when its invoice came in over what was authorized.
 - `choosePlan` — As a payer, ask for another of a program’s plans on your own enrollment that has no charges yet.
 - `closeBillingReview` — Close a staged billing account with what the committee decided.
 - `correctBillingPaymentAttribution` — Correct which payer a payment names when it names the wrong one, with a reason kept as a note.
 - `decideBillingProposal` **(confirm)** — Approve or decline a proposed late fee or suspension.
 - `decidePlanChoice` — Accept a payer’s plan choice with the confirmed total (it sets the plan and issues its payments together), or decline it with a note to the payer.
 - `recordBillingPayment` **(confirm)** — Record money that arrived on a billing account, from any rail (bank transfer, Stripe, cash, check), against the charges it pays, oldest due first.
+- `recordReimbursementPaid` **(confirm)** — Record that an authorized reimbursement with its invoice on file was paid in the bank run (the date and the bank reference).
 - `resetStripeOnboarding` — Start the organization's Stripe onboarding over with a new account, when Stripe rejected the current one.
 - `runBillingSweep` — Run today’s billing check now: propose late fees and suspensions from each program’s settings.
 - `sendBillingNotices` **(confirm)** — Send the first payment notices due today to each late account’s own payers, once per installment.
+- `sendReimbursementInvoice` **(confirm)** — Send the electronic invoice of what you bought for your own authorized reimbursement request: a file you uploaded, the invoice number, its date and its amount in minor units.
 - `stageBillingAccount` — Put a billing account on the committee’s list (“Stage for committee”).
 - `startPayout` **(confirm)** — Prefer the `start_payout` tool. Pay the available Stripe balance out to the organization's bank account.
 - `startStripeOnboarding` **(confirm)** — Begin Stripe onboarding for the organization and return the link to finish it.
@@ -269,7 +272,9 @@ Areas: account, billing, brand, broadcasts, connections, domains, drive, email-p
 ## orders
 
 - `cancelOrder` **(confirm)** — Prefer the `cancel_order` tool. Cancel a store order and, when asked, refund the buyer.
+- `markPrintfulCancelResolved` **(confirm)** — Clear the still-placed-at-Printful flag on a refunded store order once someone has dealt with it.
 - `retryOrder` **(confirm)** — Retry fulfillment for a store order that failed.
+- `retryPrintfulCancel` **(confirm)** — For a refunded store order flagged as still placed at Printful: ask Printful again to cancel it.
 
 ## organization
 
@@ -310,15 +315,19 @@ Areas: account, billing, brand, broadcasts, connections, domains, drive, email-p
 
 ## requests
 
+- `approveCommitteePurchases` **(confirm)** — Approve several purchases waiting for the purchase committee at once.
 - `cancelPurchaseRequest` — Withdraw your own purchase request while the purchaser is still picking it up or quoting it.
+- `cancelReimbursementRequest` — Withdraw your own reimbursement request while it is still waiting to be authorized.
 - `completePurchaseStep` — Move a purchase request on: pick it up, mark it ordered once approved, or mark it received (which closes it and tells the requester).
 - `decideWorkItem` — Approve or deny a request waiting for approval, such as a teacher’s time off or a quoted purchase.
 - `recordPurchaseQuote` — Record the supplier and the quoted amount for a purchase request in the organization’s currency (USD or CRC), in minor units (cents or céntimos) as a string: ₡25,000 is amountMinor "2500000" and $45.50 is "4550", not "25000".
 - `recordSubstitute` — Record who covers an approved time-off request.
 - `requestPurchase` — Ask for something to be bought for yourself: what, how many, and the date it is needed by (at least the organization’s purchase lead time ahead).
+- `requestReimbursement` — Ask to buy something urgent yourself and be paid back: what, why it cannot wait, about how much in minor units (céntimos for CRC) as a string, and the date it is needed by.
 - `requestTimeOff` — Ask for time off for yourself (a day, part of a day, or a few days).
 - `setMaterialsRequesterCannotDeliver` — Turn on or off whether the person who asked for a materials line may also be the one who delivers it (off by default: they may).
 - `setProcessSettings` — Replace the organization's back-office rules for time off (the longest request in days), purchases and materials (how many days ahead, calendar or business days, the delivery weekdays 1 = Monday to 7 = Sunday; for purchases the largest quote, as amountMaxMinor in minor units (céntimos): a cap of ₡1,000,000,000 is “100000000000”; the older amountMax takes whole units).
+- `updateMaterialsLineDetails` — Change the brand and specs on your own line of a materials request that is not in the catalog, while the purchaser is still picking it up or quoting it.
 
 ## reusable-content
 

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 · 254 actions · 5 prompts · fingerprint `459df39a`._
+_Tool surface: 51 tools · 263 actions · 5 prompts · fingerprint `4e7e4652`._
 
 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 · 254 actions · 5 prompts · fingerprint `459df39a`._
+_Tool surface: 51 tools · 263 actions · 5 prompts · fingerprint `4e7e4652`._
 
 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 · 254 actions · 5 prompts · fingerprint `459df39a`._
+_Tool surface: 51 tools · 263 actions · 5 prompts · fingerprint `4e7e4652`._
 
 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.
 
@@ -548,7 +548,7 @@ The forms in a Phenomenal organization — sign-ups, RSVPs, volunteer slots —
 
 ### `form_submissions`
 
-The answers people have submitted to a Phenomenal form, newest first. These carry family names and email addresses — keep them inside your answer to the officer and do not repeat them elsewhere.
+The answers people have submitted to a Phenomenal form, newest first, with who submitted each one when they were signed in. These carry family names and email addresses — keep them inside your answer to the officer and do not repeat them elsewhere.
 
 **Hints:** read-only, idempotent. **Confirm:** not required.
 
@@ -557,6 +557,7 @@ The answers people have submitted to a Phenomenal form, newest first. These carr
 - `orgId` (string) — The organization to act for — an id from list_my_orgs. Never invent one; if you are unsure which, ask the person.
 - `formId` (string) — From list_forms. Leave it out for every form.
 - `status` (string) — Only submissions in this state, e.g. "new".
+- `since` (string) — An ISO date-time. Only submissions made AFTER it (not at it): pass the newest createdAt you have already read.
 - `limit` (integer) — How many to return (1–100, default 25).
 - `cursor` (string) — The nextCursor from a previous call.