distil-ai-rms-reporting 1.0.21 → 1.0.23

package/dist/api.js

@@ -13,7 +13,7 @@ exports.apiGetSummaryStats = apiGetSummaryStats;
 exports.apiGetRevenueStats = apiGetRevenueStats;
 exports.apiGetTimePatternStats = apiGetTimePatternStats;
 exports.apiGetDemandAnalytics = apiGetDemandAnalytics;
-exports.apiGetOpenTableChangeLog = apiGetOpenTableChangeLog;
+exports.apiGetChangeLog = apiGetChangeLog;
 exports.apiGetAvailabilityAnalytics = apiGetAvailabilityAnalytics;
 exports.apiGetDemandOutlook = apiGetDemandOutlook;
 exports.apiGetReviewStats = apiGetReviewStats;
@@ -164,7 +164,7 @@ async function apiGetDemandAnalytics(dimension, flagType, restaurantName, theDat
         params.set("tenant_code", tenantCode);
     return request(`/demand-analytics?${params}`);
 }
-async function apiGetOpenTableChangeLog(dimension, eventType, username, restaurantName, rid, dateFrom, dateTo, period, limit, tenantCode) {
+async function apiGetChangeLog(dimension, eventType, username, restaurantName, rid, dateFrom, dateTo, period, limit, tenantCode) {
     const params = new URLSearchParams({ dimension });
     if (eventType)
         params.set("event_type", eventType);
@@ -184,7 +184,7 @@ async function apiGetOpenTableChangeLog(dimension, eventType, username, restaura
         params.set("limit", limit);
     if (tenantCode)
         params.set("tenant_code", tenantCode);
-    return request(`/opentable-change-log?${params}`);
+    return request(`/change-log?${params}`);
 }
 async function apiGetAvailabilityAnalytics(dimension, flagType, restaurantName, serviceDate, tenantCode) {
     const params = new URLSearchParams({ dimension });

package/dist/http.js

@@ -72,7 +72,7 @@ async function createSession(apiKey) {
             availableDatasetTypes = new Set(Object.values(index_js_2.TOOL_DATASET_MAP));
         }
         // Create MCP server and transport for this session
-        const server = new index_js_1.Server({ name: "distil-ai-rms-reporting", version: "1.0.0" }, { capabilities: { tools: {} } });
+        const server = new index_js_1.Server({ name: "distil-ai-rms-reporting", version: "1.0.0" }, { capabilities: { tools: {} }, instructions: index_js_2.SERVER_INSTRUCTIONS });
         (0, index_js_2.registerHandlers)(server, availableDatasetTypes, ctx);
         const transport = new streamableHttp_js_1.StreamableHTTPServerTransport({
             sessionIdGenerator: () => crypto_1.default.randomUUID(),

package/dist/index.js

@@ -4,7 +4,7 @@ var __importDefault = (this && this.__importDefault) || function (mod) {
     return (mod && mod.__esModule) ? mod : { "default": mod };
 };
 Object.defineProperty(exports, "__esModule", { value: true });
-exports.ALL_TOOLS = exports.TOOL_DATASET_MAP = void 0;
+exports.ALL_TOOLS = exports.TOOL_DATASET_MAP = exports.SERVER_INSTRUCTIONS = void 0;
 exports.registerHandlers = registerHandlers;
 const crypto_1 = __importDefault(require("crypto"));
 const index_js_1 = require("@modelcontextprotocol/sdk/server/index.js");
@@ -25,6 +25,26 @@ const PROMPT_PARAM = {
         description: "Optional. Pass the user's original natural language question that triggered this tool call. Used for usage analytics and improving data quality.",
     },
 };
+// Top-level routing guidance for Claude. Sent on initialize, applies before
+// any tool selection. Use this for cross-tool decision rules that don't fit
+// neatly inside a single tool description.
+exports.SERVER_INSTRUCTIONS = `Distil RMS Reporting MCP — restaurant analytics across reservations, demand, availability, POS, marketing, loyalty, change-log, and more.
+
+Tool-selection priorities:
+
+1. Reservation pacing ("on the book at T-N", "this week vs last week", "how is Saturday building", "covers booked by yesterday"): use get_pacing_stats. Default for any pace question on actual reservations.
+
+2. Forward-looking demand-search signal ("baseline", "days-out booking curve", "demand vs historical median at the same days_out"): use get_demand_outlook. Only when the user explicitly mentions demand or baselines.
+
+3. Aggregate counts/covers/revenue by visit date: get_date_stats / get_revenue_stats. Do NOT pull rows from query_reservations to count — use the aggregate endpoints.
+
+4. Audit / change-log questions ("who changed what", "recent admin activity", "configuration drift"): use get_change_log.
+
+5. POS check-level data (sales, comps, item mix): use the get_aloha_* family.
+
+6. Use query_reservations only when the user needs raw rows (specific bookings, guest details, notes). It caps at 1000 rows; aggregates belong in stats endpoints.
+
+If a tool is missing for the question, say so plainly rather than approximating with raw row pulls.`;
 // Maps each tool to the dataset_type it requires
 exports.TOOL_DATASET_MAP = {
     get_schema: "reservations",
@@ -37,7 +57,7 @@ exports.TOOL_DATASET_MAP = {
     get_demand_outlook: "demand",
     get_demand_analytics: "demand_analytics",
     get_availability_analytics: "availability_analytics",
-    get_opentable_change_log: "opentable_group_change_log",
+    get_change_log: "opentable_group_change_log",
     get_review_stats: "reviews",
     get_forecast_stats: "cover_forecast",
     get_aloha_schema: "aloha_opentable_pos",
@@ -220,7 +240,7 @@ exports.ALL_TOOLS = [
     },
     {
         name: "get_pacing_stats",
-        description: "Returns booking-pace ('T-N' / 'as-of') aggregates: for a given visit date (or range), how many reservations and covers were on the book by end of as_of_date, plus the current non-cancelled total and pace percentages. Use this for any 'where were we at T-1 / T-7 / last week vs this week' question. One call replaces multi-call pagination over /reservations/query with created_date / cancellation_date filters.",
+        description: "DEFAULT TOOL for any 'pace', 'pacing', 'on the book', 'T-N', 'T-1 / T-7', 'where were we at this time last week', or 'how is the book building' question about ACTUAL RESERVATIONS. Returns, for a given visit date (or range), how many reservations and covers were on the book by end of as_of_date, the current non-cancelled total, and pace percentages. One call replaces multi-call pagination over /reservations/query with created_date / cancellation_date filters. NOT for forward-looking demand-search signal — for that use get_demand_outlook.",
         inputSchema: {
             type: "object",
             properties: {
@@ -253,14 +273,14 @@ exports.ALL_TOOLS = [
     },
     {
         name: "get_demand_outlook",
-        description: "Queries the data_restaurant_demand_master table to analyse forward-looking demand. Use this for questions about upcoming reservation demand, booking pace (how far in advance guests book), party size distribution in the outlook period, or which restaurants have the highest expected demand. Always uses the latest snapshot by default.",
+        description: "Forward-looking DEMAND-SEARCH signal from the data_restaurant_demand_master snapshot — what guests are searching for and how that's tracking vs the same-day-of-week historical baseline at the same days-out. Use ONLY when the user explicitly asks about 'demand', 'demand search', 'demand outlook', 'baseline', or 'days-out booking curve'. NOT for reservation pacing — for 'how many covers were on the book at T-1 / vs last week' on actual reservations, use get_pacing_stats instead. The booking_pace and pace_by_date dimensions here describe how demand-search builds over days_out (a curve), NOT the as-of count of reservations on the book.",
         inputSchema: {
             type: "object",
             properties: {
                 dimension: {
                     type: "string",
                     enum: ["by_date", "by_restaurant", "by_party_size", "booking_pace", "pace_by_date", "by_date_restaurant", "pace_snapshot"],
-                    description: "pace_snapshot: USE THIS FIRST for any demand outlook or booking pace question. Returns one row per restaurant × future date with: days_out_today, cum_demand_today, baseline_median (same-DOW historical median at the same days_out), pct_vs_baseline, flag (Well ahead/Ahead/On track/Behind/Well behind), party mix % by band (mix_small_pct/mix_standard_pct/mix_medium_pct/mix_large_pct/mix_event_pct), and mix_shift_flag highlighting the biggest mix shift vs baseline if >10pp. One call replaces 36+ multi-call pace patterns. by_date: total demand per upcoming date (all restaurants combined). by_restaurant: demand ranked by restaurant for the outlook period. by_party_size: demand distribution across party sizes. booking_pace: booking curve aggregated across all dates. pace_by_date: booking curve per restaurant × date × days_out — all restaurants included unless restaurant_name filter applied. by_date_restaurant: per-date per-restaurant demand from the latest snapshot.",
+                    description: "pace_snapshot: USE THIS FIRST for any demand-search outlook or days-out booking-curve question. Returns one row per restaurant × future date with: days_out_today, cum_demand_today, baseline_median (median of same-DOW past dates at the same days_out horizon, pulled from historical snapshots), sample_count (how many past dates fed the baseline — treat baselines below ~4 samples as low-confidence), pct_vs_baseline, flag (Well ahead/Ahead/On track/Behind/Well behind/No baseline), party mix % by band (mix_small_pct/mix_standard_pct/mix_medium_pct/mix_large_pct/mix_event_pct), and mix_shift_flag highlighting the biggest mix shift vs baseline if >10pp. One call replaces 36+ multi-call pace patterns. by_date: total demand per upcoming date (all restaurants combined). by_restaurant: demand ranked by restaurant for the outlook period. by_party_size: demand distribution across party sizes. booking_pace: booking curve aggregated across all dates. pace_by_date: booking curve per restaurant × date × days_out — all restaurants included unless restaurant_name filter applied. by_date_restaurant: per-date per-restaurant demand from the latest snapshot.",
                 },
                 snapshot_date: {
                     type: "string",
@@ -349,8 +369,8 @@ exports.ALL_TOOLS = [
         },
     },
     {
-        name: "get_opentable_change_log",
-        description: "Queries data_opentable_change_log_master — OpenTable audit events for the tenant's restaurants (floor plan changes, shift edits, permission changes, section configuration updates, etc). Use this to investigate who changed what and when, audit configuration drift, or summarise recent admin activity across a group. Requires the tenant to have the opentable_group_change_log dataset configured.",
+        name: "get_change_log",
+        description: "Audit / change-log events for the tenant's restaurants — floor plan changes, shift edits, permission changes, section configuration updates, etc. Use this for any 'change log', 'audit', 'who changed what', 'recent admin activity', or 'configuration drift' question. Returns counts and timelines of change events; use the recent dimension for raw events and the by_* dimensions for summaries.",
         inputSchema: {
             type: "object",
             properties: {
@@ -1196,11 +1216,11 @@ function registerHandlers(server, availableDatasetTypes, tenantContext) {
                         const data = await (0, tools_js_1.getAvailabilityAnalytics)(a.dimension, a.flag_type, a.restaurant_name, a.service_date, a.tenant_code);
                         return { content: [{ type: "text", text: JSON.stringify(data, null, 2) }] };
                     }
-                    case "get_opentable_change_log": {
+                    case "get_change_log": {
                         if (!a.dimension) {
                             return { content: [{ type: "text", text: "Error: dimension is required." }], isError: true };
                         }
-                        const data = await (0, tools_js_1.getOpenTableChangeLog)(a.dimension, a.event_type, a.username, a.restaurant_name, a.rid, a.date_from, a.date_to, a.period, a.limit, a.tenant_code);
+                        const data = await (0, tools_js_1.getChangeLog)(a.dimension, a.event_type, a.username, a.restaurant_name, a.rid, a.date_from, a.date_to, a.period, a.limit, a.tenant_code);
                         return { content: [{ type: "text", text: JSON.stringify(data, null, 2) }] };
                     }
                     case "get_review_stats": {
@@ -1442,7 +1462,7 @@ async function main() {
             console.error(`Dataset discovery failed, exposing all tools: ${err instanceof Error ? err.message : String(err)}`);
             availableDatasetTypes = new Set(Object.values(exports.TOOL_DATASET_MAP));
         }
-        const server = new index_js_1.Server({ name: "distil-ai-rms-reporting", version: "1.0.0" }, { capabilities: { tools: {} } });
+        const server = new index_js_1.Server({ name: "distil-ai-rms-reporting", version: "1.0.0" }, { capabilities: { tools: {} }, instructions: exports.SERVER_INSTRUCTIONS });
         registerHandlers(server, availableDatasetTypes, ctx);
         const transport = new stdio_js_1.StdioServerTransport();
         await server.connect(transport);

package/dist/tools.js

@@ -7,7 +7,7 @@ exports.getRevenueStats = getRevenueStats;
 exports.getTimePatternStats = getTimePatternStats;
 exports.getDemandAnalytics = getDemandAnalytics;
 exports.getAvailabilityAnalytics = getAvailabilityAnalytics;
-exports.getOpenTableChangeLog = getOpenTableChangeLog;
+exports.getChangeLog = getChangeLog;
 exports.getDemandOutlook = getDemandOutlook;
 exports.getReviewStats = getReviewStats;
 exports.getForecastStats = getForecastStats;
@@ -95,9 +95,9 @@ async function getAvailabilityAnalytics(dimension, flagType, restaurantName, ser
     const { data } = await (0, api_js_1.apiGetAvailabilityAnalytics)(dimension, flagType, restaurantName, serviceDate, tenantCode);
     return checkResponseSize("get_availability_analytics", data);
 }
-async function getOpenTableChangeLog(dimension, eventType, username, restaurantName, rid, dateFrom, dateTo, period, limit, tenantCode) {
-    const { data } = await (0, api_js_1.apiGetOpenTableChangeLog)(dimension, eventType, username, restaurantName, rid, dateFrom, dateTo, period, limit, tenantCode);
-    return checkResponseSize("get_opentable_change_log", data);
+async function getChangeLog(dimension, eventType, username, restaurantName, rid, dateFrom, dateTo, period, limit, tenantCode) {
+    const { data } = await (0, api_js_1.apiGetChangeLog)(dimension, eventType, username, restaurantName, rid, dateFrom, dateTo, period, limit, tenantCode);
+    return checkResponseSize("get_change_log", data);
 }
 async function getDemandOutlook(dimension, snapshotDate, restaurantName, dateFrom, dateTo, partySize, tenantCode) {
     const { data } = await (0, api_js_1.apiGetDemandOutlook)(dimension, snapshotDate, restaurantName, dateFrom, dateTo, partySize, tenantCode);

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "distil-ai-rms-reporting",
-  "version": "1.0.21",
+  "version": "1.0.23",
   "description": "MCP server for restaurant management system reporting and analytics",
   "main": "dist/index.js",
   "bin": {