@adminforth/agent 1.20.0 → 1.21.0

package/apiBasedTools.ts

@@ -75,6 +75,7 @@ type ToolOverrideContext = {
 
 type ToolOverride = {
   wipe_frontend_specific_data?: readonly string[];
+  format_tool?: (params: ToolOverrideContext) => Promise<string> | string;
   post_process_response?: (params: ToolOverrideContext) => Promise<unknown> | unknown;
 };
 
@@ -103,6 +104,9 @@ const TOOL_OVERRIDES: Record<string, ToolOverride> = {
       'resource.options.actions[].customComponent',
       'resource.options.pageInjections',
     ],
+    format_tool: async ({ }) => {
+      return "get resource Apartments"
+    }
   },
   get_resource_data: {
     post_process_response: async ({ output, inputs, invokeTool, userTimeZone }) => {
@@ -126,6 +130,9 @@ const TOOL_OVERRIDES: Record<string, ToolOverride> = {
 
       return response;
     },
+    format_tool: async ({ }) => {
+      return "get 1-20 Apartment filtered listed=yes"
+    }
   },
 };
 

package/build.log

@@ -32,5 +32,5 @@ custom/skills/fetch_data/SKILL.md
 custom/skills/mutate_data/
 custom/skills/mutate_data/SKILL.md
 
-sent 188,483 bytes  received 451 bytes  377,868.00 bytes/sec
-total size is 186,631  speedup is 0.99
+sent 188,784 bytes  received 451 bytes  378,470.00 bytes/sec
+total size is 186,932  speedup is 0.99

package/custom/skills/data-analytics/SKILL.md

@@ -12,10 +12,10 @@ Use `get_resource_data` to fetch data for this skill. This is the main tool for
 
 When the user asks for analytics, reports, trends, comparisons, or distributions:
 
-- Fetch the underlying rows with `get_resource_data`.
-- Prefer narrow requests: request only the columns you need and use filters, sorting, pagination, and date ranges whenever possible.
+- Fetch the requested data using `aggregate` tool. This tool is capable of performing fast server-side aggregations on filtered data, groupings by date including grouping by day/week/month etc. 
+- if it is not possible to get the required aggregates using `aggregate`, fetch the underlying rows with `get_resource_data`. This is much heavier since returns original rows  with all fields, but allows you to perform complex calculations, comparisons, and custom groupings in-memory. Always prefer `aggregate` when possible.
+- Prefer narrow requests: use filters, sorting, pagination, and date ranges whenever possible.
 - If the request is ambiguous, clarify the resource, metric, grouping, or date range before fetching data.
-- Compute aggregates from the returned rows yourself: sums, counts, averages, min/max, grouped totals, ratios, and trend deltas.
 - Return a short written summary with the key finding and most important numbers.
 - If a chart would help, produce a Vega-Lite spec.
 

package/dist/apiBasedTools.js

@@ -25,6 +25,9 @@ const TOOL_OVERRIDES = {
             'resource.options.actions[].customComponent',
             'resource.options.pageInjections',
         ],
+        format_tool: (_a) => __awaiter(void 0, [_a], void 0, function* ({}) {
+            return "get resource Apartments";
+        })
     },
     get_resource_data: {
         post_process_response: (_a) => __awaiter(void 0, [_a], void 0, function* ({ output, inputs, invokeTool, userTimeZone }) {
@@ -44,6 +47,9 @@ const TOOL_OVERRIDES = {
             formatDateTimeColumns(response.data, dateTimeColumnNames, localizedTimeZone);
             return response;
         }),
+        format_tool: (_a) => __awaiter(void 0, [_a], void 0, function* ({}) {
+            return "get 1-20 Apartment filtered listed=yes";
+        })
     },
 };
 function sanitizeForYaml(value) {

package/dist/custom/skills/data-analytics/SKILL.md

@@ -12,10 +12,10 @@ Use `get_resource_data` to fetch data for this skill. This is the main tool for
 
 When the user asks for analytics, reports, trends, comparisons, or distributions:
 
-- Fetch the underlying rows with `get_resource_data`.
-- Prefer narrow requests: request only the columns you need and use filters, sorting, pagination, and date ranges whenever possible.
+- Fetch the requested data using `aggregate` tool. This tool is capable of performing fast server-side aggregations on filtered data, groupings by date including grouping by day/week/month etc. 
+- if it is not possible to get the required aggregates using `aggregate`, fetch the underlying rows with `get_resource_data`. This is much heavier since returns original rows  with all fields, but allows you to perform complex calculations, comparisons, and custom groupings in-memory. Always prefer `aggregate` when possible.
+- Prefer narrow requests: use filters, sorting, pagination, and date ranges whenever possible.
 - If the request is ambiguous, clarify the resource, metric, grouping, or date range before fetching data.
-- Compute aggregates from the returned rows yourself: sums, counts, averages, min/max, grouped totals, ratios, and trend deltas.
 - Return a short written summary with the key finding and most important numbers.
 - If a chart would help, produce a Vega-Lite spec.
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@adminforth/agent",
-  "version": "1.20.0",
+  "version": "1.21.0",
   "main": "dist/index.js",
   "types": "dist/index.d.ts",
   "type": "module",