@sap-ux/fiori-mcp-server 0.1.2 → 0.1.3

package/README.md

@@ -74,15 +74,15 @@ The following rules help guide the LLM to use the server correctly:
 
 ## [Available Tools](#available-tools)
 
-#### `doc-search`
-Searches Fiori Elements, Annotations, SAPUI5, Fiori tools documentation for the given query.
-Note: the results are based on the the most recent indexed version of SAPUI5 documentation
+#### `search_docs`
+Searches Fiori Elements, Annotations, UI5, Fiori tools documentation for the given query.
+Note: the results are based on the most recent indexed version of UI5 documentation
 
 
-#### `list-fiori-apps`
+#### `list_fiori_apps`
 Scans a specified directory to find existing SAP Fiori applications that can be modified.
 
-#### `list-functionalities` (Step 1 of 3)
+#### `list_functionalities` (Step 1 of 3)
 Gets the list of supported functionalities to create a new or modify an existing SAP Fiori application.
 
 The main functionalities are:
@@ -92,10 +92,10 @@ The main functionalities are:
 - Adding and modifying controller extensions
 - Modifying `manifest.json` properties depending on the app (e.g. adding Flexible Column Layout, enabling initial load)
 
-#### `get-functionality-details` (Step 2 of 3)
+#### `get_functionality_details` (Step 2 of 3)
 Gets the required parameters and detailed information for a specific functionality to create a new or modify an existing SAP Fiori application.
 
-#### `execute-functionality` (Step 3 of 3)
+#### `execute_functionality` (Step 3 of 3)
 Executes a specific functionality to create a new or modify an existing SAP Fiori application with provided parameters.
 
 ## Code of Conduct

package/dist/index.js

@@ -203999,7 +203999,7 @@ var StdioServerTransport = class {
 };
 
 // package.json
-var version = "0.1.2";
+var version = "0.1.3";
 var package_default = {
   name: "@sap-ux/fiori-mcp-server",
   description: "SAP Fiori - Model Context Protocol (MCP) server",
@@ -208779,7 +208779,7 @@ var FioriAppSchema = object({
 var FunctionalityIdSchema = union([string2(), array(union([string2(), number2()]))]);
 var FunctionalitySchema = object({
   functionalityId: FunctionalityIdSchema.describe(
-    "Identifier to pass as the `functionalityId` parameter when calling `get-functionality-details` or `execute-functionality`"
+    "Identifier to pass as the `functionalityId` parameter when calling `get_functionality_details` or `execute_functionality`"
   ),
   description: string2()
 });
@@ -208861,7 +208861,7 @@ var ListFunctionalitiesOutputSchema = object({
 var GetFunctionalityDetailsOutputSchema = object({
   /** ID of the functionality */
   functionalityId: FunctionalityIdSchema.describe(
-    "Identifier to pass as the `functionalityId` parameter when calling `get-functionality-details` or `execute-functionality`"
+    "Identifier to pass as the `functionalityId` parameter when calling `get_functionality_details` or `execute_functionality`"
   ),
   /** Name of the functionality */
   name: string2(),
@@ -218918,7 +218918,7 @@ function findParameterById(functionality, id) {
 // src/tools/index.ts
 var tools = [
   {
-    name: "doc-search",
+    name: "search_docs",
     title: "Search in Fiori Documentation",
     description: "Searches code snippets of Fiori Elements, Annotations, SAPUI5, Fiori tools documentation for the given query. You MUST use this tool if you're unsure about Fiori APIs. Optionally returns only code blocks.",
     inputSchema: {
@@ -218938,7 +218938,7 @@ var tools = [
     }
   },
   {
-    name: "list-fiori-apps",
+    name: "list_fiori_apps",
     description: `Scans a specified directory to find existing SAP Fiori applications that can be modified.
                     This is an optional, preliminary tool.
                     **Use this first ONLY if the target application's name or path is not already known.**
@@ -218947,33 +218947,33 @@ var tools = [
     outputSchema: convertToSchema(ListFioriAppsOutputSchema)
   },
   {
-    name: "list-functionality",
+    name: "list_functionality",
     description: `**(Step 1 of 3)**
                     Gets the complete and exclusive list of supported functionalities to create a new or modify an existing SAP Fiori application.
                     This is the **first mandatory step** to begin the workflow and requires a valid absolute path to a SAP Fiori application as input.
-                    You MUST use a functionalityId from this tool's output to request details to the functionality in 'get-functionality-details' (Step 2).
+                    You MUST use a functionalityId from this tool's output to request details to the functionality in 'get_functionality_details' (Step 2).
                     You MUST not use a functionalityId as name of a tool.
                     Do not guess, assume, or use any functionality not present in this list, as it is invalid and will cause the operation to fail.
-                    **Note: If the target application is not known, use the list-fiori-apps tool first to identify it.**
-                    if the functionality list does not include a functionality to support the current goal, then try using the doc-search tool as a fallback.`,
+                    **Note: If the target application is not known, use the list_fiori_apps tool first to identify it.**
+                    if the functionality list does not include a functionality to support the current goal, then try using the search_docs tool as a fallback.`,
     inputSchema: convertToSchema(ListFunctionalitiesInputSchema),
     outputSchema: convertToSchema(ListFunctionalitiesOutputSchema)
   },
   {
-    name: "get-functionality-details",
+    name: "get_functionality_details",
     description: `**(Step 2 of 3)**
                     Gets the required parameters and detailed information for a specific functionality to create a new or modify an existing SAP Fiori application.
-                    You MUST provide a functionalityId obtained from 'list-functionality' (Step 1).
-                    The output of this tool is required for the final step 'execute-functionality' (Step 3).`,
+                    You MUST provide a functionalityId obtained from 'list_functionality' (Step 1).
+                    The output of this tool is required for the final step 'execute_functionality' (Step 3).`,
     inputSchema: convertToSchema(GetFunctionalityDetailsInputSchema),
     outputSchema: convertToSchema(GetFunctionalityDetailsOutputSchema)
   },
   {
-    name: "execute-functionality",
+    name: "execute_functionality",
     description: `**(Step 3 of 3)**
                     Executes a specific functionality to create a new or modify an existing SAP Fiori application with provided parameters.
                     This is the **final step** of the workflow and performs the actual creation or modification.
-                    You MUST provide the exact parameter information obtained from get-functionality-details (Step 2).`,
+                    You MUST provide the exact parameter information obtained from get_functionality_details (Step 2).`,
     inputSchema: convertToSchema(ExecuteFunctionalityInputSchema),
     outputSchema: convertToSchema(ExecuteFunctionalityOutputSchema)
   }
@@ -219175,25 +219175,25 @@ var FioriFunctionalityServer = class {
           functionalityId: args?.functionalityId
         };
         switch (name) {
-          case "doc-search":
+          case "search_docs":
             result = await docSearch(args);
             return this.convertResultToCallToolResult(result.results);
-          case "list-fiori-apps":
+          case "list_fiori_apps":
             result = await listFioriApps(args);
             break;
-          case "list-functionality":
+          case "list_functionality":
             result = await listFunctionalities(args);
             break;
-          case "get-functionality-details":
+          case "get_functionality_details":
             result = await getFunctionalityDetails5(args);
             break;
-          case "execute-functionality":
+          case "execute_functionality":
             result = await executeFunctionality5(args);
             break;
           default:
             await TelemetryHelper.sendTelemetry(unknownTool, telemetryProperties, args?.appPath);
             throw new Error(
-              `Unknown tool: ${name}. Try one of: list-fiori-apps, list-functionality, get-functionality-details, execute-functionality.`
+              `Unknown tool: ${name}. Try one of: list_fiori_apps, list_functionality, get_functionality_details, execute_functionality.`
             );
         }
         await TelemetryHelper.sendTelemetry(name, telemetryProperties, args?.appPath);

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@sap-ux/fiori-mcp-server",
   "description": "SAP Fiori - Model Context Protocol (MCP) server",
-  "version": "0.1.2",
+  "version": "0.1.3",
   "keywords": [
     "SAP Fiori tools",
     "SAP Fiori elements",
@@ -38,14 +38,14 @@
     "i18next": "25.3.0",
     "os-name": "4.0.1",
     "zod": "4.1.5",
-    "@sap-ux/project-access": "1.32.1",
     "@sap-ux/fiori-annotation-api": "0.6.23",
     "@sap-ux/fiori-docs-embeddings": "0.0.2",
     "@sap-ux/i18n": "0.3.3",
+    "@sap-ux/project-access": "1.32.1",
     "@sap-ux/odata-annotation-core-types": "0.4.6",
     "@sap-ux/odata-entity-model": "0.3.1",
-    "@sap-ux/text-document-utils": "0.3.1",
     "@sap-ux/btp-utils": "1.1.2",
+    "@sap-ux/text-document-utils": "0.3.1",
     "@sap-ux/feature-toggle": "0.3.1",
     "@sap-ux/nodejs-utils": "0.2.4",
     "@sap-ux/telemetry": "0.6.23"