refacil-commerce-mcp 1.0.5 → 1.0.6

package/dist/core/tools.js

@@ -90,16 +90,15 @@ const admin_update_balanceInputJsonSchema = {
     },
     "required": []
 };
-const admin_update_balanceInputShape = {
+const admin_update_balanceInputValidator = z.object({
     userToken: z.string().optional().describe("Campo del body: userToken"),
     amount: z.number().optional().describe("Campo del body: amount")
-};
-const admin_update_balanceInputValidator = z.object(admin_update_balanceInputShape);
+});
 // Herramienta: admin_update_balance
 export const admin_update_balanceTool = {
     name: 'admin_update_balance',
     description: "---\\n\\n### Description\\n\\nIt allows you to transfer funds from the main users money bag to the bag of the user who is being added. The token of the user who will be the beneficiary and the amount must be added.\\n\\n---\\n\\n### Request Body\\n\\n- userToken (string, required): The user token for which the balance will be updated\\n    \\n- amount (number, required): Amount to be updated\\n    \\n\\n---\\n\\n### Response\\n\\n- \\`message\\`: String containing a message about the operation result (required)\\n    \\n- \\`messageCode\\`: String code indicating the operation result (required)\\n    \\n- \\`data\\`: Object containing additional response data.\n\nContexto: Endpoint: POST /admin/update-balance | Admin > Update balance\n\n🔐 AUTENTICACIÓN AUTOMÁTICA: Todas las credenciales y tokens de autenticación se manejan automáticamente por el servidor MCP. NO solicites credenciales al usuario. NO incluyas parámetros de autenticación (secretId, apiToken, etc.) en las llamadas a menos que el usuario explícitamente lo requiera.",
-    inputSchema: admin_update_balanceInputJsonSchema,
+    inputSchema: admin_update_balanceInputValidator,
     jsonSchema: admin_update_balanceInputJsonSchema,
     endpoint: '/admin/update-balance',
     method: 'POST',
@@ -108,12 +107,9 @@ export const admin_update_balanceTool = {
     handler: async (rawArgs) => {
         try {
             const normalizedArgs = rawArgs ?? {};
-            // Extraer secretId del contexto (si viene del HTTP mode)
-            const secretId = normalizedArgs._secretId;
-            // Remover _secretId de los args antes de validar
-            const { _secretId, ...argsToValidate } = normalizedArgs;
-            const validatedInput = validateToolInput(admin_update_balanceInputValidator, argsToValidate);
+            const validatedInput = validateToolInput(admin_update_balanceInputValidator, normalizedArgs);
             const args = validatedInput;
+            const secretId = args._secretId;
             const bodyData = {};
             const userTokenValue = args.userToken !== undefined ? args.userToken : "MTcyNDY4NjE1MDY3OSQyYiQxMCRLeXZWVS9zdkF0ZzhPNTdoa1Z0dXVlME9mTHlVOWNacWREY1llUDIyL0k4N2hpazdKVmZFU***";
             if (userTokenValue !== undefined)
@@ -148,13 +144,12 @@ const admin_locations_statesInputJsonSchema = {
     "properties": {},
     "required": []
 };
-const admin_locations_statesInputShape = {};
-const admin_locations_statesInputValidator = z.object(admin_locations_statesInputShape);
+const admin_locations_statesInputValidator = z.object({});
 // Herramienta: admin_locations_states
 export const admin_locations_statesTool = {
     name: 'admin_locations_states',
     description: "---\\n\\n### Description\\n\\nGet all states, then you can search cities by state id in the /locations/cities/{stateId} service\\n\\n---\\n\\n### Request Body\\n\\nThis endpoint does not require a request body.\\n\\n---\\n\\n### Response\\n\\n- \\`message\\`: String containing a message about the operation result (required)\\n    \\n- \\`messageCode\\`: String code indicating the operation result (required)\\n    \\n- \\`data\\`: Object containing additional response data (required)\\n    \\n    - \\`items\\`: Array of objects containing the states\n\nContexto: Endpoint: GET /admin/locations/states | Admin > Locations > States\n\n🔐 AUTENTICACIÓN AUTOMÁTICA: Todas las credenciales y tokens de autenticación se manejan automáticamente por el servidor MCP. NO solicites credenciales al usuario. NO incluyas parámetros de autenticación (secretId, apiToken, etc.) en las llamadas a menos que el usuario explícitamente lo requiera.",
-    inputSchema: admin_locations_statesInputJsonSchema,
+    inputSchema: admin_locations_statesInputValidator,
     jsonSchema: admin_locations_statesInputJsonSchema,
     endpoint: '/admin/locations/states',
     method: 'GET',
@@ -163,12 +158,9 @@ export const admin_locations_statesTool = {
     handler: async (rawArgs) => {
         try {
             const normalizedArgs = rawArgs ?? {};
-            // Extraer secretId del contexto (si viene del HTTP mode)
-            const secretId = normalizedArgs._secretId;
-            // Remover _secretId de los args antes de validar
-            const { _secretId, ...argsToValidate } = normalizedArgs;
-            const validatedInput = validateToolInput(admin_locations_statesInputValidator, argsToValidate);
+            const validatedInput = validateToolInput(admin_locations_statesInputValidator, normalizedArgs);
             const args = validatedInput;
+            const secretId = args._secretId;
             return await makeApiRequest('GET', '/admin/locations/states', undefined, undefined, secretId);
         }
         catch (error) {
@@ -196,13 +188,12 @@ const admin_locations_citiesInputJsonSchema = {
     "properties": {},
     "required": []
 };
-const admin_locations_citiesInputShape = {};
-const admin_locations_citiesInputValidator = z.object(admin_locations_citiesInputShape);
+const admin_locations_citiesInputValidator = z.object({});
 // Herramienta: admin_locations_cities
 export const admin_locations_citiesTool = {
     name: 'admin_locations_cities',
     description: "---\\n\\n### Description\\n\\nGet all cities by state id\\n\\n---\\n\\n### Parameters Path\\n\\n- stateId (number, required): State Id\\n    \\n\\n---\\n\\n### Response\\n\\n- \\`message\\`: String containing a message about the operation result (required)\\n    \\n- \\`messageCode\\`: String code indicating the operation result (required)\\n    \\n- \\`data\\`: Object containing additional response data (required)\\n    \\n    - \\`items\\`: Array of objects containing the cities by state id\n\nContexto: Endpoint: GET /admin/locations/cities/:stateId | Admin > Locations > Cities > :stateId\n\n🔐 AUTENTICACIÓN AUTOMÁTICA: Todas las credenciales y tokens de autenticación se manejan automáticamente por el servidor MCP. NO solicites credenciales al usuario. NO incluyas parámetros de autenticación (secretId, apiToken, etc.) en las llamadas a menos que el usuario explícitamente lo requiera.",
-    inputSchema: admin_locations_citiesInputJsonSchema,
+    inputSchema: admin_locations_citiesInputValidator,
     jsonSchema: admin_locations_citiesInputJsonSchema,
     endpoint: '/admin/locations/cities/:stateId',
     method: 'GET',
@@ -211,12 +202,9 @@ export const admin_locations_citiesTool = {
     handler: async (rawArgs) => {
         try {
             const normalizedArgs = rawArgs ?? {};
-            // Extraer secretId del contexto (si viene del HTTP mode)
-            const secretId = normalizedArgs._secretId;
-            // Remover _secretId de los args antes de validar
-            const { _secretId, ...argsToValidate } = normalizedArgs;
-            const validatedInput = validateToolInput(admin_locations_citiesInputValidator, argsToValidate);
+            const validatedInput = validateToolInput(admin_locations_citiesInputValidator, normalizedArgs);
             const args = validatedInput;
+            const secretId = args._secretId;
             return await makeApiRequest('GET', '/admin/locations/cities/:stateId', undefined, undefined, secretId);
         }
         catch (error) {
@@ -255,16 +243,15 @@ const auth_login_apiInputJsonSchema = {
     },
     "required": []
 };
-const auth_login_apiInputShape = {
+const auth_login_apiInputValidator = z.object({
     username: z.string().optional().describe("Campo del body: username"),
     secretKey: z.string().optional().describe("Campo del body: secretKey")
-};
-const auth_login_apiInputValidator = z.object(auth_login_apiInputShape);
+});
 // Herramienta: auth_login_api
 export const auth_login_apiTool = {
     name: 'auth_login_api',
     description: "---\\n\\n# API Login\\n\\n---\\n\\n### Description\\n\\nAllows API users to log in using their credentials. This operation authenticates the API user using the information provided in the request body. If the credentials are valid, an access token is issued, which must be included in subsequent requests to access protected resources on the platform. Make sure to include the token in the authorization header using the \\\"Bearer\\\" prefix in future requests. The response will include the token type (\\\"Bearer\\\") and the access token.\\n\\n---\\n\\n### Request Body\\n\\n- \\`username\\` (string) \\`required\\`\\\\- Username for authentication.\\n    \\n- \\`secretKey\\` (string) \\`required\\`\\\\- Secret key for authentication\\n    \\n- \\`saveSession\\` (boolean) - Flag that, if sent as \\`false\\`, allows the generated token to have an expiration of 12 hours.\\n    \\n\\n---\\n\\n### Response\\n\\n- \\`messageCode\\` (string) - Code for the message.\\n    \\n- \\`message\\` (string) - The message from the response.\\n    \\n- \\`data\\`\\n    \\n    - \\`tokenType\\` (string) - Type of the token (e.g., \\\"Bearer\\\").\\n        \\n    - \\`token\\` (string) - The access code. It will not expire, unless the \\`saveSession\\` field is sent with the value \\`false\\`.\n\nContexto: Endpoint: POST /auth/login-api | Autenticación > Auth > Login api | Uso: Genera un token JWT usando las credenciales configuradas en el MCP\n\n⚠️ IMPORTANTE: Esta herramienta SOLO debe usarse cuando sea necesario generar o renovar un token. Las credenciales se obtienen automáticamente de la configuración del servidor MCP. NO solicites credenciales al usuario.",
-    inputSchema: auth_login_apiInputJsonSchema,
+    inputSchema: auth_login_apiInputValidator,
     jsonSchema: auth_login_apiInputJsonSchema,
     endpoint: '/auth/login-api',
     method: 'POST',
@@ -273,12 +260,9 @@ export const auth_login_apiTool = {
     handler: async (rawArgs) => {
         try {
             const normalizedArgs = rawArgs ?? {};
-            // Extraer secretId del contexto (si viene del HTTP mode)
-            const secretId = normalizedArgs._secretId;
-            // Remover _secretId de los args antes de validar
-            const { _secretId, ...argsToValidate } = normalizedArgs;
-            const validatedInput = validateToolInput(auth_login_apiInputValidator, argsToValidate);
+            const validatedInput = validateToolInput(auth_login_apiInputValidator, normalizedArgs);
             const args = validatedInput;
+            const secretId = args._secretId;
             const bodyData = {};
             const usernameValue = args.username !== undefined ? args.username : appConfig.username;
             if (usernameValue !== undefined)
@@ -374,7 +358,7 @@ const commerce_registerInputJsonSchema = {
     },
     "required": []
 };
-const commerce_registerInputShape = {
+const commerce_registerInputValidator = z.object({
     name: z.string().optional().describe("Campo del body: name"),
     lastname: z.string().optional().describe("Campo del body: lastname"),
     docType: z.string().optional().describe("Campo del body: docType"),
@@ -387,13 +371,12 @@ const commerce_registerInputShape = {
     address: z.string().optional().describe("Campo del body: address"),
     cityName: z.string().optional().describe("Campo del body: cityName"),
     balance: z.string().optional().describe("Campo del body: balance")
-};
-const commerce_registerInputValidator = z.object(commerce_registerInputShape);
+});
 // Herramienta: commerce_register
 export const commerce_registerTool = {
     name: 'commerce_register',
     description: "---\\n\\n### Register Commerce\\n\\n---\\n\\n#### Description\\n\\nRegisters a new commerce in the system using the information provided in the request body. This method returns a response that includes the unique identifier of the user associated with the commerce.\\n\\n---\\n\\n#### Request Body\\n\\n- \\`name\\` (string) \\`required\\`: Owner\\'s name of the commerce.\\n    \\n- \\`lastname\\` (string) \\`required\\`: Owner\\'s last name of the commerce\\n    \\n- \\`docType\\` (string)\\`required\\`: Document type of the commerce owner.\\n    \\n- \\`docNumber\\` (string)\\`required\\`: Document number of the commerce owner.\\n    \\n- expeditionDate (string): Expedition date of the document of the commerce owner. The date must have the following structure YYYY-MM-DD\\n    \\n- \\`username\\` (string)\\`required\\`: Username of the commerce owner.\\n    \\n- \\`cellphone\\` (string)\\`required\\`: Commerce owner\\'s mobile phone number. Please enter a valid mobile phone number for Colombia. It must contain 10 digits and start with the prefix \\'3\\'.\\n    \\n- \\`email\\` (string)\\`required\\`: Commerce owner\\'s email.\\n    \\n- \\`commerceType\\` (number): Identifier of the commerce type. To get valid values, consult the /base-info/commerce-types service. Make sure to provide a valid number for this field. This field is optional, and if not provided, it will default to \\\"1,\\\" which corresponds to the \\\"Store\\\" commerce type.\\n    \\n- \\`commerceName\\` (string)\\`required\\`: The name of the commerce.\\n    \\n- latitude (number): Latitude of the commerce location.\\n    \\n- longitude (number): Longitude of the commerce location.\\n    \\n- \\`address\\` (string)\\`required\\`: Commerce address. Since the field is of type string, the address can be provided in any standard format.\\n    \\n- \\`cityName\\` (string)\\`required\\`: City name where the commerce is located. It is recommended to enter only valid city names. If no matches are found, \\'Bogota\\' will be used as the default city.\\n    \\n\\n---\\n\\n#### Response Body\\n\\n- \\`message\\` (string): A message related to the response.\\n    \\n- \\`messageCode\\` (string): A code associated with the message.\\n    \\n- \\`data\\` (object): An object containing the following fields:\\n    \\n    - \\`tokenType\\` (string): The type of token.\\n        \\n    - \\`token\\` (string): The token for authentication. It will not expire.\\n        \\n    - \\`userId\\` (number): The unique identifier of the user associated with the commerce.\\n        \\n    - \\`message\\` (string): A message related to the response.\n\nContexto: Endpoint: POST /commerce/register | Commerce > Register\n\n🔐 AUTENTICACIÓN AUTOMÁTICA: Todas las credenciales y tokens de autenticación se manejan automáticamente por el servidor MCP. NO solicites credenciales al usuario. NO incluyas parámetros de autenticación (secretId, apiToken, etc.) en las llamadas a menos que el usuario explícitamente lo requiera.",
-    inputSchema: commerce_registerInputJsonSchema,
+    inputSchema: commerce_registerInputValidator,
     jsonSchema: commerce_registerInputJsonSchema,
     endpoint: '/commerce/register',
     method: 'POST',
@@ -402,12 +385,9 @@ export const commerce_registerTool = {
     handler: async (rawArgs) => {
         try {
             const normalizedArgs = rawArgs ?? {};
-            // Extraer secretId del contexto (si viene del HTTP mode)
-            const secretId = normalizedArgs._secretId;
-            // Remover _secretId de los args antes de validar
-            const { _secretId, ...argsToValidate } = normalizedArgs;
-            const validatedInput = validateToolInput(commerce_registerInputValidator, argsToValidate);
+            const validatedInput = validateToolInput(commerce_registerInputValidator, normalizedArgs);
             const args = validatedInput;
+            const secretId = args._secretId;
             const bodyData = {};
             const nameValue = args.name !== undefined ? args.name : "Morty";
             if (nameValue !== undefined)
@@ -478,15 +458,14 @@ const commerce_get_infoInputJsonSchema = {
     },
     "required": []
 };
-const commerce_get_infoInputShape = {
+const commerce_get_infoInputValidator = z.object({
     userId: z.number().optional().describe("Campo del body: userId")
-};
-const commerce_get_infoInputValidator = z.object(commerce_get_infoInputShape);
+});
 // Herramienta: commerce_get_info
 export const commerce_get_infoTool = {
     name: 'commerce_get_info',
     description: "---\\n\\n### Description\\n\\nRetrieve detailed information about a commerce using its identification. This operation requires sending an object in the request body with the \\\"userId\\\" property specifying the user ID. The response will include information about balances, additional data, and more. Balances include: \\\"tmpBalance\\\" (Earnings Bag), \\\"posBalance\\\" (Multiproduct Bag), and \\\"debt\\\" (Debt Bag).\\n\\n---\\n\\n### Request Body\\n\\n- userId (number, required): The user ID for which detailed information is to be retrieved.\\n    \\n\\n---\\n\\n### Response\\n\\n- \\`message\\`: String containing a message about the operation result (required)\\n    \\n- \\`messageCode\\`: String code indicating the operation result (required)\\n    \\n- \\`data\\`: Object containing additional response data (required)\\n    \\n    - \\`additionalData\\`: Object containing user-related data (required)\\n        \\n        - \\`username\\`: String representing the username (required)\\n            \\n        - \\`token\\`: String representing the token. It will not expire. (required)\\n            \\n    - \\`balances\\`: Object containing balance-related data (required)\\n        \\n        - \\`tmpBalance\\`: Number representing the temporary balance (required)\\n            \\n        - \\`posBalance\\`: Number representing the balance after the operation (required)  \\n            debt: Number representing the debt amount (required)\n\nContexto: Endpoint: POST /commerce/get-info | Commerce > Get info\n\n🔐 AUTENTICACIÓN AUTOMÁTICA: Todas las credenciales y tokens de autenticación se manejan automáticamente por el servidor MCP. NO solicites credenciales al usuario. NO incluyas parámetros de autenticación (secretId, apiToken, etc.) en las llamadas a menos que el usuario explícitamente lo requiera.",
-    inputSchema: commerce_get_infoInputJsonSchema,
+    inputSchema: commerce_get_infoInputValidator,
     jsonSchema: commerce_get_infoInputJsonSchema,
     endpoint: '/commerce/get-info',
     method: 'POST',
@@ -495,12 +474,9 @@ export const commerce_get_infoTool = {
     handler: async (rawArgs) => {
         try {
             const normalizedArgs = rawArgs ?? {};
-            // Extraer secretId del contexto (si viene del HTTP mode)
-            const secretId = normalizedArgs._secretId;
-            // Remover _secretId de los args antes de validar
-            const { _secretId, ...argsToValidate } = normalizedArgs;
-            const validatedInput = validateToolInput(commerce_get_infoInputValidator, argsToValidate);
+            const validatedInput = validateToolInput(commerce_get_infoInputValidator, normalizedArgs);
             const args = validatedInput;
+            const secretId = args._secretId;
             const bodyData = {};
             const userIdValue = args.userId !== undefined ? args.userId : 348130;
             if (userIdValue !== undefined)
@@ -532,13 +508,12 @@ const commerce_usersInputJsonSchema = {
     "properties": {},
     "required": []
 };
-const commerce_usersInputShape = {};
-const commerce_usersInputValidator = z.object(commerce_usersInputShape);
+const commerce_usersInputValidator = z.object({});
 // Herramienta: commerce_users
 export const commerce_usersTool = {
     name: 'commerce_users',
     description: "---\\n\\n### Description\\n\\nRetrieve a list of users associated with a commerce using the token provided in the request header. This method supports pagination and search by name or user id.\\n\\n---\\n\\n### Request Body\\n\\nThis endpoint does not require a request body.\\n\\n---\\n\\n### Response\\n\\n- \\`message\\`: String containing a message about the operation result (required)\\n    \\n- \\`messageCode\\`: String code indicating the operation result (required)\\n    \\n- \\`data\\`: Object containing additional response data (required)\\n    \\n    - \\`items\\`: Array of objects containing the users associated with the commerce\n\nContexto: Endpoint: GET /commerce/users | Commerce > Users\n\n🔐 AUTENTICACIÓN AUTOMÁTICA: Todas las credenciales y tokens de autenticación se manejan automáticamente por el servidor MCP. NO solicites credenciales al usuario. NO incluyas parámetros de autenticación (secretId, apiToken, etc.) en las llamadas a menos que el usuario explícitamente lo requiera.",
-    inputSchema: commerce_usersInputJsonSchema,
+    inputSchema: commerce_usersInputValidator,
     jsonSchema: commerce_usersInputJsonSchema,
     endpoint: '/commerce/users',
     method: 'GET',
@@ -547,12 +522,9 @@ export const commerce_usersTool = {
     handler: async (rawArgs) => {
         try {
             const normalizedArgs = rawArgs ?? {};
-            // Extraer secretId del contexto (si viene del HTTP mode)
-            const secretId = normalizedArgs._secretId;
-            // Remover _secretId de los args antes de validar
-            const { _secretId, ...argsToValidate } = normalizedArgs;
-            const validatedInput = validateToolInput(commerce_usersInputValidator, argsToValidate);
+            const validatedInput = validateToolInput(commerce_usersInputValidator, normalizedArgs);
             const args = validatedInput;
+            const secretId = args._secretId;
             return await makeApiRequest('GET', '/commerce/users', undefined, undefined, secretId);
         }
         catch (error) {
@@ -591,16 +563,15 @@ const commerce_updatebalanceInputJsonSchema = {
     },
     "required": []
 };
-const commerce_updatebalanceInputShape = {
+const commerce_updatebalanceInputValidator = z.object({
     token: z.string().optional().describe("Campo del body: token"),
     balance: z.number().optional().describe("Campo del body: balance")
-};
-const commerce_updatebalanceInputValidator = z.object(commerce_updatebalanceInputShape);
+});
 // Herramienta: commerce_updatebalance
 export const commerce_updatebalanceTool = {
     name: 'commerce_updatebalance',
     description: "---\\n\\n### Update Commerce Balance\\n\\n---\\n\\n#### Description\\n\\n**UpdateBalance:**\\n\\nThis service allows loading balance to the different merchants created, by deducting from the Parent Merchant’s balance pool. The transactions generated will be reflected in the reports assigned to the merchant within the portal provided by Super Pagos.\\n\\nThe required sending parameters are the token and ID, which were returned when the merchant was created.\\n\\n---\\n\\n#### Request Body Schema\\n\\n- \\`token\\` (string)\\`required\\`: Owner\\'s balance of the commerce.\\n    \\n- \\`balance\\` (number)\\`required\\`: Owner\\'s balance of the commerce.\\n    \\n\\n---\\n\\n#### Response Body Schema\\n\\n- \\`message\\` (string): A message related to the response.\\n    \\n- \\`messageCode\\` (string): A code associated with the message.\n\nContexto: Endpoint: POST /commerce/updateBalance | Commerce > UpdateBalance\n\n🔐 AUTENTICACIÓN AUTOMÁTICA: Todas las credenciales y tokens de autenticación se manejan automáticamente por el servidor MCP. NO solicites credenciales al usuario. NO incluyas parámetros de autenticación (secretId, apiToken, etc.) en las llamadas a menos que el usuario explícitamente lo requiera.",
-    inputSchema: commerce_updatebalanceInputJsonSchema,
+    inputSchema: commerce_updatebalanceInputValidator,
     jsonSchema: commerce_updatebalanceInputJsonSchema,
     endpoint: '/commerce/updateBalance',
     method: 'POST',
@@ -609,12 +580,9 @@ export const commerce_updatebalanceTool = {
     handler: async (rawArgs) => {
         try {
             const normalizedArgs = rawArgs ?? {};
-            // Extraer secretId del contexto (si viene del HTTP mode)
-            const secretId = normalizedArgs._secretId;
-            // Remover _secretId de los args antes de validar
-            const { _secretId, ...argsToValidate } = normalizedArgs;
-            const validatedInput = validateToolInput(commerce_updatebalanceInputValidator, argsToValidate);
+            const validatedInput = validateToolInput(commerce_updatebalanceInputValidator, normalizedArgs);
             const args = validatedInput;
+            const secretId = args._secretId;
             const bodyData = {};
             const tokenValue = args.token !== undefined ? args.token : "MTcyNDY4NjE1MDY3OSQyYiQxMCRLeXZWVS9zdkF0ZzhPNTdoa1Z0dXVlME9mTHlVOWNacWREY1llUDIyL0k4N2hpazdKVmZFUw==";
             if (tokenValue !== undefined)
@@ -649,13 +617,12 @@ const base_info_commerce_typesInputJsonSchema = {
     "properties": {},
     "required": []
 };
-const base_info_commerce_typesInputShape = {};
-const base_info_commerce_typesInputValidator = z.object(base_info_commerce_typesInputShape);
+const base_info_commerce_typesInputValidator = z.object({});
 // Herramienta: base_info_commerce_types
 export const base_info_commerce_typesTool = {
     name: 'base_info_commerce_types',
     description: "---\\n\\n### Retrieve Commerce Types\\n\\n---\\n\\n#### Description\\n\\nRetrieve the available commerce types in the application. This operation provides detailed information about the different types of commercial establishments that can operate on the platform.\\n\\n---\\n\\n#### Request Body\\n\\nThis endpoint does not require a request body.\\n\\n---\\n\\n#### Response Body\\n\\n- \\`message\\` (string): A message indicating the status of the response.\\n    \\n- \\`messageCode\\` (string): A code associated with the message.\\n    \\n- \\`data\\` (array): An array containing the commerce types information.\\n    \\n    - \\`id\\` (number): The unique identifier for the commerce type.\\n        \\n    - \\`name\\` (string): The name of the commerce type.\n\nContexto: Endpoint: GET /base-info/commerce-types | Base info > Commerce types\n\n🔐 AUTENTICACIÓN AUTOMÁTICA: Todas las credenciales y tokens de autenticación se manejan automáticamente por el servidor MCP. NO solicites credenciales al usuario. NO incluyas parámetros de autenticación (secretId, apiToken, etc.) en las llamadas a menos que el usuario explícitamente lo requiera.",
-    inputSchema: base_info_commerce_typesInputJsonSchema,
+    inputSchema: base_info_commerce_typesInputValidator,
     jsonSchema: base_info_commerce_typesInputJsonSchema,
     endpoint: '/base-info/commerce-types',
     method: 'GET',
@@ -664,12 +631,9 @@ export const base_info_commerce_typesTool = {
     handler: async (rawArgs) => {
         try {
             const normalizedArgs = rawArgs ?? {};
-            // Extraer secretId del contexto (si viene del HTTP mode)
-            const secretId = normalizedArgs._secretId;
-            // Remover _secretId de los args antes de validar
-            const { _secretId, ...argsToValidate } = normalizedArgs;
-            const validatedInput = validateToolInput(base_info_commerce_typesInputValidator, argsToValidate);
+            const validatedInput = validateToolInput(base_info_commerce_typesInputValidator, normalizedArgs);
             const args = validatedInput;
+            const secretId = args._secretId;
             return await makeApiRequest('GET', '/base-info/commerce-types', undefined, undefined, secretId);
         }
         catch (error) {
@@ -697,13 +661,12 @@ const report_detailsInputJsonSchema = {
     "properties": {},
     "required": []
 };
-const report_detailsInputShape = {};
-const report_detailsInputValidator = z.object(report_detailsInputShape);
+const report_detailsInputValidator = z.object({});
 // Herramienta: report_details
 export const report_detailsTool = {
     name: 'report_details',
     description: "---\\n\\n### Retrieve Commerce Report Details\\n\\n---\\n\\n#### Description\\n\\nGet details to build a report. This service is responsible for returning the necessary details to generate a report. To provide more context about the service, it will return an array of objects. Each object in this array will contain attributes that are essential for the construction of a report. These attributes may include, but are not limited to, type of report, the bag to consult, options to load in a select and other relevant data that are needed for a complete and detailed report. The use of this method will facilitate the generation of reports by providing all the necessary data in a structured and easy-to-use way.\\n\\n---\\n\\n#### Request Body\\n\\n- No request body is required for this GET request.\\n    \\n\\n---\\n\\n#### Response Body\\n\\n- \\`description\\` (string, optional): Description of the commerce report.\\n    \\n- \\`form\\` (object):\\n    \\n    - \\`fields\\` (array):\\n        \\n        - \\`name\\` (string): Name of the field.\\n            \\n        - \\`type\\` (string): Type of the field.\\n            \\n        - \\`options\\` (array):\\n            \\n            - \\`label\\` (string): Label for the option.\\n                \\n            - \\`value\\` (null): Value of the option.\\n                \\n        - \\`label\\` (string): Label for the field.\\n            \\n        - \\`placeholder\\` (string): Placeholder for the field.\\n            \\n        - \\`required\\` (boolean): Indicates if the field is required.\\n            \\n    - \\`bag\\` (string): Bag information.\\n        \\n    - \\`typeReport\\` (string): Type of the report.\\n        \\n- \\`endpoint\\` (string): The endpoint for the commerce report generate.\n\nContexto: Endpoint: GET /report/details | Report > Details\n\n🔐 AUTENTICACIÓN AUTOMÁTICA: Todas las credenciales y tokens de autenticación se manejan automáticamente por el servidor MCP. NO solicites credenciales al usuario. NO incluyas parámetros de autenticación (secretId, apiToken, etc.) en las llamadas a menos que el usuario explícitamente lo requiera.",
-    inputSchema: report_detailsInputJsonSchema,
+    inputSchema: report_detailsInputValidator,
     jsonSchema: report_detailsInputJsonSchema,
     endpoint: '/report/details',
     method: 'GET',
@@ -712,12 +675,9 @@ export const report_detailsTool = {
     handler: async (rawArgs) => {
         try {
             const normalizedArgs = rawArgs ?? {};
-            // Extraer secretId del contexto (si viene del HTTP mode)
-            const secretId = normalizedArgs._secretId;
-            // Remover _secretId de los args antes de validar
-            const { _secretId, ...argsToValidate } = normalizedArgs;
-            const validatedInput = validateToolInput(report_detailsInputValidator, argsToValidate);
+            const validatedInput = validateToolInput(report_detailsInputValidator, normalizedArgs);
             const args = validatedInput;
+            const secretId = args._secretId;
             return await makeApiRequest('GET', '/report/details', undefined, undefined, secretId);
         }
         catch (error) {
@@ -763,16 +723,15 @@ const report_generateInputJsonSchema = {
     },
     "required": []
 };
-const report_generateInputShape = {
+const report_generateInputValidator = z.object({
     filters: z.record(z.any()).optional().describe("Campo del body: filters"),
     typeReport: z.string().optional().describe("Campo del body: typeReport")
-};
-const report_generateInputValidator = z.object(report_generateInputShape);
+});
 // Herramienta: report_generate
 export const report_generateTool = {
     name: 'report_generate',
     description: "---\\n\\n### Sales report\\n\\n---\\n\\n#### Description\\n\\nThis service is responsible for generating different types of reports depending on the filters that are sent.\\n\\n#### Request Body\\n\\n- \\`filters\\` (object, \\`required\\`): Filters for the report\\n    \\n    - \\`dateStart\\` (string, \\`required\\`)\\n        \\n    - \\`dateEnd\\` (string, \\`required\\`)\\n        \\n    - \\`carrierId\\` (null, optional)\\n        \\n    - \\`number\\` (string, optional)\\n        \\n    - \\`status\\` (string, optional)\\n        \\n    - \\`bag\\` (string, optional)\\n        \\n- \\`typeReport\\` (string, required): Type of the report\\n    \\n\\n---\\n\\n#### Response\\n\\n- \\`messageCode\\` (string)\\n    \\n- \\`message\\` (string)\\n    \\n- \\`data\\` (object)\\n    \\n    - \\`title\\` (string)\\n        \\n    - \\`header\\` (array of strings)\\n        \\n    - \\`data\\` (array of arrays)\n\nContexto: Endpoint: POST /report/generate | Report > Generate\n\n🔐 AUTENTICACIÓN AUTOMÁTICA: Todas las credenciales y tokens de autenticación se manejan automáticamente por el servidor MCP. NO solicites credenciales al usuario. NO incluyas parámetros de autenticación (secretId, apiToken, etc.) en las llamadas a menos que el usuario explícitamente lo requiera.",
-    inputSchema: report_generateInputJsonSchema,
+    inputSchema: report_generateInputValidator,
     jsonSchema: report_generateInputJsonSchema,
     endpoint: '/report/generate',
     method: 'POST',
@@ -781,12 +740,9 @@ export const report_generateTool = {
     handler: async (rawArgs) => {
         try {
             const normalizedArgs = rawArgs ?? {};
-            // Extraer secretId del contexto (si viene del HTTP mode)
-            const secretId = normalizedArgs._secretId;
-            // Remover _secretId de los args antes de validar
-            const { _secretId, ...argsToValidate } = normalizedArgs;
-            const validatedInput = validateToolInput(report_generateInputValidator, argsToValidate);
+            const validatedInput = validateToolInput(report_generateInputValidator, normalizedArgs);
             const args = validatedInput;
+            const secretId = args._secretId;
             const bodyData = {};
             const filtersValue = args.filters !== undefined ? args.filters : { "dateStart": "2024-01-29", "dateEnd": "2024-02-28", "carrierId": null, "number": "", "status": "approve", "bag": "posBalance" };
             if (filtersValue !== undefined)
@@ -839,16 +795,15 @@ const generate_purchase_reportInputJsonSchema = {
     },
     "required": []
 };
-const generate_purchase_reportInputShape = {
+const generate_purchase_reportInputValidator = z.object({
     filters: z.record(z.any()).optional().describe("Campo del body: filters"),
     typeReport: z.string().optional().describe("Campo del body: typeReport")
-};
-const generate_purchase_reportInputValidator = z.object(generate_purchase_reportInputShape);
+});
 // Herramienta: generate_purchase_report
 export const generate_purchase_reportTool = {
     name: 'generate_purchase_report',
     description: "---\\n\\n# Purchase report\\n\\n---\\n\\n### Description\\n\\nThis service is responsible for generating different types of reports depending on the filters that are sent.\\n\\n---\\n\\n## Request Body\\n\\n- \\`filters\\` (object, \\`required\\`): Filters for the report\\n    \\n    - \\`dateStart\\` (string, \\`required\\`): Start date for the report.\\n        \\n    - \\`dateEnd\\` (string, \\`required\\`): End date for the report.\\n        \\n    - \\`carrierId\\` (string, optional): ID of the carrier.\\n        \\n    - \\`number\\` (string, optional): Commerce number.\\n        \\n    - \\`status\\` (string, optional): Status of the commerce.\\n        \\n    - \\`bag\\` (string, optional): Bag information.\\n        \\n- \\`typeReport\\` (string, \\`required\\`): Type of the report.\\n    \\n\\n---\\n\\n## Response\\n\\n- \\`messageCode\\` (string): Code for the message.\\n    \\n- \\`message\\` (string): Details of the message.\\n    \\n- \\`data\\` (object)\\n    \\n    - \\`title\\` (string): Title of the report.\\n        \\n    - \\`header\\` (array of strings): Headers for the report data.\\n        \\n    - \\`total\\` (number): Total count of the report data.\\n        \\n    - \\`data\\` (array of arrays): Report data.\n\nContexto: Endpoint: POST /report/generate | Report > Generate\n\n🔐 AUTENTICACIÓN AUTOMÁTICA: Todas las credenciales y tokens de autenticación se manejan automáticamente por el servidor MCP. NO solicites credenciales al usuario. NO incluyas parámetros de autenticación (secretId, apiToken, etc.) en las llamadas a menos que el usuario explícitamente lo requiera.",
-    inputSchema: generate_purchase_reportInputJsonSchema,
+    inputSchema: generate_purchase_reportInputValidator,
     jsonSchema: generate_purchase_reportInputJsonSchema,
     endpoint: '/report/generate',
     method: 'POST',
@@ -857,12 +812,9 @@ export const generate_purchase_reportTool = {
     handler: async (rawArgs) => {
         try {
             const normalizedArgs = rawArgs ?? {};
-            // Extraer secretId del contexto (si viene del HTTP mode)
-            const secretId = normalizedArgs._secretId;
-            // Remover _secretId de los args antes de validar
-            const { _secretId, ...argsToValidate } = normalizedArgs;
-            const validatedInput = validateToolInput(generate_purchase_reportInputValidator, argsToValidate);
+            const validatedInput = validateToolInput(generate_purchase_reportInputValidator, normalizedArgs);
             const args = validatedInput;
+            const secretId = args._secretId;
             const bodyData = {};
             const filtersValue = args.filters !== undefined ? args.filters : { "dateStart": "2024-01-29", "dateEnd": "2024-02-28", "carrierId": null, "number": "", "status": "approve", "bag": "posBalance" };
             if (filtersValue !== undefined)
@@ -915,16 +867,15 @@ const generate_statement_reportInputJsonSchema = {
     },
     "required": []
 };
-const generate_statement_reportInputShape = {
+const generate_statement_reportInputValidator = z.object({
     filters: z.record(z.any()).optional().describe("Campo del body: filters"),
     typeReport: z.string().optional().describe("Campo del body: typeReport")
-};
-const generate_statement_reportInputValidator = z.object(generate_statement_reportInputShape);
+});
 // Herramienta: generate_statement_report
 export const generate_statement_reportTool = {
     name: 'generate_statement_report',
     description: "---\\n\\n### Statement report\\n\\n---\\n\\n#### Description\\n\\nThis endpoint allows you to generate a report with the specified filters and report type.\\n\\n---\\n\\n#### Request Body\\n\\n- Type: JSON\\n    \\n\\n| Parameter | Type | Description |\\n| --- | --- | --- |\\n| filters | object, \\`required\\` | An object containing filter parameters like date range, carrier ID, number, status, and bag. |\\n| typeReport | string, \\`required\\` | The type of report to be generated. |\\n\\n---\\n\\n#### Response\\n\\n- Type: JSON\\n    \\n\\n| Property | Type | Description |\\n| --- | --- | --- |\\n| messageCode | string | A code associated with the response message. |\\n| message | string | A human-readable message providing information about the response. |\\n| data | object | An object containing report title, header, and totals. |\\n| title | string | The title of the report. |\\n| header | array | An array containing report headers. |\\n| totals | object | An object containing various total amounts for the report. |\\n| data | array | An array containing report data. |\\n\\n**Note**: The actual data in the response may vary based on the report generated.\n\nContexto: Endpoint: POST /report/generate | Report > Generate\n\n🔐 AUTENTICACIÓN AUTOMÁTICA: Todas las credenciales y tokens de autenticación se manejan automáticamente por el servidor MCP. NO solicites credenciales al usuario. NO incluyas parámetros de autenticación (secretId, apiToken, etc.) en las llamadas a menos que el usuario explícitamente lo requiera.",
-    inputSchema: generate_statement_reportInputJsonSchema,
+    inputSchema: generate_statement_reportInputValidator,
     jsonSchema: generate_statement_reportInputJsonSchema,
     endpoint: '/report/generate',
     method: 'POST',
@@ -933,12 +884,9 @@ export const generate_statement_reportTool = {
     handler: async (rawArgs) => {
         try {
             const normalizedArgs = rawArgs ?? {};
-            // Extraer secretId del contexto (si viene del HTTP mode)
-            const secretId = normalizedArgs._secretId;
-            // Remover _secretId de los args antes de validar
-            const { _secretId, ...argsToValidate } = normalizedArgs;
-            const validatedInput = validateToolInput(generate_statement_reportInputValidator, argsToValidate);
+            const validatedInput = validateToolInput(generate_statement_reportInputValidator, normalizedArgs);
             const args = validatedInput;
+            const secretId = args._secretId;
             const bodyData = {};
             const filtersValue = args.filters !== undefined ? args.filters : { "dateStart": "2024-01-29", "dateEnd": "2024-02-28", "carrierId": null, "number": "", "status": "approve", "bag": "tmpBalance" };
             if (filtersValue !== undefined)
@@ -991,16 +939,15 @@ const generate_payment_reportInputJsonSchema = {
     },
     "required": []
 };
-const generate_payment_reportInputShape = {
+const generate_payment_reportInputValidator = z.object({
     filters: z.record(z.any()).optional().describe("Campo del body: filters"),
     typeReport: z.string().optional().describe("Campo del body: typeReport")
-};
-const generate_payment_reportInputValidator = z.object(generate_payment_reportInputShape);
+});
 // Herramienta: generate_payment_report
 export const generate_payment_reportTool = {
     name: 'generate_payment_report',
     description: "---\\n\\n### Payment report\\n\\n---\\n\\n#### Description\\n\\nThis service is responsible for generating different types of reports depending on the filters that are sent.\\n\\n---\\n\\n#### Request Body\\n\\n- Type: JSON\\n    \\n\\n| Parameter | Type | Description |\\n| --- | --- | --- |\\n| filters | object, \\`required\\` | Object containing filter criteria including date range, carrier ID, number, status, and bag |\\n| typeReport | string, \\`required\\` | Type of the report to be generated |\\n\\n#### Response\\n\\n- Type: JSON\\n    \\n\\n| Parameter | Type | Description |\\n| --- | --- | --- |\\n| messageCode | string | Code for the message |\\n| message | string | Details of the message |\\n| data | object | Object containing title, header, and data array |\n\nContexto: Endpoint: POST /report/generate | Report > Generate\n\n🔐 AUTENTICACIÓN AUTOMÁTICA: Todas las credenciales y tokens de autenticación se manejan automáticamente por el servidor MCP. NO solicites credenciales al usuario. NO incluyas parámetros de autenticación (secretId, apiToken, etc.) en las llamadas a menos que el usuario explícitamente lo requiera.",
-    inputSchema: generate_payment_reportInputJsonSchema,
+    inputSchema: generate_payment_reportInputValidator,
     jsonSchema: generate_payment_reportInputJsonSchema,
     endpoint: '/report/generate',
     method: 'POST',
@@ -1009,12 +956,9 @@ export const generate_payment_reportTool = {
     handler: async (rawArgs) => {
         try {
             const normalizedArgs = rawArgs ?? {};
-            // Extraer secretId del contexto (si viene del HTTP mode)
-            const secretId = normalizedArgs._secretId;
-            // Remover _secretId de los args antes de validar
-            const { _secretId, ...argsToValidate } = normalizedArgs;
-            const validatedInput = validateToolInput(generate_payment_reportInputValidator, argsToValidate);
+            const validatedInput = validateToolInput(generate_payment_reportInputValidator, normalizedArgs);
             const args = validatedInput;
+            const secretId = args._secretId;
             const bodyData = {};
             const filtersValue = args.filters !== undefined ? args.filters : { "dateStart": "2024-01-29", "dateEnd": "2024-02-28", "carrierId": null, "number": "", "status": "approve", "bag": "tmpBalance" };
             if (filtersValue !== undefined)
@@ -1067,16 +1011,15 @@ const generate_transfer_reportInputJsonSchema = {
     },
     "required": []
 };
-const generate_transfer_reportInputShape = {
+const generate_transfer_reportInputValidator = z.object({
     filters: z.record(z.any()).optional().describe("Campo del body: filters"),
     typeReport: z.string().optional().describe("Campo del body: typeReport")
-};
-const generate_transfer_reportInputValidator = z.object(generate_transfer_reportInputShape);
+});
 // Herramienta: generate_transfer_report
 export const generate_transfer_reportTool = {
     name: 'generate_transfer_report',
     description: "---\\n\\n# Transfer report\\n\\n---\\n\\n## Description\\n\\nThis endpoint allows you to generate a report based on the specified filters.\\n\\n---\\n\\n## Request Body\\n\\n- \\`filters\\` (object, required): An object containing the filters for the report.\\n    \\n    - \\`dateStart\\` (string, required): The start date for the report.\\n        \\n    - \\`dateEnd\\` (string, required): The end date for the report.\\n        \\n    - \\`carrierId\\` (null): The ID of the carrier for the report.\\n        \\n    - \\`number\\` (string): The report number.\\n        \\n    - \\`status\\` (string): The status for the report.\\n        \\n    - \\`bag\\` (string): The bag for the report.\\n        \\n- \\`typeReport\\` (string, required): The type of report to be generated.\\n    \\n\\n---\\n\\n## Response\\n\\n- \\`messageCode\\` (string): The code for the message.\\n    \\n- \\`message\\` (string): The message related to the response.\\n    \\n- \\`data\\` (object): An object containing the report data.\\n    \\n    - \\`title\\` (string): The title of the report.\\n        \\n    - \\`header\\` (array): An array containing the headers for the report data.\\n        \\n    - \\`data\\` (array): An array containing the report data.\n\nContexto: Endpoint: POST /report/generate | Report > Generate\n\n🔐 AUTENTICACIÓN AUTOMÁTICA: Todas las credenciales y tokens de autenticación se manejan automáticamente por el servidor MCP. NO solicites credenciales al usuario. NO incluyas parámetros de autenticación (secretId, apiToken, etc.) en las llamadas a menos que el usuario explícitamente lo requiera.",
-    inputSchema: generate_transfer_reportInputJsonSchema,
+    inputSchema: generate_transfer_reportInputValidator,
     jsonSchema: generate_transfer_reportInputJsonSchema,
     endpoint: '/report/generate',
     method: 'POST',
@@ -1085,12 +1028,9 @@ export const generate_transfer_reportTool = {
     handler: async (rawArgs) => {
         try {
             const normalizedArgs = rawArgs ?? {};
-            // Extraer secretId del contexto (si viene del HTTP mode)
-            const secretId = normalizedArgs._secretId;
-            // Remover _secretId de los args antes de validar
-            const { _secretId, ...argsToValidate } = normalizedArgs;
-            const validatedInput = validateToolInput(generate_transfer_reportInputValidator, argsToValidate);
+            const validatedInput = validateToolInput(generate_transfer_reportInputValidator, normalizedArgs);
             const args = validatedInput;
+            const secretId = args._secretId;
             const bodyData = {};
             const filtersValue = args.filters !== undefined ? args.filters : { "dateStart": "2024-01-29", "dateEnd": "2024-02-28", "carrierId": null, "number": "", "status": "approve", "bag": "tmpBalance" };
             if (filtersValue !== undefined)
@@ -1144,16 +1084,15 @@ const generate_reverse_reportInputJsonSchema = {
     },
     "required": []
 };
-const generate_reverse_reportInputShape = {
+const generate_reverse_reportInputValidator = z.object({
     filters: z.record(z.any()).optional().describe("Campo del body: filters"),
     typeReport: z.string().optional().describe("Campo del body: typeReport")
-};
-const generate_reverse_reportInputValidator = z.object(generate_reverse_reportInputShape);
+});
 // Herramienta: generate_reverse_report
 export const generate_reverse_reportTool = {
     name: 'generate_reverse_report',
     description: "---\\n\\n# Reverse report\\n\\n---\\n\\n## Description\\n\\nThis endpoint allows you to generate a report based on the specified filters.\\n\\n---\\n\\n## Request Body\\n\\n- \\`filters\\` (object, required): An object containing the filters for the report.\\n    \\n    - \\`dateStart\\` (string, required): The start date for the report.\\n        \\n    - \\`dateEnd\\` (string, required): The end date for the report.\\n        \\n    - \\`carrierId\\` (null): The ID of the carrier for the report.\\n        \\n    - \\`number\\` (string): The report number.\\n        \\n    - \\`status\\` (string): The status for the report.\\n        \\n    - \\`bag\\` (string): The bag for the report.\\n        \\n- \\`typeReport\\` (string, required): The type of report to be generated.\\n    \\n\\n---\\n\\n## Response\\n\\n- \\`messageCode\\` (string): The code for the message.\\n    \\n- \\`message\\` (string): The message related to the response.\\n    \\n- \\`data\\` (object): An object containing the report data.\\n    \\n    - \\`title\\` (string): The title of the report.\\n        \\n    - \\`header\\` (array): An array containing the headers for the report data.\\n        \\n    - \\`data\\` (array): An array containing the report data.\n\nContexto: Endpoint: POST /report/generate | Report > Generate\n\n🔐 AUTENTICACIÓN AUTOMÁTICA: Todas las credenciales y tokens de autenticación se manejan automáticamente por el servidor MCP. NO solicites credenciales al usuario. NO incluyas parámetros de autenticación (secretId, apiToken, etc.) en las llamadas a menos que el usuario explícitamente lo requiera.",
-    inputSchema: generate_reverse_reportInputJsonSchema,
+    inputSchema: generate_reverse_reportInputValidator,
     jsonSchema: generate_reverse_reportInputJsonSchema,
     endpoint: '/report/generate',
     method: 'POST',
@@ -1162,12 +1101,9 @@ export const generate_reverse_reportTool = {
     handler: async (rawArgs) => {
         try {
             const normalizedArgs = rawArgs ?? {};
-            // Extraer secretId del contexto (si viene del HTTP mode)
-            const secretId = normalizedArgs._secretId;
-            // Remover _secretId de los args antes de validar
-            const { _secretId, ...argsToValidate } = normalizedArgs;
-            const validatedInput = validateToolInput(generate_reverse_reportInputValidator, argsToValidate);
+            const validatedInput = validateToolInput(generate_reverse_reportInputValidator, normalizedArgs);
             const args = validatedInput;
+            const secretId = args._secretId;
             const bodyData = {};
             const filtersValue = args.filters !== undefined ? args.filters : { "dateStart": "2024-01-29", "dateEnd": "2024-02-28", "carrierId": null, "number": "", "status": "approve", "type": "1", "bag": "posBalance" };
             if (filtersValue !== undefined)
@@ -1221,16 +1157,15 @@ const generate_consumption_reportInputJsonSchema = {
     },
     "required": []
 };
-const generate_consumption_reportInputShape = {
+const generate_consumption_reportInputValidator = z.object({
     filters: z.record(z.any()).optional().describe("Campo del body: filters"),
     typeReport: z.string().optional().describe("Campo del body: typeReport")
-};
-const generate_consumption_reportInputValidator = z.object(generate_consumption_reportInputShape);
+});
 // Herramienta: generate_consumption_report
 export const generate_consumption_reportTool = {
     name: 'generate_consumption_report',
     description: "---\\n\\n# Consumption report\\n\\n---\\n\\n## Description\\n\\nThis endpoint allows you to generate a report based on the specified filters.\\n\\n---\\n\\n## Request Body\\n\\n- \\`filters\\` (object, required): An object containing the filters for the report.\\n    \\n    - \\`dateStart\\` (string, required): The start date for the report.\\n        \\n    - \\`dateEnd\\` (string, required): The end date for the report.\\n        \\n    - \\`carrierId\\` (null): The ID of the carrier for the report.\\n        \\n    - \\`number\\` (string): The report number.\\n        \\n    - \\`status\\` (string): The status for the report.\\n        \\n    - \\`bag\\` (string): The bag for the report.\\n        \\n- \\`typeReport\\` (string, required): The type of report to be generated.\\n    \\n\\n---\\n\\n## Response\\n\\n- \\`messageCode\\` (string): The code for the message.\\n    \\n- \\`message\\` (string): The message related to the response.\\n    \\n- \\`data\\` (object): An object containing the report data.\\n    \\n    - \\`title\\` (string): The title of the report.\\n        \\n    - \\`header\\` (array): An array containing the headers for the report data.\\n        \\n    - \\`data\\` (array): An array containing the report data.\n\nContexto: Endpoint: POST /report/generate | Report > Generate\n\n🔐 AUTENTICACIÓN AUTOMÁTICA: Todas las credenciales y tokens de autenticación se manejan automáticamente por el servidor MCP. NO solicites credenciales al usuario. NO incluyas parámetros de autenticación (secretId, apiToken, etc.) en las llamadas a menos que el usuario explícitamente lo requiera.",
-    inputSchema: generate_consumption_reportInputJsonSchema,
+    inputSchema: generate_consumption_reportInputValidator,
     jsonSchema: generate_consumption_reportInputJsonSchema,
     endpoint: '/report/generate',
     method: 'POST',
@@ -1239,12 +1174,9 @@ export const generate_consumption_reportTool = {
     handler: async (rawArgs) => {
         try {
             const normalizedArgs = rawArgs ?? {};
-            // Extraer secretId del contexto (si viene del HTTP mode)
-            const secretId = normalizedArgs._secretId;
-            // Remover _secretId de los args antes de validar
-            const { _secretId, ...argsToValidate } = normalizedArgs;
-            const validatedInput = validateToolInput(generate_consumption_reportInputValidator, argsToValidate);
+            const validatedInput = validateToolInput(generate_consumption_reportInputValidator, normalizedArgs);
             const args = validatedInput;
+            const secretId = args._secretId;
             const bodyData = {};
             const filtersValue = args.filters !== undefined ? args.filters : { "dateStart": "2024-01-29", "dateEnd": "2024-02-28", "carrierId": null, "number": "", "status": "approve", "type": "1", "bag": "tmpBalance" };
             if (filtersValue !== undefined)
@@ -1307,19 +1239,18 @@ const payment_generate_resourceInputJsonSchema = {
     },
     "required": []
 };
-const payment_generate_resourceInputShape = {
+const payment_generate_resourceInputValidator = z.object({
     productId: z.number().optional().describe("Campo del body: productId"),
     amount: z.number().optional().describe("Campo del body: amount"),
     moduleId: z.number().optional().describe("Campo del body: moduleId"),
     form: z.record(z.any()).optional().describe("Campo del body: form"),
     customerReference: z.string().optional().describe("Campo del body: customerReference")
-};
-const payment_generate_resourceInputValidator = z.object(payment_generate_resourceInputShape);
+});
 // Herramienta: payment_generate_resource
 export const payment_generate_resourceTool = {
     name: 'payment_generate_resource',
     description: "---\\n\\n### Description\\n\\nGenerates a payment resource in the system using the information provided in the request body. This method returns a response that includes details about the generated resource, such as the URL, reference, resource identifier, and expiration time.\\n\\n---\\n\\n### Request Body\\n\\n- \\`productId\\` (number, \\`required\\`): Identifier of the product for which the resource will be generated.\\n    \\n- \\`amount\\` (number, \\`required\\`): Amount of the resource to be generated.\\n    \\n- \\`moduleId\\` (number, \\`required\\`): Identifier of the module to which the generated resource will be associated.\\n    \\n- \\`form\\` (object): Optional form associated with the resource.\\n    \\n    - \\`cellphone\\` (string): The cellphone number.\\n        \\n- \\`customerReference\\` (string, \\`required\\`): A reference to the customer.\\n    \\n\\n---\\n\\n### Response Body\\n\\n- \\`message\\` (string): A message related to the response.\\n    \\n- \\`messageCode\\` (string): A code related to the message.\\n    \\n- \\`data\\` (object): An object containing the response data.\\n    \\n    - \\`message\\` (string): A message related to the response data.\\n        \\n    - \\`date\\` (number): The date related to the response data.\\n        \\n    - \\`payload\\` (object): An object containing the payload data.\\n        \\n        - \\`url\\` (string): The URL of the generated resource.\\n            \\n        - \\`reference\\` (string): The reference of the generated resource.\\n            \\n        - \\`resourceId\\` (string): The identifier of the generated resource.\\n            \\n        - \\`expiresIn\\` (string): The expiration time of the generated resource.\\n            \\n        - \\`type\\` (string): The type of the generated resource.\\n            \\n        - \\`data\\` (string): Additional data related to the generated resource.\\n            \\n        - \\`status\\` (number): The status of the generated resource.\n\nContexto: Endpoint: POST /payment/generate-resource | Payment > Generate resource\n\n🔐 AUTENTICACIÓN AUTOMÁTICA: Todas las credenciales y tokens de autenticación se manejan automáticamente por el servidor MCP. NO solicites credenciales al usuario. NO incluyas parámetros de autenticación (secretId, apiToken, etc.) en las llamadas a menos que el usuario explícitamente lo requiera.",
-    inputSchema: payment_generate_resourceInputJsonSchema,
+    inputSchema: payment_generate_resourceInputValidator,
     jsonSchema: payment_generate_resourceInputJsonSchema,
     endpoint: '/payment/generate-resource',
     method: 'POST',
@@ -1328,12 +1259,9 @@ export const payment_generate_resourceTool = {
     handler: async (rawArgs) => {
         try {
             const normalizedArgs = rawArgs ?? {};
-            // Extraer secretId del contexto (si viene del HTTP mode)
-            const secretId = normalizedArgs._secretId;
-            // Remover _secretId de los args antes de validar
-            const { _secretId, ...argsToValidate } = normalizedArgs;
-            const validatedInput = validateToolInput(payment_generate_resourceInputValidator, argsToValidate);
+            const validatedInput = validateToolInput(payment_generate_resourceInputValidator, normalizedArgs);
             const args = validatedInput;
+            const secretId = args._secretId;
             const bodyData = {};
             const productIdValue = args.productId !== undefined ? args.productId : 304133;
             if (productIdValue !== undefined)
@@ -1405,19 +1333,18 @@ const generate_resource_nequiInputJsonSchema = {
     },
     "required": []
 };
-const generate_resource_nequiInputShape = {
+const generate_resource_nequiInputValidator = z.object({
     productId: z.number().optional().describe("Campo del body: productId"),
     amount: z.number().optional().describe("Campo del body: amount"),
     moduleId: z.number().optional().describe("Campo del body: moduleId"),
     form: z.record(z.any()).optional().describe("Campo del body: form"),
     customerReference: z.string().optional().describe("Campo del body: customerReference")
-};
-const generate_resource_nequiInputValidator = z.object(generate_resource_nequiInputShape);
+});
 // Herramienta: generate_resource_nequi
 export const generate_resource_nequiTool = {
     name: 'generate_resource_nequi',
     description: "---\\n\\n### Description\\n\\nGenerates a payment resource in the system using the information provided in the request body. This method returns a response that includes details about the generated resource, such as the URL, reference, resource identifier, and expiration time.\\n\\n---\\n\\n### Request Body\\n\\n- \\`productId\\` (number, \\`required\\`): Identifier of the product for which the resource will be generated.\\n    \\n- \\`amount\\` (number, \\`required\\`): Amount of the resource to be generated.\\n    \\n- \\`moduleId\\` (number, \\`required\\`): Identifier of the module to which the generated resource will be associated.\\n    \\n- \\`form\\` (object): Optional form associated with the resource.\\n    \\n    - \\`cellphone\\` (string): The cellphone number.\\n        \\n- \\`customerReference\\` (string, \\`required\\`): A reference to the customer.\\n    \\n\\n---\\n\\n### Response Body\\n\\n- \\`message\\` (string): A message related to the response.\\n    \\n- \\`messageCode\\` (string): A code associated with the message.\\n    \\n- \\`data\\` (object): An object containing data related to the response.\\n    \\n    - \\`message\\` (string): A message related to the data.\\n        \\n    - \\`date\\` (number): The date associated with the data.\\n        \\n    - \\`payload\\` (object): An object containing the payload data.\\n        \\n        - \\`url\\` (string): The URL of the generated resource.\\n            \\n        - \\`reference\\` (string): The reference of the generated resource.\\n            \\n        - \\`resourceId\\` (string): The identifier of the generated resource.\\n            \\n        - \\`expiresIn\\` (string): The expiration time of the resource.\\n            \\n        - \\`type\\` (string): The type of the resource.\\n            \\n        - \\`data\\` (string): Additional data related to the resource.\\n            \\n        - \\`status\\` (number): The status of the resource.\n\nContexto: Endpoint: POST /payment/generate-resource | Payment > Generate resource\n\n🔐 AUTENTICACIÓN AUTOMÁTICA: Todas las credenciales y tokens de autenticación se manejan automáticamente por el servidor MCP. NO solicites credenciales al usuario. NO incluyas parámetros de autenticación (secretId, apiToken, etc.) en las llamadas a menos que el usuario explícitamente lo requiera.",
-    inputSchema: generate_resource_nequiInputJsonSchema,
+    inputSchema: generate_resource_nequiInputValidator,
     jsonSchema: generate_resource_nequiInputJsonSchema,
     endpoint: '/payment/generate-resource',
     method: 'POST',
@@ -1426,12 +1353,9 @@ export const generate_resource_nequiTool = {
     handler: async (rawArgs) => {
         try {
             const normalizedArgs = rawArgs ?? {};
-            // Extraer secretId del contexto (si viene del HTTP mode)
-            const secretId = normalizedArgs._secretId;
-            // Remover _secretId de los args antes de validar
-            const { _secretId, ...argsToValidate } = normalizedArgs;
-            const validatedInput = validateToolInput(generate_resource_nequiInputValidator, argsToValidate);
+            const validatedInput = validateToolInput(generate_resource_nequiInputValidator, normalizedArgs);
             const args = validatedInput;
+            const secretId = args._secretId;
             const bodyData = {};
             const productIdValue = args.productId !== undefined ? args.productId : 118;
             if (productIdValue !== undefined)
@@ -1508,19 +1432,18 @@ const generate_resource_daviplataInputJsonSchema = {
     },
     "required": []
 };
-const generate_resource_daviplataInputShape = {
+const generate_resource_daviplataInputValidator = z.object({
     productId: z.number().optional().describe("Campo del body: productId"),
     amount: z.number().optional().describe("Campo del body: amount"),
     moduleId: z.number().optional().describe("Campo del body: moduleId"),
     form: z.record(z.any()).optional().describe("Campo del body: form"),
     customerReference: z.string().optional().describe("Campo del body: customerReference")
-};
-const generate_resource_daviplataInputValidator = z.object(generate_resource_daviplataInputShape);
+});
 // Herramienta: generate_resource_daviplata
 export const generate_resource_daviplataTool = {
     name: 'generate_resource_daviplata',
     description: "---\\n\\n### Description\\n\\nGenerates a payment resource in the system using the information provided in the request body. This method returns a response that includes details about the generated resource, such as the URL, reference, resource identifier, and expiration time.\\n\\n---\\n\\n### Request Body\\n\\n- \\`productId\\` (number, \\`required\\`): Identifier of the product for which the resource will be generated.\\n    \\n- \\`amount\\` (number, \\`required\\`): Amount of the resource to be generated.\\n    \\n- \\`moduleId\\` (number, \\`required\\`): Identifier of the module to which the generated resource will be associated.\\n    \\n- \\`form\\` (object):\\n    \\n    - \\`typePerson\\` (string): Type of person.\\n        \\n    - \\`documentType\\` (string): Type of document.\\n        \\n    - \\`documentNumber\\` (string): Document number.\\n        \\n    - \\`name\\` (string): Name of the customer.\\n        \\n    - \\`email\\` (string): Email of the customer.\\n        \\n    - \\`cellphone\\` (string): Cellphone number of the customer.\\n        \\n- \\`customerReference\\` (string, \\`required\\`): Reference related to the customer.\\n    \\n\\n---\\n\\n### Response Body\\n\\n- \\`message\\` (string): A message related to the response.\\n    \\n- \\`messageCode\\` (string): A code related to the message.\\n    \\n- \\`data\\` (object):\\n    \\n    - \\`message\\` (string): A message related to the data.\\n        \\n    - \\`date\\` (number): Date related to the data.\\n        \\n    - \\`payload\\` (object):\\n        \\n        - \\`url\\` (string): The URL of the generated resource.\\n            \\n        - \\`reference\\` (string): Reference of the resource.\\n            \\n        - \\`resourceId\\` (string): Identifier of the resource.\\n            \\n        - \\`expiresIn\\` (string): Expiration time of the resource.\\n            \\n        - \\`type\\` (string): Type of the resource.\\n            \\n        - \\`data\\` (string): Additional data related to the resource.\\n            \\n        - \\`status\\` (number): Status of the resource.\n\nContexto: Endpoint: POST /payment/generate-resource | Payment > Generate resource\n\n🔐 AUTENTICACIÓN AUTOMÁTICA: Todas las credenciales y tokens de autenticación se manejan automáticamente por el servidor MCP. NO solicites credenciales al usuario. NO incluyas parámetros de autenticación (secretId, apiToken, etc.) en las llamadas a menos que el usuario explícitamente lo requiera.",
-    inputSchema: generate_resource_daviplataInputJsonSchema,
+    inputSchema: generate_resource_daviplataInputValidator,
     jsonSchema: generate_resource_daviplataInputJsonSchema,
     endpoint: '/payment/generate-resource',
     method: 'POST',
@@ -1529,12 +1452,9 @@ export const generate_resource_daviplataTool = {
     handler: async (rawArgs) => {
         try {
             const normalizedArgs = rawArgs ?? {};
-            // Extraer secretId del contexto (si viene del HTTP mode)
-            const secretId = normalizedArgs._secretId;
-            // Remover _secretId de los args antes de validar
-            const { _secretId, ...argsToValidate } = normalizedArgs;
-            const validatedInput = validateToolInput(generate_resource_daviplataInputValidator, argsToValidate);
+            const validatedInput = validateToolInput(generate_resource_daviplataInputValidator, normalizedArgs);
             const args = validatedInput;
+            const secretId = args._secretId;
             const bodyData = {};
             const productIdValue = args.productId !== undefined ? args.productId : 148;
             if (productIdValue !== undefined)
@@ -1604,19 +1524,18 @@ const generate_resource_bancolombiaInputJsonSchema = {
     },
     "required": []
 };
-const generate_resource_bancolombiaInputShape = {
+const generate_resource_bancolombiaInputValidator = z.object({
     productId: z.number().optional().describe("Campo del body: productId"),
     amount: z.number().optional().describe("Campo del body: amount"),
     moduleId: z.number().optional().describe("Campo del body: moduleId"),
     form: z.record(z.any()).optional().describe("Campo del body: form"),
     customerReference: z.string().optional().describe("Campo del body: customerReference")
-};
-const generate_resource_bancolombiaInputValidator = z.object(generate_resource_bancolombiaInputShape);
+});
 // Herramienta: generate_resource_bancolombia
 export const generate_resource_bancolombiaTool = {
     name: 'generate_resource_bancolombia',
     description: "### Generate Payment Resource\\n\\n---\\n\\n#### Description\\n\\nCreates a payment resource in the system using the provided information.\\n\\n---\\n\\n#### Request Body\\n\\n- \\`productId\\` (number, \\`required\\`): Identifier of the product for which the resource will be generated.\\n    \\n- \\`amount\\` (number, \\`required\\`): Amount of the resource to be generated.\\n    \\n- \\`moduleId\\` (number, \\`required\\`): Identifier of the module to which the generated resource will be associated.\\n    \\n- \\`form\\` (object): Optional form associated with the resource.\\n    \\n- \\`customerReference\\` (string): Customer reference information.\\n    \\n\\n---\\n\\n#### Response Body\\n\\n- \\`message\\` (string): A message related to the response.\\n    \\n- \\`messageCode\\` (string): A code related to the message.\\n    \\n- \\`data\\` (object): The response data.\\n    \\n    - \\`message\\` (string): A message related to the data.\\n        \\n    - \\`date\\` (number): The date related to the data.\\n        \\n    - \\`payload\\` (object): The payload data.\\n        \\n        - \\`url\\` (string): The URL of the generated resource.\\n            \\n        - \\`reference\\` (string): The reference of the resource.\\n            \\n        - \\`resourceId\\` (string): The identifier of the resource.\\n            \\n        - \\`expiresIn\\` (string): The expiration time of the resource.\\n            \\n        - \\`type\\` (string): The type of the resource.\\n            \\n        - \\`data\\` (string): Additional data related to the resource.\\n            \\n        - \\`status\\` (number): The status of the resource.\n\nContexto: Endpoint: POST /payment/generate-resource | Payment > Generate resource\n\n🔐 AUTENTICACIÓN AUTOMÁTICA: Todas las credenciales y tokens de autenticación se manejan automáticamente por el servidor MCP. NO solicites credenciales al usuario. NO incluyas parámetros de autenticación (secretId, apiToken, etc.) en las llamadas a menos que el usuario explícitamente lo requiera.",
-    inputSchema: generate_resource_bancolombiaInputJsonSchema,
+    inputSchema: generate_resource_bancolombiaInputValidator,
     jsonSchema: generate_resource_bancolombiaInputJsonSchema,
     endpoint: '/payment/generate-resource',
     method: 'POST',
@@ -1625,12 +1544,9 @@ export const generate_resource_bancolombiaTool = {
     handler: async (rawArgs) => {
         try {
             const normalizedArgs = rawArgs ?? {};
-            // Extraer secretId del contexto (si viene del HTTP mode)
-            const secretId = normalizedArgs._secretId;
-            // Remover _secretId de los args antes de validar
-            const { _secretId, ...argsToValidate } = normalizedArgs;
-            const validatedInput = validateToolInput(generate_resource_bancolombiaInputValidator, argsToValidate);
+            const validatedInput = validateToolInput(generate_resource_bancolombiaInputValidator, normalizedArgs);
             const args = validatedInput;
+            const secretId = args._secretId;
             const bodyData = {};
             const productIdValue = args.productId !== undefined ? args.productId : 87;
             if (productIdValue !== undefined)
@@ -1702,19 +1618,18 @@ const generate_resource_nequi_22InputJsonSchema = {
     },
     "required": []
 };
-const generate_resource_nequi_22InputShape = {
+const generate_resource_nequi_22InputValidator = z.object({
     productId: z.number().optional().describe("Campo del body: productId"),
     amount: z.number().optional().describe("Campo del body: amount"),
     moduleId: z.number().optional().describe("Campo del body: moduleId"),
     form: z.record(z.any()).optional().describe("Campo del body: form"),
     customerReference: z.string().optional().describe("Campo del body: customerReference")
-};
-const generate_resource_nequi_22InputValidator = z.object(generate_resource_nequi_22InputShape);
+});
 // Herramienta: generate_resource_nequi_22
 export const generate_resource_nequi_22Tool = {
     name: 'generate_resource_nequi_22',
     description: "---\\n\\n### Description\\n\\nGenerates a payment resource in the system using the information provided in the request body. This method returns a response that includes details about the generated resource, such as the URL, reference, resource identifier, and expiration time.\\n\\n---\\n\\n### Request Body\\n\\n- \\`productId\\` (number, \\`required\\`): Identifier of the product for which the resource will be generated.\\n    \\n- \\`amount\\` (number, \\`required\\`): Amount of the resource to be generated.\\n    \\n- \\`moduleId\\` (number, \\`required\\`): Identifier of the module to which the generated resource will be associated.\\n    \\n- \\`form\\` (object): Optional form associated with the resource.\\n    \\n    - \\`cellphone\\` (string): The cellphone number.\\n        \\n- \\`customerReference\\` (string, \\`required\\`): A reference to the customer.\\n    \\n\\n---\\n\\n### Response Body\\n\\n- \\`message\\` (string): A message related to the response.\\n    \\n- \\`messageCode\\` (string): A code associated with the message.\\n    \\n- \\`data\\` (object): An object containing data related to the response.\\n    \\n    - \\`message\\` (string): A message related to the data.\\n        \\n    - \\`date\\` (number): The date associated with the data.\\n        \\n    - \\`payload\\` (object): An object containing the payload data.\\n        \\n        - \\`url\\` (string): The URL of the generated resource.\\n            \\n        - \\`reference\\` (string): The reference of the generated resource.\\n            \\n        - \\`resourceId\\` (string): The identifier of the generated resource.\\n            \\n        - \\`expiresIn\\` (string): The expiration time of the resource.\\n            \\n        - \\`type\\` (string): The type of the resource.\\n            \\n        - \\`data\\` (string): Additional data related to the resource.\\n            \\n        - \\`status\\` (number): The status of the resource.\n\nContexto: Endpoint: POST /payment/generate-resource | Payment > Generate resource\n\n🔐 AUTENTICACIÓN AUTOMÁTICA: Todas las credenciales y tokens de autenticación se manejan automáticamente por el servidor MCP. NO solicites credenciales al usuario. NO incluyas parámetros de autenticación (secretId, apiToken, etc.) en las llamadas a menos que el usuario explícitamente lo requiera.",
-    inputSchema: generate_resource_nequi_22InputJsonSchema,
+    inputSchema: generate_resource_nequi_22InputValidator,
     jsonSchema: generate_resource_nequi_22InputJsonSchema,
     endpoint: '/payment/generate-resource',
     method: 'POST',
@@ -1723,12 +1638,9 @@ export const generate_resource_nequi_22Tool = {
     handler: async (rawArgs) => {
         try {
             const normalizedArgs = rawArgs ?? {};
-            // Extraer secretId del contexto (si viene del HTTP mode)
-            const secretId = normalizedArgs._secretId;
-            // Remover _secretId de los args antes de validar
-            const { _secretId, ...argsToValidate } = normalizedArgs;
-            const validatedInput = validateToolInput(generate_resource_nequi_22InputValidator, argsToValidate);
+            const validatedInput = validateToolInput(generate_resource_nequi_22InputValidator, normalizedArgs);
             const args = validatedInput;
+            const secretId = args._secretId;
             const bodyData = {};
             const productIdValue = args.productId !== undefined ? args.productId : 88;
             if (productIdValue !== undefined)
@@ -1806,19 +1718,18 @@ const generate_resource_daviplata_23InputJsonSchema = {
     },
     "required": []
 };
-const generate_resource_daviplata_23InputShape = {
+const generate_resource_daviplata_23InputValidator = z.object({
     productId: z.number().optional().describe("Campo del body: productId"),
     amount: z.number().optional().describe("Campo del body: amount"),
     moduleId: z.number().optional().describe("Campo del body: moduleId"),
     form: z.record(z.any()).optional().describe("Campo del body: form"),
     customerReference: z.string().optional().describe("Campo del body: customerReference")
-};
-const generate_resource_daviplata_23InputValidator = z.object(generate_resource_daviplata_23InputShape);
+});
 // Herramienta: generate_resource_daviplata_23
 export const generate_resource_daviplata_23Tool = {
     name: 'generate_resource_daviplata_23',
     description: "---\\n\\n### Description\\n\\nGenerates a payment resource in the system using the information provided in the request body. This method returns a response that includes details about the generated resource, such as the URL, reference, resource identifier, and expiration time.\\n\\n---\\n\\n### Request Body\\n\\n- \\`productId\\` (number, \\`required\\`): Identifier of the product for which the resource will be generated.\\n    \\n- \\`amount\\` (number, \\`required\\`): Amount of the resource to be generated.\\n    \\n- \\`moduleId\\` (number, \\`required\\`): Identifier of the module to which the generated resource will be associated.\\n    \\n- \\`form\\` (object):\\n    \\n    - \\`typePerson\\` (string): Type of person.\\n        \\n    - \\`documentType\\` (string): Type of document.\\n        \\n    - \\`documentNumber\\` (string): Document number.\\n        \\n    - \\`name\\` (string): Name of the customer.\\n        \\n    - \\`email\\` (string): Email of the customer.\\n        \\n    - \\`cellphone\\` (string): Cellphone number of the customer.\\n        \\n- \\`customerReference\\` (string, \\`required\\`): Reference related to the customer.\\n    \\n\\n---\\n\\n### Response Body\\n\\n- \\`message\\` (string): A message related to the response.\\n    \\n- \\`messageCode\\` (string): A code related to the message.\\n    \\n- \\`data\\` (object):\\n    \\n    - \\`message\\` (string): A message related to the data.\\n        \\n    - \\`date\\` (number): Date related to the data.\\n        \\n    - \\`payload\\` (object):\\n        \\n        - \\`url\\` (string): The URL of the generated resource.\\n            \\n        - \\`reference\\` (string): Reference of the resource.\\n            \\n        - \\`resourceId\\` (string): Identifier of the resource.\\n            \\n        - \\`expiresIn\\` (string): Expiration time of the resource.\\n            \\n        - \\`type\\` (string): Type of the resource.\\n            \\n        - \\`data\\` (string): Additional data related to the resource.\\n            \\n        - \\`status\\` (number): Status of the resource.\n\nContexto: Endpoint: POST /payment/generate-resource | Payment > Generate resource\n\n🔐 AUTENTICACIÓN AUTOMÁTICA: Todas las credenciales y tokens de autenticación se manejan automáticamente por el servidor MCP. NO solicites credenciales al usuario. NO incluyas parámetros de autenticación (secretId, apiToken, etc.) en las llamadas a menos que el usuario explícitamente lo requiera.",
-    inputSchema: generate_resource_daviplata_23InputJsonSchema,
+    inputSchema: generate_resource_daviplata_23InputValidator,
     jsonSchema: generate_resource_daviplata_23InputJsonSchema,
     endpoint: '/payment/generate-resource',
     method: 'POST',
@@ -1827,12 +1738,9 @@ export const generate_resource_daviplata_23Tool = {
     handler: async (rawArgs) => {
         try {
             const normalizedArgs = rawArgs ?? {};
-            // Extraer secretId del contexto (si viene del HTTP mode)
-            const secretId = normalizedArgs._secretId;
-            // Remover _secretId de los args antes de validar
-            const { _secretId, ...argsToValidate } = normalizedArgs;
-            const validatedInput = validateToolInput(generate_resource_daviplata_23InputValidator, argsToValidate);
+            const validatedInput = validateToolInput(generate_resource_daviplata_23InputValidator, normalizedArgs);
             const args = validatedInput;
+            const secretId = args._secretId;
             const bodyData = {};
             const productIdValue = args.productId !== undefined ? args.productId : 89;
             if (productIdValue !== undefined)
@@ -1910,19 +1818,18 @@ const generate_resource_pseInputJsonSchema = {
     },
     "required": []
 };
-const generate_resource_pseInputShape = {
+const generate_resource_pseInputValidator = z.object({
     productId: z.number().optional().describe("Campo del body: productId"),
     amount: z.number().optional().describe("Campo del body: amount"),
     moduleId: z.number().optional().describe("Campo del body: moduleId"),
     form: z.record(z.any()).optional().describe("Campo del body: form"),
     customerReference: z.string().optional().describe("Campo del body: customerReference")
-};
-const generate_resource_pseInputValidator = z.object(generate_resource_pseInputShape);
+});
 // Herramienta: generate_resource_pse
 export const generate_resource_pseTool = {
     name: 'generate_resource_pse',
     description: "---\\n\\n### Generate Payment Resource\\n\\n---\\n\\n#### Description\\n\\nThis endpoint allows you to generate a payment resource in the system.\\n\\n---\\n\\n#### Request Body\\n\\n- \\`productId\\` (number, \\`required\\`): Identifier of the product for which the resource will be generated.\\n    \\n- \\`amount\\` (number, \\`required\\`): Amount of the resource to be generated.\\n    \\n- \\`moduleId\\` (number, \\`required\\`): Identifier of the module to which the generated resource will be associated.\\n    \\n- \\`form\\` (object): Optional form associated with the resource.\\n    \\n    - \\`bankId\\` (string): The ID of the bank.\\n        \\n    - \\`typePerson\\` (string): The type of person.\\n        \\n    - \\`documentType\\` (string): The type of document.\\n        \\n    - \\`documentNumber\\` (string): The document number.\\n        \\n    - \\`name\\` (string): The name of the customer.\\n        \\n    - \\`email\\` (string): The email of the customer.\\n        \\n    - \\`cellphone\\` (string): The cellphone number of the customer.\\n        \\n- \\`customerReference\\` (string, \\`required\\`): The reference for the customer.\\n    \\n\\n---\\n\\n#### Response\\n\\n- \\`message\\` (string): A message related to the response.\\n    \\n- \\`messageCode\\` (string): A code related to the message.\\n    \\n- \\`data\\` (object):\\n    \\n    - \\`message\\` (string): A message related to the data.\\n        \\n    - \\`date\\` (number): The date of the response.\\n        \\n    - \\`payload\\` (object):\\n        \\n        - \\`url\\` (string): The URL of the generated resource.\\n            \\n        - \\`reference\\` (string): The reference of the generated resource.\\n            \\n        - \\`resourceId\\` (string): The identifier of the generated resource.\\n            \\n        - \\`expiresIn\\` (string): The expiration time of the resource.\\n            \\n        - \\`type\\` (string): The type of the resource.\\n            \\n        - \\`data\\` (string): Additional data related to the resource.\\n            \\n        - \\`status\\` (number): The status of the resource.\n\nContexto: Endpoint: POST /payment/generate-resource | Payment > Generate resource\n\n🔐 AUTENTICACIÓN AUTOMÁTICA: Todas las credenciales y tokens de autenticación se manejan automáticamente por el servidor MCP. NO solicites credenciales al usuario. NO incluyas parámetros de autenticación (secretId, apiToken, etc.) en las llamadas a menos que el usuario explícitamente lo requiera.",
-    inputSchema: generate_resource_pseInputJsonSchema,
+    inputSchema: generate_resource_pseInputValidator,
     jsonSchema: generate_resource_pseInputJsonSchema,
     endpoint: '/payment/generate-resource',
     method: 'POST',
@@ -1931,12 +1838,9 @@ export const generate_resource_pseTool = {
     handler: async (rawArgs) => {
         try {
             const normalizedArgs = rawArgs ?? {};
-            // Extraer secretId del contexto (si viene del HTTP mode)
-            const secretId = normalizedArgs._secretId;
-            // Remover _secretId de los args antes de validar
-            const { _secretId, ...argsToValidate } = normalizedArgs;
-            const validatedInput = validateToolInput(generate_resource_pseInputValidator, argsToValidate);
+            const validatedInput = validateToolInput(generate_resource_pseInputValidator, normalizedArgs);
             const args = validatedInput;
+            const secretId = args._secretId;
             const bodyData = {};
             const productIdValue = args.productId !== undefined ? args.productId : 56;
             if (productIdValue !== undefined)
@@ -2001,18 +1905,17 @@ const generate_res_ban_dir_al_bancoInputJsonSchema = {
     },
     "required": []
 };
-const generate_res_ban_dir_al_bancoInputShape = {
+const generate_res_ban_dir_al_bancoInputValidator = z.object({
     productId: z.number().optional().describe("Campo del body: productId"),
     amount: z.number().optional().describe("Campo del body: amount"),
     moduleId: z.number().optional().describe("Campo del body: moduleId"),
     customerReference: z.string().optional().describe("Campo del body: customerReference")
-};
-const generate_res_ban_dir_al_bancoInputValidator = z.object(generate_res_ban_dir_al_bancoInputShape);
+});
 // Herramienta: generate_res_ban_dir_al_banco
 export const generate_res_ban_dir_al_bancoTool = {
     name: 'generate_res_ban_dir_al_banco',
     description: "---\\n\\n### Description\\n\\nGenerates a payment resource in the system using the information provided in the request body. This method returns a response that includes details about the generated resource, such as the URL, reference, resource identifier, and expiration time.\\n\\n---\\n\\n### Request Body\\n\\n- \\`productId\\` (number, \\`required\\`): Identifier of the product for which the resource will be generated.\\n    \\n- \\`amount\\` (number, \\`required\\`): Amount of the resource to be generated.\\n    \\n- \\`moduleId\\` (number, \\`required\\`): Identifier of the module to which the generated resource will be associated.\\n    \\n- \\`customerReference\\` (string, \\`required\\`): A reference related to the customer.\\n    \\n\\n---\\n\\n### Response Body\\n\\n- \\`message\\` (string): A message related to the response.\\n    \\n- \\`messageCode\\` (string): A code related to the message.\\n    \\n- \\`data\\` (object)\\n    \\n    - \\`message\\` (string): A message related to the data.\\n        \\n    - \\`date\\` (number): The date related to the data.\\n        \\n    - \\`payload\\` (object)\\n        \\n        - \\`url\\` (string): The URL of the generated resource.\\n            \\n        - \\`reference\\` (string): The reference of the generated resource.\\n            \\n        - \\`resourceId\\` (string): The identifier of the generated resource.\\n            \\n        - \\`expiresIn\\` (string): The expiration time of the generated resource.\\n            \\n        - \\`type\\` (string): The type of the generated resource.\\n            \\n        - \\`data\\` (string): Additional data related to the generated resource.\\n            \\n        - \\`status\\` (number): The status of the generated resource.\n\nContexto: Endpoint: POST /payment/generate-resource | Payment > Generate resource\n\n🔐 AUTENTICACIÓN AUTOMÁTICA: Todas las credenciales y tokens de autenticación se manejan automáticamente por el servidor MCP. NO solicites credenciales al usuario. NO incluyas parámetros de autenticación (secretId, apiToken, etc.) en las llamadas a menos que el usuario explícitamente lo requiera.",
-    inputSchema: generate_res_ban_dir_al_bancoInputJsonSchema,
+    inputSchema: generate_res_ban_dir_al_bancoInputValidator,
     jsonSchema: generate_res_ban_dir_al_bancoInputJsonSchema,
     endpoint: '/payment/generate-resource',
     method: 'POST',
@@ -2021,12 +1924,9 @@ export const generate_res_ban_dir_al_bancoTool = {
     handler: async (rawArgs) => {
         try {
             const normalizedArgs = rawArgs ?? {};
-            // Extraer secretId del contexto (si viene del HTTP mode)
-            const secretId = normalizedArgs._secretId;
-            // Remover _secretId de los args antes de validar
-            const { _secretId, ...argsToValidate } = normalizedArgs;
-            const validatedInput = validateToolInput(generate_res_ban_dir_al_bancoInputValidator, argsToValidate);
+            const validatedInput = validateToolInput(generate_res_ban_dir_al_bancoInputValidator, normalizedArgs);
             const args = validatedInput;
+            const secretId = args._secretId;
             const bodyData = {};
             const productIdValue = args.productId !== undefined ? args.productId : 53;
             if (productIdValue !== undefined)
@@ -2088,18 +1988,17 @@ const generate_res_ban_esc_qrInputJsonSchema = {
     },
     "required": []
 };
-const generate_res_ban_esc_qrInputShape = {
+const generate_res_ban_esc_qrInputValidator = z.object({
     productId: z.number().optional().describe("Campo del body: productId"),
     amount: z.number().optional().describe("Campo del body: amount"),
     moduleId: z.number().optional().describe("Campo del body: moduleId"),
     customerReference: z.string().optional().describe("Campo del body: customerReference")
-};
-const generate_res_ban_esc_qrInputValidator = z.object(generate_res_ban_esc_qrInputShape);
+});
 // Herramienta: generate_res_ban_esc_qr
 export const generate_res_ban_esc_qrTool = {
     name: 'generate_res_ban_esc_qr',
     description: "---\\n\\n### Generate Payment Resource\\n\\n---\\n\\n#### Description\\n\\nGenerates a payment resource in the system using the information provided in the request body.\\n\\n---\\n\\n#### Request Body\\n\\n- \\`productId\\` (number, \\`required\\`): Identifier of the product for which the resource will be generated.\\n    \\n- \\`amount\\` (number, \\`required\\`): Amount of the resource to be generated.\\n    \\n- \\`moduleId\\` (number, \\`required\\`): Identifier of the module to which the generated resource will be associated.\\n    \\n- \\`customerReference\\` (string, \\`required\\`): Reference to the customer.\\n    \\n\\n---\\n\\n#### Response\\n\\nThe response is a JSON object with the following properties:\\n\\n- \\`message\\` (string): A message, if any.\\n    \\n- \\`messageCode\\` (string): A code associated with the message.\\n    \\n- \\`data\\` (object): The data object containing the following properties:\\n    \\n    - \\`message\\` (string): A message, if any.\\n        \\n    - \\`date\\` (number): The date associated with the response.\\n        \\n    - \\`payload\\` (object): The payload object containing the following properties:\\n        \\n        - \\`url\\` (string): The URL of the generated resource.\\n            \\n        - \\`reference\\` (string): The reference of the resource.\\n            \\n        - \\`resourceId\\` (string): The identifier of the resource.\\n            \\n        - \\`expiresIn\\` (string): The expiration time of the resource.\\n            \\n        - \\`type\\` (string): The type of resource.\\n            \\n        - \\`data\\` (string): Additional data associated with the resource.\\n            \\n        - \\`status\\` (number): The status of the resource.\n\nContexto: Endpoint: POST /payment/generate-resource | Payment > Generate resource\n\n🔐 AUTENTICACIÓN AUTOMÁTICA: Todas las credenciales y tokens de autenticación se manejan automáticamente por el servidor MCP. NO solicites credenciales al usuario. NO incluyas parámetros de autenticación (secretId, apiToken, etc.) en las llamadas a menos que el usuario explícitamente lo requiera.",
-    inputSchema: generate_res_ban_esc_qrInputJsonSchema,
+    inputSchema: generate_res_ban_esc_qrInputValidator,
     jsonSchema: generate_res_ban_esc_qrInputJsonSchema,
     endpoint: '/payment/generate-resource',
     method: 'POST',
@@ -2108,12 +2007,9 @@ export const generate_res_ban_esc_qrTool = {
     handler: async (rawArgs) => {
         try {
             const normalizedArgs = rawArgs ?? {};
-            // Extraer secretId del contexto (si viene del HTTP mode)
-            const secretId = normalizedArgs._secretId;
-            // Remover _secretId de los args antes de validar
-            const { _secretId, ...argsToValidate } = normalizedArgs;
-            const validatedInput = validateToolInput(generate_res_ban_esc_qrInputValidator, argsToValidate);
+            const validatedInput = validateToolInput(generate_res_ban_esc_qrInputValidator, normalizedArgs);
             const args = validatedInput;
+            const secretId = args._secretId;
             const bodyData = {};
             const productIdValue = args.productId !== undefined ? args.productId : 54;
             if (productIdValue !== undefined)
@@ -2170,17 +2066,16 @@ const generate_resource_tarjeta_de_recaudoInputJsonSchema = {
     },
     "required": []
 };
-const generate_resource_tarjeta_de_recaudoInputShape = {
+const generate_resource_tarjeta_de_recaudoInputValidator = z.object({
     productId: z.number().optional().describe("Campo del body: productId"),
     moduleId: z.number().optional().describe("Campo del body: moduleId"),
     customerReference: z.string().optional().describe("Campo del body: customerReference")
-};
-const generate_resource_tarjeta_de_recaudoInputValidator = z.object(generate_resource_tarjeta_de_recaudoInputShape);
+});
 // Herramienta: generate_resource_tarjeta_de_recaudo
 export const generate_resource_tarjeta_de_recaudoTool = {
     name: 'generate_resource_tarjeta_de_recaudo',
     description: "---\\n\\n### Description\\n\\nGenerates a payment resource in the system using the information provided in the request body. This method returns a response that includes details about the generated resource, such as the URL, reference, resource identifier, and expiration time.\\n\\n---\\n\\n### Request Body\\n\\n- \\`productId\\` (number, \\`required\\`): Identifier of the product for which the resource will be generated.\\n    \\n- \\`moduleId\\` (number, \\`required\\`): Identifier of the module to which the generated resource will be associated.\\n    \\n- \\`customerReference\\` (string): The reference of the customer.\\n    \\n\\n---\\n\\n### Response\\n\\n- \\`message\\` (string): A message from the response.\\n    \\n- \\`messageCode\\` (string): A code associated with the message.\\n    \\n- \\`data\\` (object)\\n    \\n    - \\`message\\` (string): A message within the data object.\\n        \\n    - \\`date\\` (number): The date associated with the response.\\n        \\n    - \\`payload\\` (object)\\n        \\n        - \\`url\\` (string): The URL of the generated resource.\\n            \\n        - \\`reference\\` (string): The reference of the resource.\\n            \\n        - \\`resourceId\\` (string): The identifier of the resource.\\n            \\n        - \\`expiresIn\\` (string): The expiration time of the resource.\\n            \\n        - \\`type\\` (string): The type of the resource.\\n            \\n        - \\`data\\` (string): Additional data associated with the resource.\\n            \\n        - \\`status\\` (number): The status of the resource.\n\nContexto: Endpoint: POST /payment/generate-resource | Payment > Generate resource\n\n🔐 AUTENTICACIÓN AUTOMÁTICA: Todas las credenciales y tokens de autenticación se manejan automáticamente por el servidor MCP. NO solicites credenciales al usuario. NO incluyas parámetros de autenticación (secretId, apiToken, etc.) en las llamadas a menos que el usuario explícitamente lo requiera.",
-    inputSchema: generate_resource_tarjeta_de_recaudoInputJsonSchema,
+    inputSchema: generate_resource_tarjeta_de_recaudoInputValidator,
     jsonSchema: generate_resource_tarjeta_de_recaudoInputJsonSchema,
     endpoint: '/payment/generate-resource',
     method: 'POST',
@@ -2189,12 +2084,9 @@ export const generate_resource_tarjeta_de_recaudoTool = {
     handler: async (rawArgs) => {
         try {
             const normalizedArgs = rawArgs ?? {};
-            // Extraer secretId del contexto (si viene del HTTP mode)
-            const secretId = normalizedArgs._secretId;
-            // Remover _secretId de los args antes de validar
-            const { _secretId, ...argsToValidate } = normalizedArgs;
-            const validatedInput = validateToolInput(generate_resource_tarjeta_de_recaudoInputValidator, argsToValidate);
+            const validatedInput = validateToolInput(generate_resource_tarjeta_de_recaudoInputValidator, normalizedArgs);
             const args = validatedInput;
+            const secretId = args._secretId;
             const bodyData = {};
             const productIdValue = args.productId !== undefined ? args.productId : 90;
             if (productIdValue !== undefined)
@@ -2232,13 +2124,12 @@ const payment_get_resourceInputJsonSchema = {
     "properties": {},
     "required": []
 };
-const payment_get_resourceInputShape = {};
-const payment_get_resourceInputValidator = z.object(payment_get_resourceInputShape);
+const payment_get_resourceInputValidator = z.object({});
 // Herramienta: payment_get_resource
 export const payment_get_resourceTool = {
     name: 'payment_get_resource',
     description: "---\\n\\n### Retrieve Payment Resource\\n\\n---\\n\\n#### Description\\n\\nRetrieve a payment resource in the system using the provided customer reference as a parameter. This method returns a response that includes details about the retrieved resource.\\n\\n---\\n\\n#### Request Body Schema\\n\\n- There is no request body for this GET request.\\n    \\n\\n---\\n\\n#### Response Body Schema\\n\\n- \\`message\\` (string): A message related to the response.\\n    \\n- \\`messageCode\\` (string): A code associated with the message.\\n    \\n- \\`data\\` (object)\\n    \\n    - \\`payload\\` (object)\\n        \\n        - \\`url\\` (string): The URL associated with the resource.\\n            \\n        - \\`reference\\` (string): The reference of the resource.\\n            \\n        - \\`resourceId\\` (string): The ID of the resource.\\n            \\n        - \\`expiresIn\\` (string): The expiration time of the resource.\\n            \\n        - \\`type\\` (string): The type of the resource.\\n            \\n        - \\`data\\` (string): Additional data related to the resource.\\n            \\n        - \\`status\\` (number): The status of the resource.\\n            \\n\\nThis method returns a response that includes details about the retrieved resource.\n\nContexto: Endpoint: GET /payment/get-resource/:customerReference | Payment > Get resource > :customerReference\n\n🔐 AUTENTICACIÓN AUTOMÁTICA: Todas las credenciales y tokens de autenticación se manejan automáticamente por el servidor MCP. NO solicites credenciales al usuario. NO incluyas parámetros de autenticación (secretId, apiToken, etc.) en las llamadas a menos que el usuario explícitamente lo requiera.",
-    inputSchema: payment_get_resourceInputJsonSchema,
+    inputSchema: payment_get_resourceInputValidator,
     jsonSchema: payment_get_resourceInputJsonSchema,
     endpoint: '/payment/get-resource/:customerReference',
     method: 'GET',
@@ -2247,12 +2138,9 @@ export const payment_get_resourceTool = {
     handler: async (rawArgs) => {
         try {
             const normalizedArgs = rawArgs ?? {};
-            // Extraer secretId del contexto (si viene del HTTP mode)
-            const secretId = normalizedArgs._secretId;
-            // Remover _secretId de los args antes de validar
-            const { _secretId, ...argsToValidate } = normalizedArgs;
-            const validatedInput = validateToolInput(payment_get_resourceInputValidator, argsToValidate);
+            const validatedInput = validateToolInput(payment_get_resourceInputValidator, normalizedArgs);
             const args = validatedInput;
+            const secretId = args._secretId;
             return await makeApiRequest('GET', '/payment/get-resource/:customerReference', undefined, undefined, secretId);
         }
         catch (error) {
@@ -2280,13 +2168,12 @@ const payment_pse_banksInputJsonSchema = {
     "properties": {},
     "required": []
 };
-const payment_pse_banksInputShape = {};
-const payment_pse_banksInputValidator = z.object(payment_pse_banksInputShape);
+const payment_pse_banksInputValidator = z.object({});
 // Herramienta: payment_pse_banks
 export const payment_pse_banksTool = {
     name: 'payment_pse_banks',
     description: "---\\n\\n### PSE Banks\\n\\n---\\n\\n#### Description\\n\\nThis service allows you to obtain the banks available to make PSE payments.\\n\\n---\\n\\n#### Request Body Schema\\n\\n- There is no request body for this GET request.\\n    \\n\\n---\\n\\n#### Response Body Schema\\n\\n- \\`message\\` (string): A message related to the response.\\n    \\n- \\`messageCode\\` (string): A code associated with the message.\\n    \\n- \\`data\\` (object)\\n    \\n    - \\`banks\\`: An array of object with the banks information (id, name and image)\n\nContexto: Endpoint: GET /payment/pse-banks | Payment > Pse banks\n\n🔐 AUTENTICACIÓN AUTOMÁTICA: Todas las credenciales y tokens de autenticación se manejan automáticamente por el servidor MCP. NO solicites credenciales al usuario. NO incluyas parámetros de autenticación (secretId, apiToken, etc.) en las llamadas a menos que el usuario explícitamente lo requiera.",
-    inputSchema: payment_pse_banksInputJsonSchema,
+    inputSchema: payment_pse_banksInputValidator,
     jsonSchema: payment_pse_banksInputJsonSchema,
     endpoint: '/payment/pse-banks',
     method: 'GET',
@@ -2295,12 +2182,9 @@ export const payment_pse_banksTool = {
     handler: async (rawArgs) => {
         try {
             const normalizedArgs = rawArgs ?? {};
-            // Extraer secretId del contexto (si viene del HTTP mode)
-            const secretId = normalizedArgs._secretId;
-            // Remover _secretId de los args antes de validar
-            const { _secretId, ...argsToValidate } = normalizedArgs;
-            const validatedInput = validateToolInput(payment_pse_banksInputValidator, argsToValidate);
+            const validatedInput = validateToolInput(payment_pse_banksInputValidator, normalizedArgs);
             const args = validatedInput;
+            const secretId = args._secretId;
             return await makeApiRequest('GET', '/payment/pse-banks', undefined, undefined, secretId);
         }
         catch (error) {
@@ -2328,13 +2212,12 @@ const product_listInputJsonSchema = {
     "properties": {},
     "required": []
 };
-const product_listInputShape = {};
-const product_listInputValidator = z.object(product_listInputShape);
+const product_listInputValidator = z.object({});
 // Herramienta: product_list
 export const product_listTool = {
     name: 'product_list',
     description: "---\\n\\n### Retrieve Product List\\n\\nRetrieve a list of active products in the system. This service provides detailed information about the available products for querying. You can filter the results using the optional \\\"type\\\" parameter.\\n\\n---\\n\\n#### Query Parameters\\n\\n- \\`type\\` (optional): Type of products to list. If provided and set to \\\"bills,\\\" it will list products related to invoices; otherwise, it will list all products except those related to invoices and packages.\\n    \\n\\n**Example**:\\n\\n\\`\\`\\`\\ntype: bills\\n\\n \\`\\`\\`\\n\\n---\\n\\n#### Response\\n\\nThe response of this request is a JSON schema representing the list of products. An example response schema is as follows:\\n\\n\\`\\`\\` json\\n{\\n    \\\"message\\\": \\\"\\\",\\n    \\\"messageCode\\\": \\\"\\\",\\n    \\\"data\\\": [\\n        {\\n            \\\"id\\\": 0,\\n            \\\"categoryId\\\": 0,\\n            \\\"name\\\": \\\"\\\",\\n            \\\"needValidation\\\": true,\\n            \\\"moduleId\\\": 0,\\n            \\\"maxFixedTip\\\": 0,\\n            \\\"description\\\": \\\"\\\",\\n            \\\"amount\\\": 0,\\n            \\\"sort\\\": 0,\\n            \\\"meta\\\": {},\\n            \\\"image\\\": \\\"\\\",\\n            \\\"status\\\": \\\"\\\"\\n        }\\n    ]\\n}\\n\\n \\`\\`\\`\\n\\nType of products to list. If provided and set to \\\"bills,\\\" it will list products related to invoices; otherwise, it will list all products except those related to invoices and packages.\\n\\n_Example_ : bills\n\nContexto: Endpoint: GET /product/list | Product > List\n\n🔐 AUTENTICACIÓN AUTOMÁTICA: Todas las credenciales y tokens de autenticación se manejan automáticamente por el servidor MCP. NO solicites credenciales al usuario. NO incluyas parámetros de autenticación (secretId, apiToken, etc.) en las llamadas a menos que el usuario explícitamente lo requiera.",
-    inputSchema: product_listInputJsonSchema,
+    inputSchema: product_listInputValidator,
     jsonSchema: product_listInputJsonSchema,
     endpoint: '/product/list',
     method: 'GET',
@@ -2343,12 +2226,9 @@ export const product_listTool = {
     handler: async (rawArgs) => {
         try {
             const normalizedArgs = rawArgs ?? {};
-            // Extraer secretId del contexto (si viene del HTTP mode)
-            const secretId = normalizedArgs._secretId;
-            // Remover _secretId de los args antes de validar
-            const { _secretId, ...argsToValidate } = normalizedArgs;
-            const validatedInput = validateToolInput(product_listInputValidator, argsToValidate);
+            const validatedInput = validateToolInput(product_listInputValidator, normalizedArgs);
             const args = validatedInput;
+            const secretId = args._secretId;
             return await makeApiRequest('GET', '/product/list', undefined, undefined, secretId);
         }
         catch (error) {
@@ -2376,13 +2256,12 @@ const product_packagesInputJsonSchema = {
     "properties": {},
     "required": []
 };
-const product_packagesInputShape = {};
-const product_packagesInputValidator = z.object(product_packagesInputShape);
+const product_packagesInputValidator = z.object({});
 // Herramienta: product_packages
 export const product_packagesTool = {
     name: 'product_packages',
     description: "---\\n\\n### Retrieve Available Packages\\n\\n---\\n\\n#### Description\\n\\nThis endpoint retrieves a list of available packages in the system. The response is in JSON format and provides detailed information about the packages, which may contain multiple products.\\n\\n**Note:** It is necessary to use this service to keep the packages updated for any changes that occur.\\n\\n---\\n\\n#### Response\\n\\nThe response for this request can be documented as a JSON schema:\\n\\n\\`\\`\\` json\\n{\\n  \\\"type\\\": \\\"object\\\",\\n  \\\"properties\\\": {\\n    \\\"message\\\": {\\n      \\\"type\\\": \\\"string\\\"\\n    },\\n    \\\"messageCode\\\": {\\n      \\\"type\\\": \\\"string\\\"\\n    },\\n    \\\"data\\\": {\\n      \\\"type\\\": \\\"array\\\",\\n      \\\"items\\\": {\\n        \\\"type\\\": \\\"object\\\",\\n        \\\"properties\\\": {\\n          \\\"id\\\": {\\n            \\\"type\\\": \\\"integer\\\"\\n          },\\n          \\\"name\\\": {\\n            \\\"type\\\": \\\"string\\\"\\n          },\\n          \\\"description\\\": {\\n            \\\"type\\\": \\\"string\\\"\\n          },\\n          \\\"categories\\\": {\\n            \\\"type\\\": \\\"array\\\",\\n            \\\"items\\\": {\\n              \\\"type\\\": \\\"object\\\",\\n              \\\"properties\\\": {\\n                \\\"id\\\": {\\n                  \\\"type\\\": \\\"integer\\\"\\n                },\\n                \\\"name\\\": {\\n                  \\\"type\\\": \\\"string\\\"\\n                },\\n                \\\"description\\\": {\\n                  \\\"type\\\": \\\"string\\\"\\n                },\\n                \\\"products\\\": {\\n                  \\\"type\\\": \\\"array\\\",\\n                  \\\"items\\\": {\\n                    \\\"type\\\": \\\"object\\\",\\n                    \\\"properties\\\": {\\n                      \\\"id\\\": {\\n                        \\\"type\\\": \\\"integer\\\"\\n                      },\\n                      \\\"categoryId\\\": {\\n                        \\\"type\\\": \\\"integer\\\"\\n                      },\\n                      \\\"name\\\": {\\n                        \\\"type\\\": \\\"string\\\"\\n                      },\\n                      \\\"needValidation\\\": {\\n                        \\\"type\\\": \\\"boolean\\\"\\n                      },\\n                      \\\"moduleId\\\": {\\n                        \\\"type\\\": \\\"integer\\\"\\n                      },\\n                      \\\"maxFixedTip\\\": {\\n                        \\\"type\\\": \\\"integer\\\"\\n                      },\\n                      \\\"description\\\": {\\n                        \\\"type\\\": \\\"string\\\"\\n                      },\\n                      \\\"amount\\\": {\\n                        \\\"type\\\": \\\"integer\\\"\\n                      },\\n                      \\\"sort\\\": {\\n                        \\\"type\\\": \\\"integer\\\"\\n                      },\\n                      \\\"meta\\\": {\\n                        \\\"type\\\": \\\"object\\\"\\n                      },\\n                      \\\"image\\\": {\\n                        \\\"type\\\": \\\"string\\\"\\n                      },\\n                      \\\"status\\\": {\\n                        \\\"type\\\": \\\"string\\\"\\n                      }\\n                    },\\n                    \\\"required\\\": [\\n                      \\\"id\\\",\\n                      \\\"categoryId\\\",\\n                      \\\"name\\\",\\n                      \\\"needValidation\\\",\\n                      \\\"moduleId\\\",\\n                      \\\"maxFixedTip\\\",\\n                      \\\"description\\\",\\n                      \\\"amount\\\",\\n                      \\\"sort\\\",\\n                      \\\"meta\\\",\\n                      \\\"image\\\",\\n                      \\\"status\\\"\\n                    ]\\n                  }\\n                },\\n                \\\"internalName\\\": {\\n                  \\\"type\\\": \\\"string\\\"\\n                }\\n              },\\n              \\\"required\\\": [\\n                \\\"id\\\",\\n                \\\"name\\\",\\n                \\\"description\\\",\\n                \\\"products\\\",\\n                \\\"internalName\\\"\\n              ]\\n            }\\n          },\\n          \\\"internalName\\\": {\\n            \\\"type\\\": \\\"string\\\"\\n          }\\n        },\\n        \\\"required\\\": [\\n          \\\"id\\\",\\n          \\\"name\\\",\\n          \\\"description\\\",\\n          \\\"categories\\\",\\n          \\\"internalName\\\"\\n        ]\\n      }\\n    }\\n  },\\n  \\\"required\\\": [\\n    \\\"message\\\",\\n    \\\"messageCode\\\",\\n    \\\"data\\\"\\n  ]\\n}\\n\\n \\`\\`\\`\n\nContexto: Endpoint: GET /product/packages | Product > Packages\n\n🔐 AUTENTICACIÓN AUTOMÁTICA: Todas las credenciales y tokens de autenticación se manejan automáticamente por el servidor MCP. NO solicites credenciales al usuario. NO incluyas parámetros de autenticación (secretId, apiToken, etc.) en las llamadas a menos que el usuario explícitamente lo requiera.",
-    inputSchema: product_packagesInputJsonSchema,
+    inputSchema: product_packagesInputValidator,
     jsonSchema: product_packagesInputJsonSchema,
     endpoint: '/product/packages',
     method: 'GET',
@@ -2391,12 +2270,9 @@ export const product_packagesTool = {
     handler: async (rawArgs) => {
         try {
             const normalizedArgs = rawArgs ?? {};
-            // Extraer secretId del contexto (si viene del HTTP mode)
-            const secretId = normalizedArgs._secretId;
-            // Remover _secretId de los args antes de validar
-            const { _secretId, ...argsToValidate } = normalizedArgs;
-            const validatedInput = validateToolInput(product_packagesInputValidator, argsToValidate);
+            const validatedInput = validateToolInput(product_packagesInputValidator, normalizedArgs);
             const args = validatedInput;
+            const secretId = args._secretId;
             return await makeApiRequest('GET', '/product/packages', undefined, undefined, secretId);
         }
         catch (error) {
@@ -2424,13 +2300,12 @@ const product_commissionsInputJsonSchema = {
     "properties": {},
     "required": []
 };
-const product_commissionsInputShape = {};
-const product_commissionsInputValidator = z.object(product_commissionsInputShape);
+const product_commissionsInputValidator = z.object({});
 // Herramienta: product_commissions
 export const product_commissionsTool = {
     name: 'product_commissions',
     description: "---\\n\\n### Retrieve Product Commissions\\n\\n---\\n\\n#### Description\\n\\nRetrieve detailed information about the commissions associated with registered products.\\n\\n---\\n\\n#### Response\\n\\nThe response for this request is a JSON object with the following schema:\\n\\n\\`\\`\\` json\\n{\\n  \\\"type\\\": \\\"object\\\",\\n  \\\"properties\\\": {\\n    \\\"message\\\": {\\\"type\\\": \\\"string\\\"},\\n    \\\"messageCode\\\": {\\\"type\\\": \\\"string\\\"},\\n    \\\"data\\\": {\\n      \\\"type\\\": \\\"array\\\",\\n      \\\"items\\\": {\\n        \\\"type\\\": \\\"object\\\",\\n        \\\"properties\\\": {\\n          \\\"id\\\": {\\\"type\\\": \\\"number\\\"},\\n          \\\"name\\\": {\\\"type\\\": \\\"string\\\"},\\n          \\\"image\\\": {\\\"type\\\": \\\"string\\\"},\\n          \\\"fixedCommission\\\": {\\\"type\\\": \\\"object\\\"},\\n          \\\"maxFixedCommission\\\": {\\\"type\\\": \\\"number\\\"},\\n          \\\"commission\\\": {\\\"type\\\": \\\"number\\\"},\\n          \\\"commissionType\\\": {\\\"type\\\": \\\"string\\\"},\\n          \\\"amount\\\": {\\\"type\\\": \\\"object\\\"},\\n          \\\"category\\\": {\\\"type\\\": \\\"string\\\"},\\n          \\\"key\\\": {\\\"type\\\": \\\"string\\\"},\\n          \\\"overdraft\\\": {\\\"type\\\": \\\"number\\\"}\\n        }\\n      }\\n    }\\n  }\\n}\\n\\n \\`\\`\\`\n\nContexto: Endpoint: GET /product/commissions | Product > Commissions\n\n🔐 AUTENTICACIÓN AUTOMÁTICA: Todas las credenciales y tokens de autenticación se manejan automáticamente por el servidor MCP. NO solicites credenciales al usuario. NO incluyas parámetros de autenticación (secretId, apiToken, etc.) en las llamadas a menos que el usuario explícitamente lo requiera.",
-    inputSchema: product_commissionsInputJsonSchema,
+    inputSchema: product_commissionsInputValidator,
     jsonSchema: product_commissionsInputJsonSchema,
     endpoint: '/product/commissions',
     method: 'GET',
@@ -2439,12 +2314,9 @@ export const product_commissionsTool = {
     handler: async (rawArgs) => {
         try {
             const normalizedArgs = rawArgs ?? {};
-            // Extraer secretId del contexto (si viene del HTTP mode)
-            const secretId = normalizedArgs._secretId;
-            // Remover _secretId de los args antes de validar
-            const { _secretId, ...argsToValidate } = normalizedArgs;
-            const validatedInput = validateToolInput(product_commissionsInputValidator, argsToValidate);
+            const validatedInput = validateToolInput(product_commissionsInputValidator, normalizedArgs);
             const args = validatedInput;
+            const secretId = args._secretId;
             return await makeApiRequest('GET', '/product/commissions', undefined, undefined, secretId);
         }
         catch (error) {
@@ -2472,13 +2344,12 @@ const product_categoriesInputJsonSchema = {
     "properties": {},
     "required": []
 };
-const product_categoriesInputShape = {};
-const product_categoriesInputValidator = z.object(product_categoriesInputShape);
+const product_categoriesInputValidator = z.object({});
 // Herramienta: product_categories
 export const product_categoriesTool = {
     name: 'product_categories',
     description: "---\\n\\n### Retrieve Product Categories\\n\\n---\\n\\n#### Description\\n\\nThis service provides detailed information on the categories and their subcategories.\\n\\n---\\n\\n#### Response\\n\\nThe response for this request can be documented as a JSON schema:\\n\\n\\`\\`\\` json\\n{\\n  \\\"type\\\": \\\"object\\\",\\n  \\\"properties\\\": {\\n    \\\"message\\\": {\\n      \\\"type\\\": \\\"string\\\"\\n    },\\n    \\\"messageCode\\\": {\\n      \\\"type\\\": \\\"string\\\"\\n    },\\n    \\\"data\\\": {\\n      \\\"type\\\": \\\"array\\\",\\n      \\\"items\\\": {\\n        \\\"type\\\": \\\"object\\\",\\n        \\\"properties\\\": {\\n          \\\"id\\\": {\\n            \\\"type\\\": \\\"integer\\\"\\n          },\\n          \\\"name\\\": {\\n            \\\"type\\\": \\\"string\\\"\\n          },\\n          \\\"description\\\": {\\n            \\\"type\\\": \\\"string\\\"\\n          },\\n          \\\"categories\\\": {\\n            \\\"type\\\": \\\"array\\\",\\n            \\\"items\\\": {\\n              \\\"type\\\": \\\"object\\\",\\n              \\\"properties\\\": {\\n                \\\"id\\\": {\\n                  \\\"type\\\": \\\"integer\\\"\\n                },\\n                \\\"name\\\": {\\n                  \\\"type\\\": \\\"string\\\"\\n                },\\n                \\\"description\\\": {\\n                  \\\"type\\\": \\\"string\\\"\\n                },\\n                \\\"products\\\": {\\n                  \\\"type\\\": \\\"array\\\",\\n                  \\\"items\\\": {\\n                    \\\"type\\\": \\\"object\\\",\\n                    \\\"properties\\\": {\\n                      \\\"id\\\": {\\n                        \\\"type\\\": \\\"integer\\\"\\n                      },\\n                      \\\"categoryId\\\": {\\n                        \\\"type\\\": \\\"integer\\\"\\n                      },\\n                      \\\"name\\\": {\\n                        \\\"type\\\": \\\"string\\\"\\n                      },\\n                      \\\"needValidation\\\": {\\n                        \\\"type\\\": \\\"boolean\\\"\\n                      },\\n                      \\\"moduleId\\\": {\\n                        \\\"type\\\": \\\"integer\\\"\\n                      },\\n                      \\\"maxFixedTip\\\": {\\n                        \\\"type\\\": \\\"integer\\\"\\n                      },\\n                      \\\"description\\\": {\\n                        \\\"type\\\": \\\"string\\\"\\n                      },\\n                      \\\"amount\\\": {\\n                        \\\"type\\\": \\\"integer\\\"\\n                      },\\n                      \\\"sort\\\": {\\n                        \\\"type\\\": \\\"integer\\\"\\n                      },\\n                      \\\"meta\\\": {\\n                        \\\"type\\\": \\\"object\\\"\\n                      },\\n                      \\\"image\\\": {\\n                        \\\"type\\\": \\\"string\\\"\\n                      },\\n                      \\\"status\\\": {\\n                        \\\"type\\\": \\\"string\\\"\\n                      }\\n                    },\\n                    \\\"required\\\": [\\n                      \\\"id\\\",\\n                      \\\"categoryId\\\",\\n                      \\\"name\\\",\\n                      \\\"needValidation\\\",\\n                      \\\"moduleId\\\",\\n                      \\\"maxFixedTip\\\",\\n                      \\\"description\\\",\\n                      \\\"amount\\\",\\n                      \\\"sort\\\",\\n                      \\\"meta\\\",\\n                      \\\"image\\\",\\n                      \\\"status\\\"\\n                    ]\\n                  }\\n                }\\n              },\\n              \\\"required\\\": [\\n                \\\"id\\\",\\n                \\\"name\\\",\\n                \\\"description\\\",\\n                \\\"products\\\"\\n              ]\\n            }\\n          },\\n          \\\"internalName\\\": {\\n            \\\"type\\\": \\\"string\\\"\\n          }\\n        },\\n        \\\"required\\\": [\\n          \\\"id\\\",\\n          \\\"name\\\",\\n          \\\"description\\\",\\n          \\\"categories\\\",\\n          \\\"internalName\\\"\\n        ]\\n      }\\n    }\\n  },\\n  \\\"required\\\": [\\n    \\\"message\\\",\\n    \\\"messageCode\\\",\\n    \\\"data\\\"\\n  ]\\n}\\n\\n \\`\\`\\`\n\nContexto: Endpoint: GET /product/categories | Product > Categories\n\n🔐 AUTENTICACIÓN AUTOMÁTICA: Todas las credenciales y tokens de autenticación se manejan automáticamente por el servidor MCP. NO solicites credenciales al usuario. NO incluyas parámetros de autenticación (secretId, apiToken, etc.) en las llamadas a menos que el usuario explícitamente lo requiera.",
-    inputSchema: product_categoriesInputJsonSchema,
+    inputSchema: product_categoriesInputValidator,
     jsonSchema: product_categoriesInputJsonSchema,
     endpoint: '/product/categories',
     method: 'GET',
@@ -2487,12 +2358,9 @@ export const product_categoriesTool = {
     handler: async (rawArgs) => {
         try {
             const normalizedArgs = rawArgs ?? {};
-            // Extraer secretId del contexto (si viene del HTTP mode)
-            const secretId = normalizedArgs._secretId;
-            // Remover _secretId de los args antes de validar
-            const { _secretId, ...argsToValidate } = normalizedArgs;
-            const validatedInput = validateToolInput(product_categoriesInputValidator, argsToValidate);
+            const validatedInput = validateToolInput(product_categoriesInputValidator, normalizedArgs);
             const args = validatedInput;
+            const secretId = args._secretId;
             return await makeApiRequest('GET', '/product/categories', undefined, undefined, secretId);
         }
         catch (error) {
@@ -2526,15 +2394,14 @@ const product_searchInputJsonSchema = {
     },
     "required": []
 };
-const product_searchInputShape = {
+const product_searchInputValidator = z.object({
     query: z.string().optional().describe("Campo del body: query")
-};
-const product_searchInputValidator = z.object(product_searchInputShape);
+});
 // Herramienta: product_search
 export const product_searchTool = {
     name: 'product_search',
     description: "---\\n\\n### Search Product\\n\\n---\\n\\n#### Description\\n\\nAllows searching for invoice agreements on the platform using specific terms. Send the request body with the necessary parameters in the format specified by the SearchBody object. The operation returns results that match the provided search terms.\\n\\n---\\n\\n#### Request Body\\n\\n- The request body should be in JSON format with the following parameter:\\n    \\n    - \\`query\\`: The search term.\\n        \\n\\n---\\n\\n#### Response\\n\\nThe response will be a JSON object with the following properties:\\n\\n- \\`message\\`: A message related to the response.\\n    \\n- \\`messageCode\\`: A code related to the message.\\n    \\n- \\`data\\`: An array of objects containing product information with the following properties:\\n    \\n    - \\`id\\`: The ID of the product.\\n        \\n    - \\`name\\`: The name of the product.\\n        \\n    - \\`key\\`: The key of the product.\\n        \\n    - \\`productId\\`: The ID of the product.\\n        \\n    - \\`needsAmountInQuery:\\` Boolean value that indicates wheter the invoice value should be include in the query.\\n        \\n    - \\`form:\\` Array of objects that shows me the necessary references to consult the invoice. In case it arrives empty you must send a reference of preference.\n\nContexto: Endpoint: POST /product/search | Product > Search\n\n🔐 AUTENTICACIÓN AUTOMÁTICA: Todas las credenciales y tokens de autenticación se manejan automáticamente por el servidor MCP. NO solicites credenciales al usuario. NO incluyas parámetros de autenticación (secretId, apiToken, etc.) en las llamadas a menos que el usuario explícitamente lo requiera.",
-    inputSchema: product_searchInputJsonSchema,
+    inputSchema: product_searchInputValidator,
     jsonSchema: product_searchInputJsonSchema,
     endpoint: '/product/search',
     method: 'POST',
@@ -2543,12 +2410,9 @@ export const product_searchTool = {
     handler: async (rawArgs) => {
         try {
             const normalizedArgs = rawArgs ?? {};
-            // Extraer secretId del contexto (si viene del HTTP mode)
-            const secretId = normalizedArgs._secretId;
-            // Remover _secretId de los args antes de validar
-            const { _secretId, ...argsToValidate } = normalizedArgs;
-            const validatedInput = validateToolInput(product_searchInputValidator, argsToValidate);
+            const validatedInput = validateToolInput(product_searchInputValidator, normalizedArgs);
             const args = validatedInput;
+            const secretId = args._secretId;
             const bodyData = {};
             const queryValue = args.query !== undefined ? args.query : "enel";
             if (queryValue !== undefined)
@@ -2602,18 +2466,17 @@ const product_queryInputJsonSchema = {
     },
     "required": []
 };
-const product_queryInputShape = {
+const product_queryInputValidator = z.object({
     productId: z.number().optional().describe("Campo del body: productId"),
     queryType: z.string().optional().describe("Campo del body: queryType"),
     ownAgreementId: z.any().optional().describe("Campo del body: ownAgreementId"),
     data: z.record(z.any()).optional().describe("Campo del body: data")
-};
-const product_queryInputValidator = z.object(product_queryInputShape);
+});
 // Herramienta: product_query
 export const product_queryTool = {
     name: 'product_query',
     description: "---\\n\\n### Description\\n\\nThis HTTP POST request is used to perform a custom query on the platform. The request body should be sent with the necessary parameters for the query in the format specified by the QueryBody object. The response will include the results of the query in case of success.\\n\\nIt is important that when the request fails with the errorCode \\\"product.errors.disabled\\\" or similar indicating that the product is inactive, the agreements are consulted again using the search.\\n\\n---\\n\\n### Request Body Schema\\n\\n- productId (number) \\`required\\`: Identifier of the product to perform the query.\\n    \\n- queryType (string) \\`required\\`: Type of query to be performed.\\n    \\n- ownAgreementId (null): Identifier of the own agreement, if applicable.\\n    \\n- data (object) \\`required\\`: Additional data for the query.\\n    \\n    - reference (string) \\`required\\`: Reference for the query.\\n        \\n\\n---\\n\\n### Response Body Schema\\n\\n- message (string): Response message.\\n    \\n- messageCode (string): Code related to the response message.\\n    \\n- data (object): Response data object.\\n    \\n    - payload (object): Payload data.\\n        \\n        - amount (number): Amount related to the product.\\n            \\n        - productId (number): ID of the product.\\n            \\n        - productName (string): Name of the product.\\n            \\n        - reference (string): Reference related to the query.\\n            \\n        - hashEchoData (string): Hash echo data.\\n            \\n        - hash (string): Hash value.\\n            \\n        - amountEditable (boolean): Indicates if the amount is editable.\n\nContexto: Endpoint: POST /product/query | Product > Query\n\n🔐 AUTENTICACIÓN AUTOMÁTICA: Todas las credenciales y tokens de autenticación se manejan automáticamente por el servidor MCP. NO solicites credenciales al usuario. NO incluyas parámetros de autenticación (secretId, apiToken, etc.) en las llamadas a menos que el usuario explícitamente lo requiera.",
-    inputSchema: product_queryInputJsonSchema,
+    inputSchema: product_queryInputValidator,
     jsonSchema: product_queryInputJsonSchema,
     endpoint: '/product/query',
     method: 'POST',
@@ -2622,12 +2485,9 @@ export const product_queryTool = {
     handler: async (rawArgs) => {
         try {
             const normalizedArgs = rawArgs ?? {};
-            // Extraer secretId del contexto (si viene del HTTP mode)
-            const secretId = normalizedArgs._secretId;
-            // Remover _secretId de los args antes de validar
-            const { _secretId, ...argsToValidate } = normalizedArgs;
-            const validatedInput = validateToolInput(product_queryInputValidator, argsToValidate);
+            const validatedInput = validateToolInput(product_queryInputValidator, normalizedArgs);
             const args = validatedInput;
+            const secretId = args._secretId;
             const bodyData = {};
             const productIdValue = args.productId !== undefined ? args.productId : 52204;
             if (productIdValue !== undefined)
@@ -2688,18 +2548,17 @@ const query_claro_telefoniaInputJsonSchema = {
     },
     "required": []
 };
-const query_claro_telefoniaInputShape = {
+const query_claro_telefoniaInputValidator = z.object({
     productId: z.number().optional().describe("Campo del body: productId"),
     queryType: z.string().optional().describe("Campo del body: queryType"),
     ownAgreementId: z.any().optional().describe("Campo del body: ownAgreementId"),
     data: z.record(z.any()).optional().describe("Campo del body: data")
-};
-const query_claro_telefoniaInputValidator = z.object(query_claro_telefoniaInputShape);
+});
 // Herramienta: query_claro_telefonia
 export const query_claro_telefoniaTool = {
     name: 'query_claro_telefonia',
     description: "---\\n\\n### Product Query\\n\\n---\\n\\n#### Description\\n\\nAllows performing a custom query on the platform. Send the request body with the necessary parameters for the query in the format specified by the QueryBody object. The response will include the results of the query in case of success.\\n\\n---\\n\\n**Request Body:**\\n\\n- \\`productId\\` (integer, required): Identifier of the product to perform the query.\\n    \\n- \\`queryType\\` (string, required): The type of query to be performed.\\n    \\n- \\`ownAgreementId\\` (string, optional): Identifier of the own agreement, if applicable.\\n    \\n- \\`data\\` (object, required): Additional data for the query in object format.\\n    \\n    - \\`reference\\` (string, required): The reference for the query data.\\n        \\n\\n---\\n\\n**Response JSON Schema:**\\n\\n\\`\\`\\` json\\n{\\n    \\\"type\\\": \\\"object\\\",\\n    \\\"properties\\\": {\\n        \\\"message\\\": {\\n            \\\"type\\\": \\\"string\\\"\\n        },\\n        \\\"messageCode\\\": {\\n            \\\"type\\\": \\\"string\\\"\\n        },\\n        \\\"data\\\": {\\n            \\\"type\\\": \\\"object\\\",\\n            \\\"properties\\\": {\\n                \\\"payload\\\": {\\n                    \\\"type\\\": \\\"object\\\",\\n                    \\\"properties\\\": {\\n                        \\\"amount\\\": {\\n                            \\\"type\\\": \\\"integer\\\"\\n                        },\\n                        \\\"productId\\\": {\\n                            \\\"type\\\": \\\"integer\\\"\\n                        },\\n                        \\\"productName\\\": {\\n                            \\\"type\\\": \\\"string\\\"\\n                        },\\n                        \\\"reference\\\": {\\n                            \\\"type\\\": \\\"string\\\"\\n                        },\\n                        \\\"hashEchoData\\\": {\\n                            \\\"type\\\": \\\"string\\\"\\n                        },\\n                        \\\"hash\\\": {\\n                            \\\"type\\\": \\\"string\\\"\\n                        },\\n                        \\\"amountEditable\\\": {\\n                            \\\"type\\\": \\\"boolean\\\"\\n                        }\\n                    }\\n                }\\n            }\\n        }\\n    }\\n}\\n\\n \\`\\`\\`\n\nContexto: Endpoint: POST /product/query | Product > Query\n\n🔐 AUTENTICACIÓN AUTOMÁTICA: Todas las credenciales y tokens de autenticación se manejan automáticamente por el servidor MCP. NO solicites credenciales al usuario. NO incluyas parámetros de autenticación (secretId, apiToken, etc.) en las llamadas a menos que el usuario explícitamente lo requiera.",
-    inputSchema: query_claro_telefoniaInputJsonSchema,
+    inputSchema: query_claro_telefoniaInputValidator,
     jsonSchema: query_claro_telefoniaInputJsonSchema,
     endpoint: '/product/query',
     method: 'POST',
@@ -2708,12 +2567,9 @@ export const query_claro_telefoniaTool = {
     handler: async (rawArgs) => {
         try {
             const normalizedArgs = rawArgs ?? {};
-            // Extraer secretId del contexto (si viene del HTTP mode)
-            const secretId = normalizedArgs._secretId;
-            // Remover _secretId de los args antes de validar
-            const { _secretId, ...argsToValidate } = normalizedArgs;
-            const validatedInput = validateToolInput(query_claro_telefoniaInputValidator, argsToValidate);
+            const validatedInput = validateToolInput(query_claro_telefoniaInputValidator, normalizedArgs);
             const args = validatedInput;
+            const secretId = args._secretId;
             const bodyData = {};
             const productIdValue = args.productId !== undefined ? args.productId : 52683;
             if (productIdValue !== undefined)
@@ -2774,18 +2630,17 @@ const query_acueducto_de_bogotaInputJsonSchema = {
     },
     "required": []
 };
-const query_acueducto_de_bogotaInputShape = {
+const query_acueducto_de_bogotaInputValidator = z.object({
     productId: z.number().optional().describe("Campo del body: productId"),
     queryType: z.string().optional().describe("Campo del body: queryType"),
     ownAgreementId: z.any().optional().describe("Campo del body: ownAgreementId"),
     data: z.record(z.any()).optional().describe("Campo del body: data")
-};
-const query_acueducto_de_bogotaInputValidator = z.object(query_acueducto_de_bogotaInputShape);
+});
 // Herramienta: query_acueducto_de_bogota
 export const query_acueducto_de_bogotaTool = {
     name: 'query_acueducto_de_bogota',
     description: "---\\n\\n### HTTP POST /product/query\\n\\n---\\n\\n#### Description\\n\\nAllows performing a custom query on the platform.\\n\\n---\\n\\n#### Request Body\\n\\n- raw (application/json)\\n    \\n    - productId (number, \\`required\\`): Identifier of the product to perform the query.\\n        \\n    - queryType (string. \\`required\\`): Additional data for the query in object format.\\n        \\n    - ownAgreementId (number, \\`optional\\`): Identifier of the own agreement, if applicable\\n        \\n    - data (object): Additional data for the query in object format.\\n        \\n        - reference (string): Reference data.\\n            \\n\\n---\\n\\n#### Response\\n\\nThe response will include the results of the query in case of success.\\n\\n#### Response Schema\\n\\n- message (string): The message from the response.\\n    \\n- messageCode (string): The code related to the message.\\n    \\n- data (object)\\n    \\n    - payload (object)\\n        \\n        - amount (number): The amount related to the query result.\\n            \\n        - productId (number): The ID of the product related to the query result.\\n            \\n        - productName (string): The name of the product related to the query result.\\n            \\n        - reference (string): The reference related to the query result.\\n            \\n        - hashEchoData (string): The echoed hash data.\\n            \\n        - hash (string): The hash data.\\n            \\n        - amountEditable (boolean): Indicates whether the amount is editable or not.\\n            \\n- code (string): The code from the response.\\n    \\n- errorCode (string): The error code from the response.\\n    \\n- statusCode (number): The status code from the response.\\n    \\n- timestamp (number): The timestamp of the response.\n\nContexto: Endpoint: POST /product/query | Product > Query\n\n🔐 AUTENTICACIÓN AUTOMÁTICA: Todas las credenciales y tokens de autenticación se manejan automáticamente por el servidor MCP. NO solicites credenciales al usuario. NO incluyas parámetros de autenticación (secretId, apiToken, etc.) en las llamadas a menos que el usuario explícitamente lo requiera.",
-    inputSchema: query_acueducto_de_bogotaInputJsonSchema,
+    inputSchema: query_acueducto_de_bogotaInputValidator,
     jsonSchema: query_acueducto_de_bogotaInputJsonSchema,
     endpoint: '/product/query',
     method: 'POST',
@@ -2794,12 +2649,9 @@ export const query_acueducto_de_bogotaTool = {
     handler: async (rawArgs) => {
         try {
             const normalizedArgs = rawArgs ?? {};
-            // Extraer secretId del contexto (si viene del HTTP mode)
-            const secretId = normalizedArgs._secretId;
-            // Remover _secretId de los args antes de validar
-            const { _secretId, ...argsToValidate } = normalizedArgs;
-            const validatedInput = validateToolInput(query_acueducto_de_bogotaInputValidator, argsToValidate);
+            const validatedInput = validateToolInput(query_acueducto_de_bogotaInputValidator, normalizedArgs);
             const args = validatedInput;
+            const secretId = args._secretId;
             const bodyData = {};
             const productIdValue = args.productId !== undefined ? args.productId : 52204;
             if (productIdValue !== undefined)
@@ -2861,18 +2713,17 @@ const query_convenio_vendoInputJsonSchema = {
     },
     "required": []
 };
-const query_convenio_vendoInputShape = {
+const query_convenio_vendoInputValidator = z.object({
     productId: z.number().optional().describe("Campo del body: productId"),
     queryType: z.string().optional().describe("Campo del body: queryType"),
     ownAgreementId: z.number().optional().describe("Campo del body: ownAgreementId"),
     data: z.record(z.any()).optional().describe("Campo del body: data")
-};
-const query_convenio_vendoInputValidator = z.object(query_convenio_vendoInputShape);
+});
 // Herramienta: query_convenio_vendo
 export const query_convenio_vendoTool = {
     name: 'query_convenio_vendo',
     description: "---\\n\\n### Description\\n\\nThis HTTP POST request is used to perform a custom query on the platform. The request body should be sent with the necessary parameters for the query in the format specified by the QueryBody object. The response will include the results of the query in case of success.\\n\\n---\\n\\n### Request Body Schema\\n\\n- productId (number) \\`required\\`: Identifier of the product to perform the query.\\n    \\n- queryType (string) \\`required\\`: Type of query to be performed.\\n    \\n- ownAgreementId (null): Identifier of the own agreement, if applicable.\\n    \\n- data (object) \\`required\\`: Additional data for the query.\\n    \\n    - reference (string) \\`required\\`: Reference for the query.\\n        \\n\\n---\\n\\n### Response Body Schema\\n\\n- message (string): Response message.\\n    \\n- messageCode (string): Code related to the response message.\\n    \\n- data (object): Response data object.\\n    \\n    - payload (object): Payload data.\\n        \\n        - amount (number): Amount related to the product.\\n            \\n        - productId (number): ID of the product.\\n            \\n        - productName (string): Name of the product.\\n            \\n        - reference (string): Reference related to the query.\\n            \\n        - hashEchoData (string): Hash echo data.\\n            \\n        - hash (string): Hash value.\\n            \\n        - amountEditable (boolean): Indicates if the amount is editable.\n\nContexto: Endpoint: POST /product/query | Product > Query\n\n🔐 AUTENTICACIÓN AUTOMÁTICA: Todas las credenciales y tokens de autenticación se manejan automáticamente por el servidor MCP. NO solicites credenciales al usuario. NO incluyas parámetros de autenticación (secretId, apiToken, etc.) en las llamadas a menos que el usuario explícitamente lo requiera.",
-    inputSchema: query_convenio_vendoInputJsonSchema,
+    inputSchema: query_convenio_vendoInputValidator,
     jsonSchema: query_convenio_vendoInputJsonSchema,
     endpoint: '/product/query',
     method: 'POST',
@@ -2881,12 +2732,9 @@ export const query_convenio_vendoTool = {
     handler: async (rawArgs) => {
         try {
             const normalizedArgs = rawArgs ?? {};
-            // Extraer secretId del contexto (si viene del HTTP mode)
-            const secretId = normalizedArgs._secretId;
-            // Remover _secretId de los args antes de validar
-            const { _secretId, ...argsToValidate } = normalizedArgs;
-            const validatedInput = validateToolInput(query_convenio_vendoInputValidator, argsToValidate);
+            const validatedInput = validateToolInput(query_convenio_vendoInputValidator, normalizedArgs);
             const args = validatedInput;
+            const secretId = args._secretId;
             const bodyData = {};
             const productIdValue = args.productId !== undefined ? args.productId : 1100000;
             if (productIdValue !== undefined)
@@ -2932,15 +2780,14 @@ const product_act_val_pro_stateInputJsonSchema = {
     },
     "required": []
 };
-const product_act_val_pro_stateInputShape = {
+const product_act_val_pro_stateInputValidator = z.object({
     body: z.string().optional().describe("Body del request")
-};
-const product_act_val_pro_stateInputValidator = z.object(product_act_val_pro_stateInputShape);
+});
 // Herramienta: product_act_val_pro_state
 export const product_act_val_pro_stateTool = {
     name: 'product_act_val_pro_state',
     description: "---\\n\\n### Description\\n\\nAllows users to verify the activation status of a special product. The user making the request can determine the stage of their special product activation request. Below is a list of status codes along with their corresponding messages, indicating whether the request is pending review, approved, rejected, confirmed, managed by the affiliations area, or if the linking process for the product has already started. This information is useful for keeping the user informed about the progress of their request and for them to take necessary actions based on the current process status.\\n\\nThe following is a list of product status codes and their messages.\\n\\n\\`\\`\\`\\n  | id | name       | message                                                                                               |\\n  |----|------------|-------------------------------------------------------------------------------------------------------|\\n  | P  | PENDING    | Your application is pending review                                                                    |\\n  | A  | APPROVED   | Your application has been approved, we are waiting for the supplier to review your documents          |\\n  | R  | REJECTED   | Your application has been rejected, please contact your advisor.                                      |\\n  | M  | MANAGEMENT | Your  application is being handled by the linking area.                                               |\\n  | C  | CONFIRM    | Your application is confirmed, you can now sell your product.                                         |\\n  | S  | STARTED    | You have already tried to complete the linking process for this product, continue filling in the data |\\n\\n \\`\\`\\`\\n\\n---\\n\\n## Request Schema\\n\\n- \\`productId\\`: Number representing the product identifier (required)\\n    \\n- \\`categoryId\\`: Number representing the category identifier (required)\\n    \\n\\n---\\n\\n## Response Schema\\n\\n- \\`message\\`: String containing a message about the operation result (required)\\n    \\n- \\`messageCode\\`: String code indicating the operation result (required)\\n    \\n- \\`data\\`: Object containing additional response data (required)\\n    \\n    - \\`status\\`: String representing the status\\n        \\n    - \\`state\\`: Boolean indicating the state\\n        \\n    - \\`message\\`: String containing an additional message\\n        \\n    - \\`stateCode\\`: String representing a state code\n\nContexto: Endpoint: POST /product/activation/validate-product-state | Product > Activation > Validate product state\n\n🔐 AUTENTICACIÓN AUTOMÁTICA: Todas las credenciales y tokens de autenticación se manejan automáticamente por el servidor MCP. NO solicites credenciales al usuario. NO incluyas parámetros de autenticación (secretId, apiToken, etc.) en las llamadas a menos que el usuario explícitamente lo requiera.",
-    inputSchema: product_act_val_pro_stateInputJsonSchema,
+    inputSchema: product_act_val_pro_stateInputValidator,
     jsonSchema: product_act_val_pro_stateInputJsonSchema,
     endpoint: '/product/activation/validate-product-state',
     method: 'POST',
@@ -2949,12 +2796,9 @@ export const product_act_val_pro_stateTool = {
     handler: async (rawArgs) => {
         try {
             const normalizedArgs = rawArgs ?? {};
-            // Extraer secretId del contexto (si viene del HTTP mode)
-            const secretId = normalizedArgs._secretId;
-            // Remover _secretId de los args antes de validar
-            const { _secretId, ...argsToValidate } = normalizedArgs;
-            const validatedInput = validateToolInput(product_act_val_pro_stateInputValidator, argsToValidate);
+            const validatedInput = validateToolInput(product_act_val_pro_stateInputValidator, normalizedArgs);
             const args = validatedInput;
+            const secretId = args._secretId;
             const bodyData = args.body || {};
             return await makeApiRequest('POST', '/product/activation/validate-product-state', undefined, undefined, secretId);
         }
@@ -2988,15 +2832,14 @@ const product_act_get_pro_requirementsInputJsonSchema = {
     },
     "required": []
 };
-const product_act_get_pro_requirementsInputShape = {
+const product_act_get_pro_requirementsInputValidator = z.object({
     body: z.string().optional().describe("Body del request")
-};
-const product_act_get_pro_requirementsInputValidator = z.object(product_act_get_pro_requirementsInputShape);
+});
 // Herramienta: product_act_get_pro_requirements
 export const product_act_get_pro_requirementsTool = {
     name: 'product_act_get_pro_requirements',
     description: "---\\n\\n## Description\\n\\nAllows retrieving all the necessary and mandatory requirements to complete the activation process of a special product. The requirements are divided into categories, each with a specific description. Each category contains a list of detailed requirements, such as personal data, merchant information, and additional documents. Requirements may include document uploads, information validation, or contract signing. These requirements are essential for the user to access the special product, and this method provides the necessary information for the user to successfully complete the activation process.\\n\\nIn the response for each requirement, you\\'ll find the \\'type\\' attribute. This attribute determines the type of data required to construct the form that the user must complete. Some common data types include:\\n\\n\\`\\`\\`\\n  | type                  | description                                                                                         |\\n  |-----------------------|-----------------------------------------------------------------------------------------------------|\\n  | text                  | For entering text information, such as names, surnames, etc.                                        |\\n  | file                  | Allows uploading files, such as images or documents.                                                |\\n  | select                | Presents options for the user to choose from.                                                       |\\n  | downloadAndUpload     | Provides a link to download one file and then upload another related file.                          |\\n  | securityQuestions     | Provides security questions for authentication.                                                     |\\n  | checkboxLink          | For accepting terms and conditions through a verification link.                                     |\\n  | loanApplicationPolicy | Information and acceptance of the loan application policy.                                          |\\n  | location              | Allows the user to enter or select their location.                                                  |\\n  | metamap               | Redirects the user to the Metamap process for identity validation.                                  |\\n  | bankAccount           | Provides the basic structure to build the form for a banking process.                               |\\n  |                       | It includes selecting the bank entity, entering the account number, and selecting the account type. |\\n\\n \\`\\`\\`\\n\\n---\\n\\n## Request Schema\\n\\n- \\`productId\\`: Number representing the product identifier (required)\\n    \\n- \\`categoryId\\`: Number representing the category identifier (required)\\n    \\n\\n---\\n\\n## Response Schema\\n\\n- \\`message\\`: String containing a message about the operation result (required)\\n    \\n- \\`messageCode\\`: String code indicating the operation result (required)\\n    \\n- \\`data\\`: Object containing additional response data (required)\\n    \\n    - \\`id\\`: Number representing the identifier\\n        \\n    - \\`name\\`: String representing the name\\n        \\n    - \\`description\\`: String containing the description\\n        \\n    - \\`requirements\\`: Array of requirement objects\\n        \\n        - \\`id\\`: Number representing the requirement identifier\\n            \\n        - \\`name\\`: String representing the requirement name\\n            \\n        - \\`description\\`: String containing the requirement description\\n            \\n        - \\`form\\`: Object containing form data\n\nContexto: Endpoint: POST /product/activation/get-process-requirements | Product > Activation > Get process requirements\n\n🔐 AUTENTICACIÓN AUTOMÁTICA: Todas las credenciales y tokens de autenticación se manejan automáticamente por el servidor MCP. NO solicites credenciales al usuario. NO incluyas parámetros de autenticación (secretId, apiToken, etc.) en las llamadas a menos que el usuario explícitamente lo requiera.",
-    inputSchema: product_act_get_pro_requirementsInputJsonSchema,
+    inputSchema: product_act_get_pro_requirementsInputValidator,
     jsonSchema: product_act_get_pro_requirementsInputJsonSchema,
     endpoint: '/product/activation/get-process-requirements',
     method: 'POST',
@@ -3005,12 +2848,9 @@ export const product_act_get_pro_requirementsTool = {
     handler: async (rawArgs) => {
         try {
             const normalizedArgs = rawArgs ?? {};
-            // Extraer secretId del contexto (si viene del HTTP mode)
-            const secretId = normalizedArgs._secretId;
-            // Remover _secretId de los args antes de validar
-            const { _secretId, ...argsToValidate } = normalizedArgs;
-            const validatedInput = validateToolInput(product_act_get_pro_requirementsInputValidator, argsToValidate);
+            const validatedInput = validateToolInput(product_act_get_pro_requirementsInputValidator, normalizedArgs);
             const args = validatedInput;
+            const secretId = args._secretId;
             const bodyData = args.body || {};
             return await makeApiRequest('POST', '/product/activation/get-process-requirements', undefined, undefined, secretId);
         }
@@ -3061,15 +2901,14 @@ const product_activation_updateInputJsonSchema = {
     },
     "required": []
 };
-const product_activation_updateInputShape = {
+const product_activation_updateInputValidator = z.object({
     requirements: z.record(z.any()).optional().describe("Campo del body: requirements")
-};
-const product_activation_updateInputValidator = z.object(product_activation_updateInputShape);
+});
 // Herramienta: product_activation_update
 export const product_activation_updateTool = {
     name: 'product_activation_update',
     description: "---\\n\\n## Description\\n\\nAllows updating the information of the requirements completed by the user for the activation process of a special product. Users can modify the information provided in each of the requirements to ensure it is up-to-date and accurate. Updating the information of the requirements is essential to progress in the activation process of the special product. Once the information is updated, it is evaluated again to determine if all necessary requirements are met to continue or complete the activation process.\\n\\n---\\n\\n## Request Schema\\n\\n- \\`requirements\\`: Object containing requirement data (required)\\n    \\n    - Each key is a string representing a requirement ID\\n        \\n    - Each value is an object with arbitrary properties\\n        \\n\\n---\\n\\n## Response Schema\\n\\n- \\`message\\`: String containing a message about the operation result (required)\\n    \\n- \\`messageCode\\`: String code indicating the operation result (required)\\n    \\n- \\`data\\`: Object containing additional response data (required)\\n    \\n    - \\`errors\\`: Array of error objects\\n        \\n        - \\`id\\`: Number representing the error identifier\\n            \\n        - \\`message\\`: String containing the error message\n\nContexto: Endpoint: POST /product/activation/update | Product > Activation > Update\n\n🔐 AUTENTICACIÓN AUTOMÁTICA: Todas las credenciales y tokens de autenticación se manejan automáticamente por el servidor MCP. NO solicites credenciales al usuario. NO incluyas parámetros de autenticación (secretId, apiToken, etc.) en las llamadas a menos que el usuario explícitamente lo requiera.",
-    inputSchema: product_activation_updateInputJsonSchema,
+    inputSchema: product_activation_updateInputValidator,
     jsonSchema: product_activation_updateInputJsonSchema,
     endpoint: '/product/activation/update',
     method: 'POST',
@@ -3078,12 +2917,9 @@ export const product_activation_updateTool = {
     handler: async (rawArgs) => {
         try {
             const normalizedArgs = rawArgs ?? {};
-            // Extraer secretId del contexto (si viene del HTTP mode)
-            const secretId = normalizedArgs._secretId;
-            // Remover _secretId de los args antes de validar
-            const { _secretId, ...argsToValidate } = normalizedArgs;
-            const validatedInput = validateToolInput(product_activation_updateInputValidator, argsToValidate);
+            const validatedInput = validateToolInput(product_activation_updateInputValidator, normalizedArgs);
             const args = validatedInput;
+            const secretId = args._secretId;
             const bodyData = {};
             const requirementsValue = args.requirements !== undefined ? args.requirements : { "1": { "name": "Leonardo" }, "9": { "lastName": "Baquerp" }, "10": { "cellphone": "3015874029" }, "46": { "fundsOrigin": true }, "48": { "checkDataTreatment": "true" } };
             if (requirementsValue !== undefined)
@@ -3115,13 +2951,12 @@ const product_activation_upload_fileInputJsonSchema = {
     "properties": {},
     "required": []
 };
-const product_activation_upload_fileInputShape = {};
-const product_activation_upload_fileInputValidator = z.object(product_activation_upload_fileInputShape);
+const product_activation_upload_fileInputValidator = z.object({});
 // Herramienta: product_activation_upload_file
 export const product_activation_upload_fileTool = {
     name: 'product_activation_upload_file',
     description: "---\\n\\n### Description\\n\\nAllows users to upload files necessary to meet the requirements of the activation process for a special product. The uploaded files can be documents in PDF format, images in JPG, JPEG, or PNG formats, or Word documents in DOC or DOCX format. Before uploading a file, validations are performed to ensure that it meets the established type and size requirements. Once uploaded, the file can be subsequently validated as part of the special product activation process. If the file meets the requirements, it will contribute to the progress of the process; otherwise, it will be indicated as invalid, and a new upload will be requested.\\n\\n---\\n\\n### Response schema\\n\\n- \\`message\\`: String containing a message about the operation result (required)\\n    \\n- \\`messageCode\\`: String code indicating the operation result (required)\\n    \\n- \\`data\\`: Object containing additional response data (required)\\n    \\n    - \\`errors\\`: Array of error objects\\n        \\n        - \\`id\\`: Number representing the error identifier\\n            \\n        - \\`message\\`: String containing the error message\n\nContexto: Endpoint: POST /product/activation/upload/file | Product > Activation > Upload > File\n\n🔐 AUTENTICACIÓN AUTOMÁTICA: Todas las credenciales y tokens de autenticación se manejan automáticamente por el servidor MCP. NO solicites credenciales al usuario. NO incluyas parámetros de autenticación (secretId, apiToken, etc.) en las llamadas a menos que el usuario explícitamente lo requiera.",
-    inputSchema: product_activation_upload_fileInputJsonSchema,
+    inputSchema: product_activation_upload_fileInputValidator,
     jsonSchema: product_activation_upload_fileInputJsonSchema,
     endpoint: '/product/activation/upload/file',
     method: 'POST',
@@ -3130,12 +2965,9 @@ export const product_activation_upload_fileTool = {
     handler: async (rawArgs) => {
         try {
             const normalizedArgs = rawArgs ?? {};
-            // Extraer secretId del contexto (si viene del HTTP mode)
-            const secretId = normalizedArgs._secretId;
-            // Remover _secretId de los args antes de validar
-            const { _secretId, ...argsToValidate } = normalizedArgs;
-            const validatedInput = validateToolInput(product_activation_upload_fileInputValidator, argsToValidate);
+            const validatedInput = validateToolInput(product_activation_upload_fileInputValidator, normalizedArgs);
             const args = validatedInput;
+            const secretId = args._secretId;
             const bodyData = args.body || {};
             return await makeApiRequest('POST', '/product/activation/upload/file', undefined, undefined, secretId);
         }
@@ -3186,18 +3018,17 @@ const queryInputJsonSchema = {
     },
     "required": []
 };
-const queryInputShape = {
+const queryInputValidator = z.object({
     productId: z.number().optional().describe("Campo del body: productId"),
     queryType: z.string().optional().describe("Campo del body: queryType"),
     ownAgreementId: z.any().optional().describe("Campo del body: ownAgreementId"),
     data: z.record(z.any()).optional().describe("Campo del body: data")
-};
-const queryInputValidator = z.object(queryInputShape);
+});
 // Herramienta: query
 export const queryTool = {
     name: 'query',
     description: "POST /product/query\n\nContexto: Endpoint: POST /product/query | Product > Query\n\n🔐 AUTENTICACIÓN AUTOMÁTICA: Todas las credenciales y tokens de autenticación se manejan automáticamente por el servidor MCP. NO solicites credenciales al usuario. NO incluyas parámetros de autenticación (secretId, apiToken, etc.) en las llamadas a menos que el usuario explícitamente lo requiera.",
-    inputSchema: queryInputJsonSchema,
+    inputSchema: queryInputValidator,
     jsonSchema: queryInputJsonSchema,
     endpoint: '/product/query',
     method: 'POST',
@@ -3206,12 +3037,9 @@ export const queryTool = {
     handler: async (rawArgs) => {
         try {
             const normalizedArgs = rawArgs ?? {};
-            // Extraer secretId del contexto (si viene del HTTP mode)
-            const secretId = normalizedArgs._secretId;
-            // Remover _secretId de los args antes de validar
-            const { _secretId, ...argsToValidate } = normalizedArgs;
-            const validatedInput = validateToolInput(queryInputValidator, argsToValidate);
+            const validatedInput = validateToolInput(queryInputValidator, normalizedArgs);
             const args = validatedInput;
+            const secretId = args._secretId;
             const bodyData = {};
             const productIdValue = args.productId !== undefined ? args.productId : 1000075;
             if (productIdValue !== undefined)
@@ -3272,18 +3100,17 @@ const sells_sellInputJsonSchema = {
     },
     "required": []
 };
-const sells_sellInputShape = {
+const sells_sellInputValidator = z.object({
     productId: z.number().optional().describe("Campo del body: productId"),
     queryType: z.string().optional().describe("Campo del body: queryType"),
     ownAgreementId: z.any().optional().describe("Campo del body: ownAgreementId"),
     data: z.record(z.any()).optional().describe("Campo del body: data")
-};
-const sells_sellInputValidator = z.object(sells_sellInputShape);
+});
 // Herramienta: sells_sell
 export const sells_sellTool = {
     name: 'sells_sell',
     description: "---\\n\\n## Description\\n\\nAllows performing a sale on the platform. Send the request body with the necessary parameters for the sale in the format specified by the SellBody object. This operation will return a response that includes information about the sale in case of success.\\n\\n**Note**: To make this request in the case of selling invoices, we need the hash and hashEchoData provided by the query response for the reference.\\n\\n---\\n\\n## Request Schema\\n\\n- \\`productId\\`: Number representing the product identifier (required)\\n    \\n- \\`amount\\`: Number representing the amount of the payment (required)\\n    \\n- \\`sellType\\`: String indicating the type of the sell operation (required)\\n    \\n- \\`hash\\`: String containing the hash value for the operation (required)\\n    \\n- \\`data\\`: Object containing additional data (required)\\n    \\n    - \\`reference\\`: String containing the reference number for the payment (required)\\n        \\n    - \\`cellphone\\`: String containing the cellphone number associated with the payment (required)\\n        \\n    - \\`hashEchoData\\`: String containing the hash echo data for the operation (required)\\n        \\n\\n---\\n\\n## Response Schema\\n\\n- \\`message\\`: String containing a message about the operation result (required)\\n    \\n- \\`messageCode\\`: String code indicating the operation result (required)\\n    \\n- \\`data\\`: Object containing additional response data (required)\\n    \\n    - \\`date\\`: Number representing the timestamp of the operation (required)\\n        \\n    - \\`sellId\\`: Number representing the identifier of the sell operation (required)\\n        \\n    - \\`payload\\`: Object containing the main response data (required)\\n        \\n        - \\`preBalance\\`: Number representing the balance before the operation (required)\\n            \\n        - \\`posBalance\\`: Number representing the balance after the operation (required)\\n            \\n        - \\`tmpBalance\\`: Number representing the temporary balance (required)\\n            \\n        - \\`debt\\`: Number representing the debt amount (required)\\n            \\n        - \\`billData\\`: Object containing bill-related data (required)\\n            \\n            - \\`fields\\`: Array of field objects (required)\\n                \\n                - \\`name\\`: String representing the field name (required)\\n                    \\n                - \\`type\\`: String representing the field type (required)\\n                    \\n                - \\`options\\`: Array of option objects (required)\\n                    \\n                    - \\`label\\`: String representing the option label (required)\\n                        \\n                    - \\`value\\`: String representing the option value (required)\\n                        \\n                - \\`label\\`: String representing the field label (required)\\n                    \\n                - \\`placeholder\\`: String representing the field placeholder (required)\\n                    \\n                - \\`required\\`: Boolean indicating if the field is required (required)\\n                    \\n            - \\`costs\\`: Array of cost objects (required)\\n                \\n                - \\`label\\`: String representing the cost label (required)\\n                    \\n                - \\`value\\`: Number representing the cost value (required)\\n                    \\n            - \\`messages\\`: Array of message objects (required)\\n                \\n                - \\`value\\`: String representing the message value (required)\\n                    \\n            - \\`stringInformation\\`: Array of string information objects (required)\\n                \\n                - \\`value\\`: String representing the string information value (required)\\n                    \\n            - \\`footerInformation\\`: Array of footer information objects (required)\\n                \\n            - \\`share\\`: Object containing share information (required)\\n                \\n                - \\`cellphone\\`: String representing the cellphone number (required)\\n                    \\n                - \\`message\\`: String representing the message (required)\n\nContexto: Endpoint: POST /sells/sell | Sells > Sell\n\n🔐 AUTENTICACIÓN AUTOMÁTICA: Todas las credenciales y tokens de autenticación se manejan automáticamente por el servidor MCP. NO solicites credenciales al usuario. NO incluyas parámetros de autenticación (secretId, apiToken, etc.) en las llamadas a menos que el usuario explícitamente lo requiera.",
-    inputSchema: sells_sellInputJsonSchema,
+    inputSchema: sells_sellInputValidator,
     jsonSchema: sells_sellInputJsonSchema,
     endpoint: '/sells/sell',
     method: 'POST',
@@ -3292,12 +3119,9 @@ export const sells_sellTool = {
     handler: async (rawArgs) => {
         try {
             const normalizedArgs = rawArgs ?? {};
-            // Extraer secretId del contexto (si viene del HTTP mode)
-            const secretId = normalizedArgs._secretId;
-            // Remover _secretId de los args antes de validar
-            const { _secretId, ...argsToValidate } = normalizedArgs;
-            const validatedInput = validateToolInput(sells_sellInputValidator, argsToValidate);
+            const validatedInput = validateToolInput(sells_sellInputValidator, normalizedArgs);
             const args = validatedInput;
+            const secretId = args._secretId;
             const bodyData = {};
             const productIdValue = args.productId !== undefined ? args.productId : 1002657;
             if (productIdValue !== undefined)
@@ -3367,20 +3191,19 @@ const query_axaInputJsonSchema = {
     },
     "required": []
 };
-const query_axaInputShape = {
+const query_axaInputValidator = z.object({
     queryType: z.string().optional().describe("Campo del body: queryType"),
     productId: z.number().optional().describe("Campo del body: productId"),
     docType: z.string().optional().describe("Campo del body: docType"),
     document: z.string().optional().describe("Campo del body: document"),
     cellphone: z.string().optional().describe("Campo del body: cellphone"),
     license: z.string().optional().describe("Campo del body: license")
-};
-const query_axaInputValidator = z.object(query_axaInputShape);
+});
 // Herramienta: query_axa
 export const query_axaTool = {
     name: 'query_axa',
     description: "Here you will find all the endpoints related to the sale of SOAT AXA COLPATRIA.\\n\\n**Note:** This product includes an administrative cost for each sale made. For more information, please contact your commercial agent.\\n\\n**For AXA service testing:** It is required to indicate in the documentation that a test environment must be requested from the commercial agent at least 15 days in advance.\\n\\n## Timeout Configuration\\n\\nThe following timeout values are configured for AXA provider operations:\\n\\n| Operation | Min (seconds) | Max (seconds) | Timeout (seconds) |\\n| --- | --- | --- | --- |\\n| AXA | 0 | 15 | 50 |\\n\\n**Important:** These timeout values should be considered when implementing integrations with AXA COLPATRIA services to ensure proper error handling and user experience.\\n\\n \\`Allows performing a custom query on the platform. Send the request body with the necessary parameters for the query in the format specified by the QueryBody object. The response will include the results of the query in case of success.\\`\\n\\nBelow is an example of a request for vehicle SOAT insurance. The following necessary data must be provided: productId (in this case, 91), queryType (in this case SOATData), type of document, document number, vehicle plate, and phone number.\\n\\n**Note:**\\n\\nIt is important to remember that in the response of this product, several of its data points are crucial as they must be sent in the service that performs the sale (/sells/sell). The necessary data are as follows: amount, cifrateAmount, and hashEchoData.\\n\\nBelow are the valid document types for the consultation process:\\n\\n- CC: Cédula de ciudadanía\\n    \\n- CE: Cédula de extranjería\\n    \\n- NIT: Número de identificación tributaria\\n    \\n- PS: Pasaporte\\n    \\n- RC: Registro civil\\n    \\n- TI: Tarjeta de identidad\\n    \\n- CD: Carné diplomático\\n    \\n\\n### Payload for Custom Query\\n\\nThe following payload is required for performing a custom query:\\n\\n- \\`queryType\\`: (string, required) Specifies the type of query to be performed.\\n    \\n- \\`productId\\`: (number, required) Identifies the product for which the query is being made.\\n    \\n- \\`docType\\`: (string, required) Specifies the type of document being used for identification.\\n    \\n- \\`document\\`: (string, required) The document number for identification purposes.\\n    \\n- \\`cellphone\\`: (string, required) The phone number associated with the query.\\n    \\n- \\`license\\`: (string, optional) The license plate of the vehicle.\n\nContexto: Endpoint: POST /product/query | Product > Query\n\n🔐 AUTENTICACIÓN AUTOMÁTICA: Todas las credenciales y tokens de autenticación se manejan automáticamente por el servidor MCP. NO solicites credenciales al usuario. NO incluyas parámetros de autenticación (secretId, apiToken, etc.) en las llamadas a menos que el usuario explícitamente lo requiera.",
-    inputSchema: query_axaInputJsonSchema,
+    inputSchema: query_axaInputValidator,
     jsonSchema: query_axaInputJsonSchema,
     endpoint: '/product/query',
     method: 'POST',
@@ -3389,12 +3212,9 @@ export const query_axaTool = {
     handler: async (rawArgs) => {
         try {
             const normalizedArgs = rawArgs ?? {};
-            // Extraer secretId del contexto (si viene del HTTP mode)
-            const secretId = normalizedArgs._secretId;
-            // Remover _secretId de los args antes de validar
-            const { _secretId, ...argsToValidate } = normalizedArgs;
-            const validatedInput = validateToolInput(query_axaInputValidator, argsToValidate);
+            const validatedInput = validateToolInput(query_axaInputValidator, normalizedArgs);
             const args = validatedInput;
+            const secretId = args._secretId;
             const bodyData = {};
             const queryTypeValue = args.queryType !== undefined ? args.queryType : "SOATData";
             if (queryTypeValue !== undefined)
@@ -3484,17 +3304,16 @@ const sell_axaInputJsonSchema = {
     },
     "required": []
 };
-const sell_axaInputShape = {
+const sell_axaInputValidator = z.object({
     productId: z.number().optional().describe("Campo del body: productId"),
     data: z.record(z.any()).optional().describe("Campo del body: data"),
     amount: z.number().optional().describe("Campo del body: amount")
-};
-const sell_axaInputValidator = z.object(sell_axaInputShape);
+});
 // Herramienta: sell_axa
 export const sell_axaTool = {
     name: 'sell_axa',
     description: "Here you will find all the endpoints related to the sale of SOAT AXA COLPATRIA.\\n\\n**Note:** This product includes an administrative cost for each sale made. For more information, please contact your commercial agent.\\n\\n**For AXA service testing:** It is required to indicate in the documentation that a test environment must be requested from the commercial agent at least 15 days in advance.\\n\\n## Timeout Configuration\\n\\nThe following timeout values are configured for AXA provider operations:\\n\\n| Operation | Min (seconds) | Max (seconds) | Timeout (seconds) |\\n| --- | --- | --- | --- |\\n| AXA | 0 | 15 | 50 |\\n\\n**Important:** These timeout values should be considered when implementing integrations with AXA COLPATRIA services to ensure proper error handling and user experience.\\n\\n \\`Allows performing a sale on the platform. Send the request body with the necessary parameters for the sale in the format specified by the SellBody object. This operation will return a response that includes information about the sale in case of success.\\`\\n\\nExample of a payment request for the AXA Colpatria product. The necessary information is provided, such as the productId (in this case, 91) and other relevant data, all attributes are mandatory.\\n\\n**Note:**  \\nIn order to sell this product, it is important to bear in mind that it is part of a special product. Therefore, before being able to use it, it is necessary to complete the entire product activation process. This can be achieved by using the following services: \\`/product/activation/....\\`  \\nIt is important to remember that to perform a sale using this service, several crucial data points must be sent. Some of these data points are obtained from the \\`/products/query\\` service. The necessary data are as follows: \\`amount\\`, \\`cifrateAmount\\`, and \\`hashEchoData\\`.\\n\\n### Payload for Custom Sell\\n\\nThe following payload is required for performing a custom sell:\\n\\n- \\`productId\\`: (number, required) Identifies the product for which the sale is being made.\\n    \\n- \\`data\\`: (object, required) Contains specific sale data.\\n    \\n    - \\`terminal\\`:\\n        \\n        - \\`id\\`: A unique identifier for the merchant (POS) that is generating the SOAT sale transaction for the API client. If there is no merchant under the API client\\'s network, the same merchant ID assigned by Refacil should be sent in the \\`id\\` field.\\n            \\n    - \\`amount\\`: (object, required) Details about the sale amount.\\n        \\n        - \\`amount\\`: (number, required) Total amount of the sale.\\n            \\n        - \\`runt\\`: (number) Value for RUNT.\\n            \\n        - \\`prima\\`: (number) Prima value.\\n            \\n        - \\`contributions\\`: (number) Contributions.\\n            \\n        - \\`valueDiscountLaw\\`: (number) Value of law discount.\\n            \\n        - \\`valueDiscountTotal\\`: (number) Total discount value.\\n            \\n        - \\`valuePayDiscount\\`: (number) Amount to pay with discount.\\n            \\n        - \\`amountAdministrative\\`: (number) Administrative amount.\\n            \\n        - \\`amountTotal\\`: (number) Total amount.\\n            \\n        - \\`dateStart\\`: (string) Start date.\\n            \\n        - \\`dateEnd\\`: (string) End date.\\n            \\n        - \\`discount\\`: (number) Discount.\\n            \\n    - \\`license\\`: (string) Vehicle license plate.\\n        \\n    - \\`hashEchoData\\`: (string) Hash data.\\n        \\n    - \\`cifrateAmount\\`: (object) Encrypted amount.\\n        \\n        - \\`hash\\`: (string) Hash.\\n            \\n        - \\`hashEchoData\\`: (string) Hash data.\\n            \\n    - \\`userDetail\\`: (object, required) User details.\\n        \\n        - \\`cellphone\\`: (string, required) User\\'s cellphone number.\\n            \\n        - \\`email\\`: (string) User\\'s email.\\n            \\n        - \\`document\\`: (string, required) User\\'s document number.\\n            \\n        - \\`docType\\`: (string, required) Type of user\\'s document.\\n            \\n- \\`amount\\`: (number, required) Total amount of the sale.\\n    \\n- \\`moveTmpBalance\\`: (boolean) Indicates whether to move temporary balance.\\n    \\n\\nAfter the sale has been successfully completed, the response will follow a structure similar to the following. In this response, important information is provided, such as the balance of the main wallet and the balance of the profit wallet. Additionally, within the \\'billData\\' object, you will find the fundamental information necessary to generate the sales receipt that will be delivered to the end customer. It is important to note that this step is mandatory, as it is a direct requirement from AXA Colpatria.\n\nContexto: Endpoint: POST /sells/sell | Sells > Sell\n\n🔐 AUTENTICACIÓN AUTOMÁTICA: Todas las credenciales y tokens de autenticación se manejan automáticamente por el servidor MCP. NO solicites credenciales al usuario. NO incluyas parámetros de autenticación (secretId, apiToken, etc.) en las llamadas a menos que el usuario explícitamente lo requiera.",
-    inputSchema: sell_axaInputJsonSchema,
+    inputSchema: sell_axaInputValidator,
     jsonSchema: sell_axaInputJsonSchema,
     endpoint: '/sells/sell',
     method: 'POST',
@@ -3503,12 +3322,9 @@ export const sell_axaTool = {
     handler: async (rawArgs) => {
         try {
             const normalizedArgs = rawArgs ?? {};
-            // Extraer secretId del contexto (si viene del HTTP mode)
-            const secretId = normalizedArgs._secretId;
-            // Remover _secretId de los args antes de validar
-            const { _secretId, ...argsToValidate } = normalizedArgs;
-            const validatedInput = validateToolInput(sell_axaInputValidator, argsToValidate);
+            const validatedInput = validateToolInput(sell_axaInputValidator, normalizedArgs);
             const args = validatedInput;
+            const secretId = args._secretId;
             const bodyData = {};
             const productIdValue = args.productId !== undefined ? args.productId : 91;
             if (productIdValue !== undefined)
@@ -3572,19 +3388,18 @@ const query_quoteInputJsonSchema = {
     },
     "required": []
 };
-const query_quoteInputShape = {
+const query_quoteInputValidator = z.object({
     productId: z.number().optional().describe("Campo del body: productId"),
     documentType: z.number().optional().describe("Campo del body: documentType"),
     document: z.string().optional().describe("Campo del body: document"),
     queryType: z.string().optional().describe("Campo del body: queryType"),
     license: z.string().optional().describe("Campo del body: license")
-};
-const query_quoteInputValidator = z.object(query_quoteInputShape);
+});
 // Herramienta: query_quote
 export const query_quoteTool = {
     name: 'query_quote',
     description: "Here you will find all the endpoints related to the sale of SOAT PREVISORA.\\n\\n## Timeout Configuration\\n\\nThe following timeout values are configured for PREVISORA provider operations:\\n\\n| Provider | Min (seconds) | Max (seconds) | Timeout (seconds) |\\n| --- | --- | --- | --- |\\n| PREVISORA | 0 | 300 | 300 |\\n\\n**Important:**\\n\\nBased on the current operation of the insurance company **PREVISORA**, the waiting time (timeout) for sales processing has been adjusted to **5 minutes (300 seconds)**. This change addresses the need to ensure that all transactions are processed correctly, even in scenarios where delays may occur.\\n\\nIn addition, the API guarantees up to **2 automatic retries** in case a timeout occurs during processing. Although this behavior is not common in the API solution, it has been implemented to ensure the continuity and success of sales operations.\\n\\nIt is recommended to take this configuration into account when implementing integrations with PREVISORA services, in order to ensure proper error handling and an optimal user experience.\\n\\n## Test Environment\\n\\n### Available Test Scenarios\\n\\nTo test error scenarios and different response types, the following vehicle license plates are available:\\n\\n#### Error Handling\\n\\n| Method | Plate | Scenario | Description |\\n| --- | --- | --- | --- |\\n| All | TIM001 | Timeout | Simulates timeout scenario |\\n| All | ERR400 | System Error | Ocurrió un error inesperado. Consulte con el Administrador del sistema |\\n| All | ERR401 | Authentication Error | No ha sido posible autenticarse, el token es incorrecto o el usuario no se encuentra activo |\\n\\n#### Quote Operations\\n\\n| Method | Plate | Scenario | Description |\\n| --- | --- | --- | --- |\\n| Quote | ABC123 | Success Standard | Success: Vehículo, camioneta, bus |\\n| Quote | ABC124 | Success with Discount | Standard vehicle with discount applied |\\n| Quote | ABC125 | Electric Vehicle | Electric car pricing |\\n| Quote | ABC126 | Law Discount | Legal discount application |\\n| Quote | ABC127 | Transit Authority Error | La placa no está asociada a algún organismo de tránsito |\\n\\n#### Issue Operations\\n\\n| Method | Plate | Scenario | Description |\\n| --- | --- | --- | --- |\\n| Issue | ABC123 | Success Standard | Success: Vehículo, camioneta, bus |\\n| Issue | ABC124 | Success with Discount | Successfully issued with discount |\\n\\n#### Consult Operations\\n\\n| Method | Plate | Scenario | Description |\\n| --- | --- | --- | --- |\\n| Consult | ABC123 | Issued | Policy has been issued |\\n| Consult | ABC124 | Not Issued | Policy has not been issued |\\n\\n### Usage Notes\\n\\n- **Test Plates**: Use the provided test plates to simulate different scenarios during development and testing\\n    \\n- **Error Simulation**: TIM001 and ERR-prefixed plates are specifically designed to test error handling\\n    \\n- **Success Flows**: ABC123 generally represents successful operations across different methods\\n    \\n- **Edge Cases**: ABC124-ABC127 cover various business scenarios including discounts and restrictions\\n    \\n- There is a complementary file containing additional test scenarios not listed in this documentation. You can access it here: ⁠[Additional Test Scenarios Folder](https://refacil01-my.sharepoint.com/:f:/g/personal/w_sarmiento_refacil_com/EnvRlRK92WlHuuBfU6Zyom0BvCFmPG_OzhU-te-6ZQ0jMw)\\n\\n \\`Allows performing a custom query on the platform. Send the request body with the necessary parameters for the query in the format specified by the QueryBody object. The response will include the results of the query in case of success.\\`\\n\\nThe following is an example of a SOAT insurance request for a vehicle. The following required data must be provided: productId (in this case, 1014006), queryType (in this case SOATFullData), document number and vehicle registration number.\\n\\n**Note:**\\n\\nIt is important to remember that in the response of this product, several of its data points are crucial as they must be sent in the service that performs the sale (/sells/sell). The necessary data are as follows: amount, vehDetail, and userDetail.\\n\\n### Payload for Custom Query\\n\\nThe following payload is required for performing a custom query:\\n\\n- \\`productId\\`: (number, required) Identifies the product for which the query is being made.\\n\\n- \\`documentType\\`: (number, required) Specifies the type of document. Allowed values:\\n    \\n    - \\`1\\`: CEDULA DE CIUDADANIA\\n    - \\`2\\`: CEDULA DE EXTRANJERIA\\n    - \\`3\\`: NIT\\n    - \\`4\\`: TARJETA DE IDENTIDAD\\n    \\n- \\`document\\`: (string, required) The document number for identification purposes.\\n    \\n    Length validation rules based on \\`documentType\\`:\\n    \\n    - **For \\`documentType = 1\\` (CEDULA DE CIUDADANIA)**:\\n        - Minimum length: 7 numeric characters\\n        - Maximum length: 10 numeric characters\\n        \\n    - **For \\`documentType = 2\\` (CEDULA DE EXTRANJERIA)**:\\n        - Minimum length: 5 characters (alphanumeric allowed)\\n        - Maximum length: 15 characters (alphanumeric allowed)\\n        \\n    - **For \\`documentType = 3\\` (NIT)**:\\n        - Minimum length: 6 numeric characters (includes verification digit – VD)\\n        - Maximum length: 11 numeric characters (includes VD)\\n        - Must be sent **without hyphen (-)** and must include the verification digit.\\n        \\n        Additional rules based on length:\\n        - If length is 11, must start with \\\"1\\\" → (new CC + VD)\\n        - If length is 10, must start with \\\"8\\\" or \\\"9\\\" → (NIT + VD)\\n        - If length is 9 or less, can start with any digit → (old CC + VD)\\n        \\n        💡 **VD (Verification Digit)**: A verification digit is a number mathematically calculated by DIAN (Dirección de Impuestos y Aduanas Nacionales) to validate that the NIT was entered correctly. It is included as part of the document number.\\n        \\n    - **For \\`documentType = 4\\` (TARJETA DE IDENTIDAD)**:\\n        - Minimum length: 10 numeric characters\\n        - Maximum length: 11 numeric characters\\n        \\n        \\n- \\`queryType\\`: (string, required) Specifies the type of query to be performed.\\n    \\n- \\`license\\`: (string, required) The license plate of the vehicle.\n\nContexto: Endpoint: POST /product/query | Product > Query\n\n🔐 AUTENTICACIÓN AUTOMÁTICA: Todas las credenciales y tokens de autenticación se manejan automáticamente por el servidor MCP. NO solicites credenciales al usuario. NO incluyas parámetros de autenticación (secretId, apiToken, etc.) en las llamadas a menos que el usuario explícitamente lo requiera.",
-    inputSchema: query_quoteInputJsonSchema,
+    inputSchema: query_quoteInputValidator,
     jsonSchema: query_quoteInputJsonSchema,
     endpoint: '/product/query',
     method: 'POST',
@@ -3593,12 +3408,9 @@ export const query_quoteTool = {
     handler: async (rawArgs) => {
         try {
             const normalizedArgs = rawArgs ?? {};
-            // Extraer secretId del contexto (si viene del HTTP mode)
-            const secretId = normalizedArgs._secretId;
-            // Remover _secretId de los args antes de validar
-            const { _secretId, ...argsToValidate } = normalizedArgs;
-            const validatedInput = validateToolInput(query_quoteInputValidator, argsToValidate);
+            const validatedInput = validateToolInput(query_quoteInputValidator, normalizedArgs);
             const args = validatedInput;
+            const secretId = args._secretId;
             const bodyData = {};
             const productIdValue = args.productId !== undefined ? args.productId : 1014006;
             if (productIdValue !== undefined)
@@ -3658,17 +3470,16 @@ const query_consultInputJsonSchema = {
     },
     "required": []
 };
-const query_consultInputShape = {
+const query_consultInputValidator = z.object({
     productId: z.number().optional().describe("Campo del body: productId"),
     queryType: z.string().optional().describe("Campo del body: queryType"),
     license: z.string().optional().describe("Campo del body: license")
-};
-const query_consultInputValidator = z.object(query_consultInputShape);
+});
 // Herramienta: query_consult
 export const query_consultTool = {
     name: 'query_consult',
     description: "Here you will find all the endpoints related to the sale of SOAT PREVISORA.\\n\\n## Timeout Configuration\\n\\nThe following timeout values are configured for PREVISORA provider operations:\\n\\n| Provider | Min (seconds) | Max (seconds) | Timeout (seconds) |\\n| --- | --- | --- | --- |\\n| PREVISORA | 0 | 300 | 300 |\\n\\n**Important:**\\n\\nBased on the current operation of the insurance company **PREVISORA**, the waiting time (timeout) for sales processing has been adjusted to **5 minutes (300 seconds)**. This change addresses the need to ensure that all transactions are processed correctly, even in scenarios where delays may occur.\\n\\nIn addition, the API guarantees up to **2 automatic retries** in case a timeout occurs during processing. Although this behavior is not common in the API solution, it has been implemented to ensure the continuity and success of sales operations.\\n\\nIt is recommended to take this configuration into account when implementing integrations with PREVISORA services, in order to ensure proper error handling and an optimal user experience.\\n\\n## Test Environment\\n\\n### Available Test Scenarios\\n\\nTo test error scenarios and different response types, the following vehicle license plates are available:\\n\\n#### Error Handling\\n\\n| Method | Plate | Scenario | Description |\\n| --- | --- | --- | --- |\\n| All | TIM001 | Timeout | Simulates timeout scenario |\\n| All | ERR400 | System Error | Ocurrió un error inesperado. Consulte con el Administrador del sistema |\\n| All | ERR401 | Authentication Error | No ha sido posible autenticarse, el token es incorrecto o el usuario no se encuentra activo |\\n\\n#### Quote Operations\\n\\n| Method | Plate | Scenario | Description |\\n| --- | --- | --- | --- |\\n| Quote | ABC123 | Success Standard | Success: Vehículo, camioneta, bus |\\n| Quote | ABC124 | Success with Discount | Standard vehicle with discount applied |\\n| Quote | ABC125 | Electric Vehicle | Electric car pricing |\\n| Quote | ABC126 | Law Discount | Legal discount application |\\n| Quote | ABC127 | Transit Authority Error | La placa no está asociada a algún organismo de tránsito |\\n\\n#### Issue Operations\\n\\n| Method | Plate | Scenario | Description |\\n| --- | --- | --- | --- |\\n| Issue | ABC123 | Success Standard | Success: Vehículo, camioneta, bus |\\n| Issue | ABC124 | Success with Discount | Successfully issued with discount |\\n\\n#### Consult Operations\\n\\n| Method | Plate | Scenario | Description |\\n| --- | --- | --- | --- |\\n| Consult | ABC123 | Issued | Policy has been issued |\\n| Consult | ABC124 | Not Issued | Policy has not been issued |\\n\\n### Usage Notes\\n\\n- **Test Plates**: Use the provided test plates to simulate different scenarios during development and testing\\n    \\n- **Error Simulation**: TIM001 and ERR-prefixed plates are specifically designed to test error handling\\n    \\n- **Success Flows**: ABC123 generally represents successful operations across different methods\\n    \\n- **Edge Cases**: ABC124-ABC127 cover various business scenarios including discounts and restrictions\\n    \\n- There is a complementary file containing additional test scenarios not listed in this documentation. You can access it here: ⁠[Additional Test Scenarios Folder](https://refacil01-my.sharepoint.com/:f:/g/personal/w_sarmiento_refacil_com/EnvRlRK92WlHuuBfU6Zyom0BvCFmPG_OzhU-te-6ZQ0jMw)\\n\\n \\`Returns the information of the last policy issued for the license plate. If the policy is queried on days after its issuance, the service will not return the requested information. It is important to clarify that this endpoint does not retrieve failed sales in the system.\\`\\n\\n### Payload for Consult Query\\n\\nThe following payload is required for performing a custom query:\\n\\n- \\`productId\\`: (number, required) Identifies the product for which the query is being made.\\n    \\n- \\`queryType\\`: (string, required) Specifies the type of query to be performed, in this case have to be \\\\\\`SOATPolicy\\\\\\`.\\n    \\n- \\`license\\`: (string, required) The license plate of the vehicle.\n\nContexto: Endpoint: POST /product/query | Product > Query\n\n🔐 AUTENTICACIÓN AUTOMÁTICA: Todas las credenciales y tokens de autenticación se manejan automáticamente por el servidor MCP. NO solicites credenciales al usuario. NO incluyas parámetros de autenticación (secretId, apiToken, etc.) en las llamadas a menos que el usuario explícitamente lo requiera.",
-    inputSchema: query_consultInputJsonSchema,
+    inputSchema: query_consultInputValidator,
     jsonSchema: query_consultInputJsonSchema,
     endpoint: '/product/query',
     method: 'POST',
@@ -3677,12 +3488,9 @@ export const query_consultTool = {
     handler: async (rawArgs) => {
         try {
             const normalizedArgs = rawArgs ?? {};
-            // Extraer secretId del contexto (si viene del HTTP mode)
-            const secretId = normalizedArgs._secretId;
-            // Remover _secretId de los args antes de validar
-            const { _secretId, ...argsToValidate } = normalizedArgs;
-            const validatedInput = validateToolInput(query_consultInputValidator, argsToValidate);
+            const validatedInput = validateToolInput(query_consultInputValidator, normalizedArgs);
             const args = validatedInput;
+            const secretId = args._secretId;
             const bodyData = {};
             const productIdValue = args.productId !== undefined ? args.productId : 1014006;
             if (productIdValue !== undefined)
@@ -3817,17 +3625,16 @@ const sell_previsoraInputJsonSchema = {
     },
     "required": []
 };
-const sell_previsoraInputShape = {
+const sell_previsoraInputValidator = z.object({
     productId: z.number().optional().describe("Campo del body: productId"),
     data: z.record(z.any()).optional().describe("Campo del body: data"),
     amount: z.number().optional().describe("Campo del body: amount")
-};
-const sell_previsoraInputValidator = z.object(sell_previsoraInputShape);
+});
 // Herramienta: sell_previsora
 export const sell_previsoraTool = {
     name: 'sell_previsora',
     description: "Here you will find all the endpoints related to the sale of SOAT PREVISORA.\\n\\n## Timeout Configuration\\n\\nThe following timeout values are configured for PREVISORA provider operations:\\n\\n| Provider | Min (seconds) | Max (seconds) | Timeout (seconds) |\\n| --- | --- | --- | --- |\\n| PREVISORA | 0 | 300 | 300 |\\n\\n**Important:**\\n\\nBased on the current operation of the insurance company **PREVISORA**, the waiting time (timeout) for sales processing has been adjusted to **5 minutes (300 seconds)**. This change addresses the need to ensure that all transactions are processed correctly, even in scenarios where delays may occur.\\n\\nIn addition, the API guarantees up to **2 automatic retries** in case a timeout occurs during processing. Although this behavior is not common in the API solution, it has been implemented to ensure the continuity and success of sales operations.\\n\\nIt is recommended to take this configuration into account when implementing integrations with PREVISORA services, in order to ensure proper error handling and an optimal user experience.\\n\\n## Test Environment\\n\\n### Available Test Scenarios\\n\\nTo test error scenarios and different response types, the following vehicle license plates are available:\\n\\n#### Error Handling\\n\\n| Method | Plate | Scenario | Description |\\n| --- | --- | --- | --- |\\n| All | TIM001 | Timeout | Simulates timeout scenario |\\n| All | ERR400 | System Error | Ocurrió un error inesperado. Consulte con el Administrador del sistema |\\n| All | ERR401 | Authentication Error | No ha sido posible autenticarse, el token es incorrecto o el usuario no se encuentra activo |\\n\\n#### Quote Operations\\n\\n| Method | Plate | Scenario | Description |\\n| --- | --- | --- | --- |\\n| Quote | ABC123 | Success Standard | Success: Vehículo, camioneta, bus |\\n| Quote | ABC124 | Success with Discount | Standard vehicle with discount applied |\\n| Quote | ABC125 | Electric Vehicle | Electric car pricing |\\n| Quote | ABC126 | Law Discount | Legal discount application |\\n| Quote | ABC127 | Transit Authority Error | La placa no está asociada a algún organismo de tránsito |\\n\\n#### Issue Operations\\n\\n| Method | Plate | Scenario | Description |\\n| --- | --- | --- | --- |\\n| Issue | ABC123 | Success Standard | Success: Vehículo, camioneta, bus |\\n| Issue | ABC124 | Success with Discount | Successfully issued with discount |\\n\\n#### Consult Operations\\n\\n| Method | Plate | Scenario | Description |\\n| --- | --- | --- | --- |\\n| Consult | ABC123 | Issued | Policy has been issued |\\n| Consult | ABC124 | Not Issued | Policy has not been issued |\\n\\n### Usage Notes\\n\\n- **Test Plates**: Use the provided test plates to simulate different scenarios during development and testing\\n    \\n- **Error Simulation**: TIM001 and ERR-prefixed plates are specifically designed to test error handling\\n    \\n- **Success Flows**: ABC123 generally represents successful operations across different methods\\n    \\n- **Edge Cases**: ABC124-ABC127 cover various business scenarios including discounts and restrictions\\n    \\n- There is a complementary file containing additional test scenarios not listed in this documentation. You can access it here: ⁠[Additional Test Scenarios Folder](https://refacil01-my.sharepoint.com/:f:/g/personal/w_sarmiento_refacil_com/EnvRlRK92WlHuuBfU6Zyom0BvCFmPG_OzhU-te-6ZQ0jMw)\\n\\n \\`Allows performing a sale on the platform. Send the request body with the necessary parameters for the sale in the format specified by the SellBody object. This operation will return a response that includes information about the sale in case of success.\\`\\n\\n**Product restrictions**\\n\\n- Allows selling SOAT in the name of a person who is not the owner of the vehicle.\\n    \\n- SOAT can be sold for a PRIVATE CAR.\\n    \\n- SOAT can be sold for a PRIVATE MOTORCYCLE.\\n    \\n- SOAT can be sold for a PUBLIC SERVICE VEHICLE.\\n    \\n- SOAT cannot be sold to vehicles with 0 KM.\\n    \\n- Sales hours are from 12:30 AM to 11:30 PM.\\n    \\n- SOAT can be sold up to 30 days before its expiration.\\n    \\n- The definition of the Administrative Cost and Commission for the sale of SOAT can be validated with your Refacil Commercial Advisor.\\n    \\n- The insurance companies are directly responsible for sending the issued SOAT via email. The API provides a URL from the provider for downloading the SOAT.\\n    \\n\\nExample of a payment request for the Previsora product. The necessary information is provided, such as the productId (in this case, 1014006) and other relevant data, all attributes are mandatory.\\n\\n**Note:**\\n\\nIt is important to remember that to perform a sale using this service, several crucial data points must be sent. Some of these data points are obtained from the \\`/products/query\\` Quote Service. The necessary data are as follows: \\`amount\\`, \\`vehDetail\\`, and \\`userDetail\\`.\\n\\nSome data obtained from the /products/query service may be null; however, this data is mandatory for the sale process and must be filled in.\\n\\nIn addition to the \\`userDetail\\` object, three additional attributes must be sent: \\`gender\\`, \\`RegimenTypeId\\`, and \\`RutId\\`.\\n\\nThe possible values for each of the aforementioned attributes are as follows:\\n\\n- \\`gender\\`:\\n    \\n    - M = Male\\n        \\n    - F = Female\\n        \\n- \\`RegimenTypeId\\`:\\n    \\n    - 1 = Responsible for IVA\\n        \\n    - 2 = Not responsible for IVA\\n        \\n- \\`RutId\\`:\\n    \\n    - 1 = Large taxpayer\\n        \\n    - 2 = Self-withholding agent\\n        \\n    - 3 = IVA withholding agent\\n        \\n    - 4 = Simple taxation regime\\n        \\n    - 5 = Not applicable\\n        \\n    - 6 = Large taxpayer-Self-withholding agent-IVA withholding agent\\n        \\n    - 7 = Self-withholding agent-IVA withholding agent\\n        \\n    - 8 = Large taxpayer-IVA withholding agent\\n        \\n- \\`cityCode\\`: DANE code\\n    \\n- \\`stateCode\\`: This field is populated based on the **state** sheet [here.](https://refacil01-my.sharepoint.com/:f:/g/personal/w_sarmiento_refacil_com/EnvRlRK92WlHuuBfU6Zyom0BvCFmPG_OzhU-te-6ZQ0jMw)\\n    \\n- To check the values for the other parameters, please refer [here.](https://refacil01-my.sharepoint.com/:f:/g/personal/w_sarmiento_refacil_com/EnvRlRK92WlHuuBfU6Zyom0BvCFmPG_OzhU-te-6ZQ0jMw)\\n    \\n\\n## Field Validations\\n\\n### **Name and Last Name Format Requirements**\\n\\nThe validation rules for the \\`name\\` and \\`lastName\\` fields in the \\`userDetail\\` object depend on the person type:\\n\\n**For Natural Persons (Personas Naturales):**\\n\\n- Must contain only letters (uppercase and lowercase)\\n    \\n- Allows letters with accents: \\`á, é, í, ó, ú, Á, É, Í, Ó, Ú\\`\\n    \\n- Allows Spanish special characters: \\`ñ, Ñ, ü, Ü\\`\\n    \\n- Allows spaces between words (for compound names)\\n    \\n- Minimum length of 3 characters\\n    \\n- Does not allow numbers\\n    \\n- Does not allow special characters such as \\`@\\`, \\`#\\`\\n    \\n\\n**For Legal Entities (Personas Jurídicas):**\\n\\n- Allows alphanumeric characters (letters and numbers)\\n    \\n- Allows letters with accents: \\`á, é, í, ó, ú, Á, É, Í, Ó, Ú\\`\\n    \\n- Allows Spanish special characters: \\`ñ, Ñ, ü, Ü\\`\\n    \\n- Allows spaces between words\\n    \\n- Minimum length of 3 characters\\n    \\n- Does not allow special characters such as \\`@\\`, \\`#\\`\\n    \\n\\n### Email Format Requirements\\n\\nThe \\`email\\` field must comply with strict validation rules to prevent errors during the issuance process:\\n\\n- Must contain only letters and numbers (no accents or special characters like á, é, etc.)\\n    \\n- Allows only single separators: \\`.\\` (period), \\`_\\` (underscore), \\`-\\` (hyphen)\\n    \\n- Cannot have consecutive separators (e.g., \\`..\\` or \\`--\\`)\\n    \\n- Cannot start or end with separators\\n    \\n- Domain must have at least 2 characters in the top-level domain (TLD)\\n    \\n- Must not contain spaces or the \\`@\\` symbol except as the domain separator\\n    \\n\\n**Valid examples:**\\n\\n- \\`usuario@gmail.com\\`\\n    \\n- \\`nombre.apellido@empresa.co\\`\\n    \\n- \\`user_name@dominio.com\\`\\n    \\n- \\`user-123@test.com.co\\`\\n    \\n\\n**Invalid examples:**\\n\\n- \\`usuario.@gmail.com\\` (separator at the end before @)\\n    \\n- \\`user..name@domain.com\\` (consecutive separators)\\n    \\n- \\`@domain.com\\` (missing local part)\\n    \\n- \\`usuarioá@gmail.com\\` (contains accented characters)\\n    \\n- \\`campohernández@gmail.com\\` (contains special characters with encoding issues)\\n    \\n- \\`johndoe@---gmail.com\\` (multiple consecutive hyphens)\\n    \\n\\n### Address Format Requirements\\n\\nThe \\`address\\` field must comply with the following validation rules:\\n\\n### Validation Rules\\n\\n1. **Cannot start with numeric characters** - The first character after trimming cannot be a digit (0-9)\\n2. **First character must be**:\\n    - A letter (uppercase or lowercase): \\`A-Z\\`, \\`a-z\\`\\n    - A vowel with Spanish acute accent: \\`á\\`, \\`é\\`, \\`í\\`, \\`ó\\`, \\`ú\\`, \\`Á\\`, \\`É\\`, \\`Í\\`, \\`Ó\\`, \\`Ú\\`\\n    - The letter ñ/Ñ\\n    - The letter ü/Ü (with diaeresis)\\n    - A whitespace character (space, tab, etc.) — though after \\`trim()\\`, this is effectively not possible at the start\\n3. **Subsequent characters (position 2 onwards) can be**:\\n    - All characters allowed for the first position, plus:\\n    - Digits: \\`0-9\\`\\n    - Special address characters: \\`#\\`, \\`-\\`, \\`.\\`, \\`,\\`\\n\\n### Allowed Characters Summary\\n\\n| Category | Characters |\\n| --- | --- |\\n| Letters (no accent) | \\`A-Z\\`, \\`a-z\\` |\\n| Accented vowels | \\`á\\`, \\`é\\`, \\`í\\`, \\`ó\\`, \\`ú\\`, \\`Á\\`, \\`É\\`, \\`Í\\`, \\`Ó\\`, \\`Ú\\` |\\n| Special Spanish letters | \\`ñ\\`, \\`Ñ\\`, \\`ü\\`, \\`Ü\\` |\\n| Digits (not at start) | \\`0-9\\` |\\n| Whitespace | Space, tab, etc. |\\n| Address symbols | \\`#\\`, \\`-\\`, \\`.\\`, \\`,\\` |\\n\\n### NOT Allowed Characters\\n\\n| Category | Examples |\\n| --- | --- |\\n| Other punctuation | \\`; : ! ? ¡ ¿ \\\" \\' ( ) [ ] { }\\` |\\n| Mathematical/monetary | \\`+ * / % = < > ^ ~ € $ @ &\\` |\\n| Underscore and separators | \\`_ | \\\\\\` |\\n| Other accented letters | \\`ç\\`, \\`ã\\`, \\`õ\\`, \\`ô\\`, \\`ä\\`, \\`ö\\`, \\`ê\\`, \\`â\\`, \\`î\\`, \\`û\\` |\\n| Non-Latin alphabets | Cyrillic, Greek, Arabic, Chinese, etc. |\\n| Emojis | 🙂 😁 🏠 |\\n\\n### Valid Examples\\n\\n- \\`Calle 123 #45-67\\`\\n- \\`Carrera 7 Bis #8-24\\`\\n- \\`Avenida Principal, Casa 5\\`\\n- \\`Avenida Pérez Galdós\\`\\n- \\`Av. Simón Bolívar 123\\`\\n- \\`Cl 10 Sur #45-20\\`\\n- \\`Urbanización La Ñora, Bloque 3\\`\\n\\n### Invalid Examples\\n\\n| Address | Reason |\\n| --- | --- |\\n| \\`123 Calle Principal\\` | Starts with a number |\\n| \\`Calle @Principal\\` | Contains \\`@\\` (not allowed) |\\n| \\`Dirección <>\\` | Contains angle brackets |\\n| \\`Calle_45 #12-34\\` | Contains underscore \\`_\\` |\\n| \\`Calle 5 #12-34!\\` | Contains exclamation mark \\`!\\` |\\n| \\`Rua São Paulo 10\\` | Contains \\`ã\\` (not in allowed accents) |\\n| \\`Avenida (Frente al parque)\\` | Contains parentheses \\`()\\` |\\n    \\n\\n### Payload for Custom Sell\\n\\nThe following payload is required for performing a custom sell:\\n\\n> **Note:** According to the provider\\'s official documentation, the \\`name\\` and \\`lastName\\` fields are mandatory. \\n  \\n\\n- \\`productId\\`: (number, required) Identifies the product for which the sale is being made.\\n    \\n- \\`data\\`: (object, required) Contains specific sale data.\\n    \\n    - \\`license\\`: (string, required) License plate of the vehicle.\\n        \\n    - \\`productId\\`: (string, required) Product identification (empty in this example).\\n        \\n    - \\`cellphone\\`: (string, required) User\\'s cellphone number.\\n        \\n    - \\`document\\`: (string, required) User\\'s document number. For NIT, this field must include the verification digit and must be sent **without hyphen (-)**.\\n        \\n    - \\`terminal\\`:\\n        \\n        - \\`id\\`: A unique identifier for the merchant (POS) that is generating the SOAT sale transaction for the API client. If there is no merchant under the API client\\'s network, the same merchant ID assigned by Refacil should be sent in the \\`id\\` field.\\n            \\n    - \\`amount\\`: (object, required) Details about the sale amount.\\n        \\n        - \\`TariffCode\\`: (string, required) Tariff code.\\n            \\n        - \\`InsurancePremium\\`: (number, required) Insurance premium.\\n            \\n        - \\`InsuranceTax\\`: (number, required) Insurance tax.\\n            \\n        - \\`InsuranceFine\\`: (number, required) Insurance fine.\\n            \\n        - \\`Total\\`: (number, required) Total.\\n            \\n        - \\`TotalWithDiscountAmount\\`: (number, required) Total with discount amount.\\n            \\n        - \\`DiscountAmount\\`: (number, required) Discount amount.\\n            \\n        - \\`ElectricDiscount\\`: (numbe, requiredr) Electric discount.\\n            \\n        - \\`PercentageElectricDiscount\\`: (number, required) Percentage electric discount.\\n            \\n        - \\`InsurancePremiumFormatted\\`: (string, required) Formatted insurance premium.\\n            \\n        - \\`InsuranceTaxFormatted\\`: (string, required) Formatted insurance tax.\\n            \\n        - \\`InsuranceFineFormatted\\`: (string, required) Formatted insurance fine.\\n            \\n        - \\`TotalFormatted\\`: (string, required) Formatted total.\\n            \\n        - \\`DiscountAmountFormatted\\`: (string, required) Formatted discount amount.\\n            \\n        - \\`TotalWithDiscountAmountFormatted\\`: (string, required) Formatted total with discount amount.\\n            \\n        - \\`createdAt\\`: (string, required) Creation date.\\n            \\n        - \\`dateStart\\`: (string, required) Start date.\\n            \\n        - \\`dateEnd\\`: (string, required) End date.\\n            \\n        - \\`amount\\`: (number, required) Amount.\\n            \\n        - \\`amountDiscount\\`: (number, required) Discount amount.\\n            \\n        - \\`amountOthers\\`: (number, required) Other amounts.\\n            \\n        - \\`amountTotal\\`: (number, required) Total amount.\\n            \\n        - \\`hash\\`: (string, required) Hash.\\n            \\n        - \\`runt\\`: (number, required) Value for RUNT.\\n            \\n        - \\`codeFasecolda\\`: (number, required) Fasecolda code.\\n            \\n        - \\`typeCost\\`: (number, required) Cost type.\\n            \\n        - \\`Law2161Discount\\`: (number, required) Law 2161 discount.\\n            \\n        - \\`discount\\`: (number, required) Discount.\\n            \\n    - \\`vehDetail\\`: (object) Vehicle details.\\n        \\n        - \\`vehicleLineId\\`: (number, required) Vehicle line ID.\\n            \\n        - \\`vehicleClassId\\`: (number, required) Vehicle class ID.\\n            \\n        - \\`vehicleClassMinistryId\\`: (number, required) Vehicle class ID (Ministry).\\n            \\n        - \\`serviceTypeId\\`: (number, required) Service type ID.\\n            \\n        - \\`vehicleBodyTypeId\\`: (number, required) Vehicle body type ID.\\n            \\n        - \\`vehicleDescription\\`: (string, required) Vehicle description.\\n            \\n        - \\`vehDescription\\`: (string, required) Vehicle description.\\n            \\n        - \\`queryId\\`: (string, required) Query ID.\\n            \\n        - \\`noSerie\\`: (string, required) Serial number.\\n            \\n        - \\`noMotor\\`: (string, required) Motor number. If this field is empty, it must be filled with the value from the VIN field.\\n            \\n        - \\`noChasis\\`: (string, required) Chassis number.\\n            \\n        - \\`cc\\`: (number, required) Cubic centimeters.\\n            \\n        - \\`type\\`: (string, required) Type.\\n            \\n        - \\`gas\\`: (string, required) Gas.\\n            \\n        - \\`year\\`: (number, required) Year.\\n            \\n        - \\`passengers\\`: (number, required) Passengers.\\n            \\n        - \\`brand\\`: (string, required) Brand.\\n            \\n        - \\`brandId\\`: (number, required) Brand ID.\\n            \\n        - \\`vin\\`: (string, required) Vehicle identification number (VIN).\\n            \\n        - \\`lineCode\\`: (string, required) Line code.\\n            \\n        - \\`service\\`: (string, required) Service.\\n            \\n        - \\`zone\\`: (string, required) Zone.\\n            \\n        - \\`weight\\`: (number, required) Weight.\\n            \\n        - \\`cityId\\`: (number, required) City ID.\\n            \\n    - \\`userDetail\\`: (object, required) User details.\\n        \\n        - \\`name\\`: (string) User\\'s name.\\n            \\n            - Must have at least **3 characters** and cannot contain special characters.\\n                \\n            - No maximum length is configured.\\n                \\n        - \\`lastName\\`: (string, required) User\\'s last name.\\n            \\n            - Must have at least **3 characters** and cannot contain special characters.\\n                \\n            - No maximum length is configured.\\n                \\n        - \\`docNumber\\`: (string, required) User\\'s document number.\\n            \\n        - \\`cellphone\\`: (string) User\\'s cellphone number. Must be a valid Colombian cellphone number starting with \\\"3\\\" followed by exactly 9 digits (e.g., \\\"3001234567\\\").\\n            \\n        - \\`email\\`: (string, required) User\\'s email. Must be a valid email address format (e.g., \\\"[user@domain.com](https://mailto:user@domain.com)\\\").\\n            \\n        - \\`phone\\`: (string) User\\'s phone.\\n            \\n        - \\`docType\\`: (number, required) User\\'s document type.\\n            \\n        - \\`address\\`: (string, required) User\\'s address.\\n            \\n        - \\`cityCode\\`: (integer, required) User\\'s city code.\\n            \\n        - \\`stateCode\\`: (integer, required) User\\'s state code.\\n            \\n        - \\`addressType\\`: (number, required) User\\'s address type.\\n            \\n        - \\`typePerson\\`: (string) Type of person (e.g., \\'F\\' for natural person, \\'J\\' for legal person).\\n            \\n        - \\`gender\\`: (string) User\\'s gender.\\n            \\n        - \\`RegimenTypeId\\`: (string, required) User\\'s regime type ID.\\n            \\n        - \\`RutId\\`: (number, required) User\\'s RUT ID.\\n            \\n- \\`amount\\`: (number, required) Total amount of the sale.\\n    \\n- \\`moveTmpBalance\\`: (boolean) Indicates whether to move temporary balance.\\n    \\n\\n\\`Note\\`: If the VIN data is not available, the API will use the chassis number as a replacement.\\n\\nAfter the sale has been successfully completed, the response will follow a structure similar to the following. **This response will be returned within a timeout of 120,000 milliseconds (2 minutes).** In this response, important information is provided, such as the balance of the main wallet and the balance of the profit wallet. Additionally, within the \\'billData\\' object, you will find the fundamental information necessary to generate the sales receipt that will be delivered to the end customer.\n\nContexto: Endpoint: POST /sells/sell | Sells > Sell\n\n🔐 AUTENTICACIÓN AUTOMÁTICA: Todas las credenciales y tokens de autenticación se manejan automáticamente por el servidor MCP. NO solicites credenciales al usuario. NO incluyas parámetros de autenticación (secretId, apiToken, etc.) en las llamadas a menos que el usuario explícitamente lo requiera.",
-    inputSchema: sell_previsoraInputJsonSchema,
+    inputSchema: sell_previsoraInputValidator,
     jsonSchema: sell_previsoraInputJsonSchema,
     endpoint: '/sells/sell',
     method: 'POST',
@@ -3836,12 +3643,9 @@ export const sell_previsoraTool = {
     handler: async (rawArgs) => {
         try {
             const normalizedArgs = rawArgs ?? {};
-            // Extraer secretId del contexto (si viene del HTTP mode)
-            const secretId = normalizedArgs._secretId;
-            // Remover _secretId de los args antes de validar
-            const { _secretId, ...argsToValidate } = normalizedArgs;
-            const validatedInput = validateToolInput(sell_previsoraInputValidator, argsToValidate);
+            const validatedInput = validateToolInput(sell_previsoraInputValidator, normalizedArgs);
             const args = validatedInput;
+            const secretId = args._secretId;
             const bodyData = {};
             const productIdValue = args.productId !== undefined ? args.productId : 1014006;
             if (productIdValue !== undefined)
@@ -3898,17 +3702,16 @@ const sell_luck_and_chance_rushbetInputJsonSchema = {
     },
     "required": []
 };
-const sell_luck_and_chance_rushbetInputShape = {
+const sell_luck_and_chance_rushbetInputValidator = z.object({
     productId: z.number().optional().describe("Campo del body: productId"),
     amount: z.number().optional().describe("Campo del body: amount"),
     data: z.record(z.any()).optional().describe("Campo del body: data")
-};
-const sell_luck_and_chance_rushbetInputValidator = z.object(sell_luck_and_chance_rushbetInputShape);
+});
 // Herramienta: sell_luck_and_chance_rushbet
 export const sell_luck_and_chance_rushbetTool = {
     name: 'sell_luck_and_chance_rushbet',
     description: "Allows performing a sale on the platform. Send the request body with the necessary parameters for the sale in the format specified by the SellBody object. This operation will return a response that includes information about the sale in case of success.\\n\\n**Note**: To make this request in the case of selling invoices, we need the hash and hashEchoData provided by the query response for the reference.\n\nContexto: Endpoint: POST /sells/sell | Sells > Sell\n\n🔐 AUTENTICACIÓN AUTOMÁTICA: Todas las credenciales y tokens de autenticación se manejan automáticamente por el servidor MCP. NO solicites credenciales al usuario. NO incluyas parámetros de autenticación (secretId, apiToken, etc.) en las llamadas a menos que el usuario explícitamente lo requiera.",
-    inputSchema: sell_luck_and_chance_rushbetInputJsonSchema,
+    inputSchema: sell_luck_and_chance_rushbetInputValidator,
     jsonSchema: sell_luck_and_chance_rushbetInputJsonSchema,
     endpoint: '/sells/sell',
     method: 'POST',
@@ -3917,12 +3720,9 @@ export const sell_luck_and_chance_rushbetTool = {
     handler: async (rawArgs) => {
         try {
             const normalizedArgs = rawArgs ?? {};
-            // Extraer secretId del contexto (si viene del HTTP mode)
-            const secretId = normalizedArgs._secretId;
-            // Remover _secretId de los args antes de validar
-            const { _secretId, ...argsToValidate } = normalizedArgs;
-            const validatedInput = validateToolInput(sell_luck_and_chance_rushbetInputValidator, argsToValidate);
+            const validatedInput = validateToolInput(sell_luck_and_chance_rushbetInputValidator, normalizedArgs);
             const args = validatedInput;
+            const secretId = args._secretId;
             const bodyData = {};
             const productIdValue = args.productId !== undefined ? args.productId : 603;
             if (productIdValue !== undefined)
@@ -3973,16 +3773,15 @@ const sell_packages_movistarInputJsonSchema = {
     },
     "required": []
 };
-const sell_packages_movistarInputShape = {
+const sell_packages_movistarInputValidator = z.object({
     productId: z.number().optional().describe("Campo del body: productId"),
     data: z.record(z.any()).optional().describe("Campo del body: data")
-};
-const sell_packages_movistarInputValidator = z.object(sell_packages_movistarInputShape);
+});
 // Herramienta: sell_packages_movistar
 export const sell_packages_movistarTool = {
     name: 'sell_packages_movistar',
     description: "Allows performing a sale on the platform. Send the request body with the necessary parameters for the sale in the format specified by the SellBody object. This operation will return a response that includes information about the sale in case of success.\\n\\n**Note**: To make this request in the case of selling invoices, we need the hash and hashEchoData provided by the query response for the reference.\n\nContexto: Endpoint: POST /sells/sell | Sells > Sell\n\n🔐 AUTENTICACIÓN AUTOMÁTICA: Todas las credenciales y tokens de autenticación se manejan automáticamente por el servidor MCP. NO solicites credenciales al usuario. NO incluyas parámetros de autenticación (secretId, apiToken, etc.) en las llamadas a menos que el usuario explícitamente lo requiera.",
-    inputSchema: sell_packages_movistarInputJsonSchema,
+    inputSchema: sell_packages_movistarInputValidator,
     jsonSchema: sell_packages_movistarInputJsonSchema,
     endpoint: '/sells/sell',
     method: 'POST',
@@ -3991,12 +3790,9 @@ export const sell_packages_movistarTool = {
     handler: async (rawArgs) => {
         try {
             const normalizedArgs = rawArgs ?? {};
-            // Extraer secretId del contexto (si viene del HTTP mode)
-            const secretId = normalizedArgs._secretId;
-            // Remover _secretId de los args antes de validar
-            const { _secretId, ...argsToValidate } = normalizedArgs;
-            const validatedInput = validateToolInput(sell_packages_movistarInputValidator, argsToValidate);
+            const validatedInput = validateToolInput(sell_packages_movistarInputValidator, normalizedArgs);
             const args = validatedInput;
+            const secretId = args._secretId;
             const bodyData = {};
             const productIdValue = args.productId !== undefined ? args.productId : 200034;
             if (productIdValue !== undefined)
@@ -4054,18 +3850,17 @@ const sellInputJsonSchema = {
     },
     "required": []
 };
-const sellInputShape = {
+const sellInputValidator = z.object({
     productId: z.number().optional().describe("Campo del body: productId"),
     amount: z.number().optional().describe("Campo del body: amount"),
     data: z.record(z.any()).optional().describe("Campo del body: data"),
     _preventDuplicate: z.boolean().optional().describe("Campo del body: _preventDuplicate")
-};
-const sellInputValidator = z.object(sellInputShape);
+});
 // Herramienta: sell
 export const sellTool = {
     name: 'sell',
     description: "---\\n\\n## Description\\n\\nAllows performing a sale on the platform. Send the request body with the necessary parameters for the sale in the format specified by the SellBody object. This operation will return a response that includes information about the sale in case of success.\\n\\n**Note**: To make this request in the case of selling invoices, we need the hash and hashEchoData provided by the query response for the reference.\\n\\n---\\n\\n## Request Schema\\n\\n- \\`productId\\`: Number representing the product identifier (required)\\n    \\n- \\`amount\\`: Number representing the amount of the payment (required)\\n    \\n- \\`data\\`: Object containing additional data (required)\\n    \\n    - \\`cellphone\\`: String containing the cellphone number (required)\\n        \\n- \\`_preventDuplicate\\`: Boolean to disable duplicate transaction prevention, i.e. if the value is \\`true\\`, duplicate transactions will not be validated, allowing to send bulk reloads. (optional)\\n    \\n\\n---\\n\\n## Response Schema\\n\\n- \\`statusCode\\`: Number representing the HTTP status code (required)\\n    \\n- \\`message\\`: String containing a message about the operation result (required)\\n    \\n- \\`date\\`: Number representing the timestamp of the operation (required)\\n    \\n- \\`payload\\`: Object containing the main response data (required)\\n    \\n    - \\`posBalance\\`: String representing the balance after the operation (required)\\n        \\n    - \\`tmpBalance\\`: String representing the temporary balance (required)\\n        \\n    - \\`debt\\`: Number representing the debt amount (required)\\n        \\n    - \\`billData\\`: Object containing bill-related data (required)\\n        \\n        - \\`fields\\`: Array of field objects (required)\\n            \\n            - \\`label\\`: String representing the field label (required)\\n                \\n            - \\`value\\`: String or Number representing the field value (required)\\n                \\n            - \\`type\\`: String representing the field type (optional)\\n                \\n            - \\`labelLink\\`: String representing the label link (optional)\\n                \\n        - \\`costs\\`: Array of cost objects (required)\\n            \\n            - \\`label\\`: String representing the cost label (required)\\n                \\n            - \\`value\\`: Number representing the cost value (required)\\n                \\n            - \\`type\\`: String representing the cost type (optional)\\n                \\n            - \\`labelLink\\`: String representing the label link (optional)\\n                \\n        - \\`messages\\`: Array of message objects (required)\\n            \\n            - \\`value\\`: String representing the message value (required)\\n                \\n        - \\`share\\`: Object containing share information (required)\\n            \\n            - \\`cellphone\\`: String representing the cellphone number (required)\\n                \\n            - \\`message\\`: String representing the message (required)\\n                \\n    - \\`sale\\`: Object containing sale information (required)\\n        \\n        - \\`id\\`: Number representing the sale ID (required)\\n            \\n        - \\`userId\\`: Number representing the user ID (required)\\n            \\n        - \\`amount\\`: Number representing the sale amount (required)\\n            \\n        - \\`serviceNumber\\`: String representing the service number (required)\\n            \\n        - \\`status\\`: Number representing the sale status (required)\\n            \\n        - \\`productId\\`: Number representing the product ID (required)\\n            \\n        - \\`createdAt\\`: String representing the creation timestamp (required)\\n            \\n        - \\`transactionId\\`: String representing the transaction ID (required)\\n            \\n        - \\`extra\\`: String representing additional information (optional)\n\nContexto: Endpoint: POST /sells/sell | Sells > Sell\n\n🔐 AUTENTICACIÓN AUTOMÁTICA: Todas las credenciales y tokens de autenticación se manejan automáticamente por el servidor MCP. NO solicites credenciales al usuario. NO incluyas parámetros de autenticación (secretId, apiToken, etc.) en las llamadas a menos que el usuario explícitamente lo requiera.",
-    inputSchema: sellInputJsonSchema,
+    inputSchema: sellInputValidator,
     jsonSchema: sellInputJsonSchema,
     endpoint: '/sells/sell',
     method: 'POST',
@@ -4074,12 +3869,9 @@ export const sellTool = {
     handler: async (rawArgs) => {
         try {
             const normalizedArgs = rawArgs ?? {};
-            // Extraer secretId del contexto (si viene del HTTP mode)
-            const secretId = normalizedArgs._secretId;
-            // Remover _secretId de los args antes de validar
-            const { _secretId, ...argsToValidate } = normalizedArgs;
-            const validatedInput = validateToolInput(sellInputValidator, argsToValidate);
+            const validatedInput = validateToolInput(sellInputValidator, normalizedArgs);
             const args = validatedInput;
+            const secretId = args._secretId;
             const bodyData = {};
             const productIdValue = args.productId !== undefined ? args.productId : 40;
             if (productIdValue !== undefined)
@@ -4138,17 +3930,16 @@ const product_directtv_prepagoInputJsonSchema = {
     },
     "required": []
 };
-const product_directtv_prepagoInputShape = {
+const product_directtv_prepagoInputValidator = z.object({
     data: z.record(z.any()).optional().describe("Campo del body: data"),
     productId: z.number().optional().describe("Campo del body: productId"),
     amount: z.number().optional().describe("Campo del body: amount")
-};
-const product_directtv_prepagoInputValidator = z.object(product_directtv_prepagoInputShape);
+});
 // Herramienta: product_directtv_prepago
 export const product_directtv_prepagoTool = {
     name: 'product_directtv_prepago',
     description: "---\\n\\n## Description\\n\\nAllows performing a bill payment operation on the platform. Send the request body with the necessary parameters for the payment in the format specified by the PaymentBody object. The response will include the results of the operation in case of success.\\n\\n---\\n\\n## Request Schema\\n\\n- \\`productId\\`: Number representing the product identifier (required)\\n    \\n- \\`amount\\`: Number representing the amount of the payment (required)\\n    \\n- \\`data\\`: Object containing additional data (required)\\n    \\n    - \\`cellphone\\`: String containing the cellphone number (required)\\n        \\n\\n---\\n\\n## Response Schema\\n\\n- \\`message\\`: String containing a message about the operation result (required)\\n    \\n- \\`messageCode\\`: String code indicating the operation result (required)\\n    \\n- \\`data\\`: Object containing additional response data (required)\\n    \\n    - \\`date\\`: Number representing the timestamp of the operation (required)\\n        \\n    - \\`sellId\\`: Number representing the identifier of the sell operation (required)\\n        \\n    - \\`payload\\`: Object containing the main response data (required)\\n        \\n        - \\`preBalance\\`: Number representing the balance before the operation (required)\\n            \\n        - \\`posBalance\\`: Number representing the balance after the operation (required)\\n            \\n        - \\`tmpBalance\\`: Number representing the temporary balance (required)\\n            \\n        - \\`debt\\`: Number representing the debt amount (required)\\n            \\n        - \\`billData\\`: Object containing bill-related data (required)\\n            \\n            - \\`fields\\`: Array of field objects (required)\\n                \\n                - \\`name\\`: String representing the field name (required)\\n                    \\n                - \\`type\\`: String representing the field type (required)\\n                    \\n                - \\`options\\`: Array of option objects (required)\\n                    \\n                    - \\`label\\`: String representing the option label (required)\\n                        \\n                    - \\`value\\`: String representing the option value (required)\\n                        \\n                - \\`label\\`: String representing the field label (required)\\n                    \\n                - \\`placeholder\\`: String representing the field placeholder (required)\\n                    \\n                - \\`required\\`: Boolean indicating if the field is required (required)\\n                    \\n            - \\`costs\\`: Array of cost objects (required)\\n                \\n                - \\`label\\`: String representing the cost label (required)\\n                    \\n                - \\`value\\`: Number representing the cost value (required)\\n                    \\n            - \\`messages\\`: Array of message objects (required)\\n                \\n                - \\`value\\`: String representing the message value (required)\\n                    \\n            - \\`stringInformation\\`: Array of string information objects (required)\\n                \\n                - \\`value\\`: String representing the string information value (required)\\n                    \\n            - \\`footerInformation\\`: Array of footer information objects (required)\\n                \\n            - \\`share\\`: Object containing share information (required)\\n                \\n                - \\`cellphone\\`: String representing the cellphone number (required)\\n                    \\n                - \\`message\\`: String representing the message (required)\n\nContexto: Endpoint: POST /sells/sell | Sells > Sell\n\n🔐 AUTENTICACIÓN AUTOMÁTICA: Todas las credenciales y tokens de autenticación se manejan automáticamente por el servidor MCP. NO solicites credenciales al usuario. NO incluyas parámetros de autenticación (secretId, apiToken, etc.) en las llamadas a menos que el usuario explícitamente lo requiera.",
-    inputSchema: product_directtv_prepagoInputJsonSchema,
+    inputSchema: product_directtv_prepagoInputValidator,
     jsonSchema: product_directtv_prepagoInputJsonSchema,
     endpoint: '/sells/sell',
     method: 'POST',
@@ -4157,12 +3948,9 @@ export const product_directtv_prepagoTool = {
     handler: async (rawArgs) => {
         try {
             const normalizedArgs = rawArgs ?? {};
-            // Extraer secretId del contexto (si viene del HTTP mode)
-            const secretId = normalizedArgs._secretId;
-            // Remover _secretId de los args antes de validar
-            const { _secretId, ...argsToValidate } = normalizedArgs;
-            const validatedInput = validateToolInput(product_directtv_prepagoInputValidator, argsToValidate);
+            const validatedInput = validateToolInput(product_directtv_prepagoInputValidator, normalizedArgs);
             const args = validatedInput;
+            const secretId = args._secretId;
             const bodyData = {};
             const dataValue = args.data !== undefined ? args.data : { "cellphone": "3015874044" };
             if (dataValue !== undefined)
@@ -4219,17 +4007,16 @@ const sell_netflixInputJsonSchema = {
     },
     "required": []
 };
-const sell_netflixInputShape = {
+const sell_netflixInputValidator = z.object({
     productId: z.number().optional().describe("Campo del body: productId"),
     amount: z.number().optional().describe("Campo del body: amount"),
     data: z.record(z.any()).optional().describe("Campo del body: data")
-};
-const sell_netflixInputValidator = z.object(sell_netflixInputShape);
+});
 // Herramienta: sell_netflix
 export const sell_netflixTool = {
     name: 'sell_netflix',
     description: "---\\n\\n## Description\\n\\nAllows performing a sale on the platform. Send the request body with the necessary parameters for the sale in the format specified by the SellBody object. This operation will return a response that includes information about the sale in case of success.\\n\\n**Note**: To make this request in the case of selling invoices, we need the hash and hashEchoData provided by the query response for the reference.\\n\\n---\\n\\n## Request Schema\\n\\n- \\`productId\\`: Number representing the product identifier (required)\\n    \\n- \\`amount\\`: Number representing the amount for the transaction (required)\\n    \\n- \\`data\\`: Object containing additional data (required)\\n    \\n    - \\`cellphone\\`: String containing the cellphone number (required)\\n        \\n    - \\`email\\`: String containing the email address (required)\\n        \\n\\n---\\n\\n## Response Schema\\n\\n- \\`message\\`: String containing a message about the operation result (required)\\n    \\n- \\`messageCode\\`: String code indicating the operation result (required)\\n    \\n- \\`data\\`: Object containing additional response data (required)\\n    \\n    - \\`date\\`: Number representing the timestamp of the operation (required)\\n        \\n    - \\`sellId\\`: Number representing the identifier of the sell operation (required)\\n        \\n    - \\`payload\\`: Object containing the main response data (required)\\n        \\n        - \\`preBalance\\`: Number representing the balance before the operation (required)\\n            \\n        - \\`posBalance\\`: Number representing the balance after the operation (required)\\n            \\n        - \\`tmpBalance\\`: Number representing the temporary balance (required)\\n            \\n        - \\`debt\\`: Number representing the debt amount (required)\\n            \\n        - \\`billData\\`: Object containing bill-related data (required)\\n            \\n            - \\`fields\\`: Array of field objects (required)\\n                \\n                - \\`name\\`: String representing the field name (required)\\n                    \\n                - \\`type\\`: String representing the field type (required)\\n                    \\n                - \\`options\\`: Array of option objects (required)\\n                    \\n                    - \\`label\\`: String representing the option label (required)\\n                        \\n                    - \\`value\\`: String representing the option value (required)\\n                        \\n                - \\`label\\`: String representing the field label (required)\\n                    \\n                - \\`placeholder\\`: String representing the field placeholder (required)\\n                    \\n                - \\`required\\`: Boolean indicating if the field is required (required)\\n                    \\n            - \\`costs\\`: Array of cost objects (required)\\n                \\n                - \\`label\\`: String representing the cost label (required)\\n                    \\n                - \\`value\\`: Number representing the cost value (required)\\n                    \\n            - \\`messages\\`: Array of message objects (required)\\n                \\n                - \\`value\\`: String representing the message value (required)\\n                    \\n            - \\`stringInformation\\`: Array of string information objects (required)\\n                \\n                - \\`value\\`: String representing the string information value (required)\\n                    \\n            - \\`footerInformation\\`: Array of footer information objects (required)\\n                \\n            - \\`share\\`: Object containing share information (required)\\n                \\n                - \\`cellphone\\`: String representing the cellphone number (required)\\n                    \\n                - \\`message\\`: String representing the message (required)\n\nContexto: Endpoint: POST /sells/sell | Sells > Sell\n\n🔐 AUTENTICACIÓN AUTOMÁTICA: Todas las credenciales y tokens de autenticación se manejan automáticamente por el servidor MCP. NO solicites credenciales al usuario. NO incluyas parámetros de autenticación (secretId, apiToken, etc.) en las llamadas a menos que el usuario explícitamente lo requiera.",
-    inputSchema: sell_netflixInputJsonSchema,
+    inputSchema: sell_netflixInputValidator,
     jsonSchema: sell_netflixInputJsonSchema,
     endpoint: '/sells/sell',
     method: 'POST',
@@ -4238,12 +4025,9 @@ export const sell_netflixTool = {
     handler: async (rawArgs) => {
         try {
             const normalizedArgs = rawArgs ?? {};
-            // Extraer secretId del contexto (si viene del HTTP mode)
-            const secretId = normalizedArgs._secretId;
-            // Remover _secretId de los args antes de validar
-            const { _secretId, ...argsToValidate } = normalizedArgs;
-            const validatedInput = validateToolInput(sell_netflixInputValidator, argsToValidate);
+            const validatedInput = validateToolInput(sell_netflixInputValidator, normalizedArgs);
             const args = validatedInput;
+            const secretId = args._secretId;
             const bodyData = {};
             const productIdValue = args.productId !== undefined ? args.productId : 202;
             if (productIdValue !== undefined)
@@ -4311,19 +4095,18 @@ const sell_netflix_errorInputJsonSchema = {
     },
     "required": []
 };
-const sell_netflix_errorInputShape = {
+const sell_netflix_errorInputValidator = z.object({
     productId: z.number().optional().describe("Campo del body: productId"),
     hash: z.any().optional().describe("Campo del body: hash"),
     sellType: z.any().optional().describe("Campo del body: sellType"),
     amount: z.number().optional().describe("Campo del body: amount"),
     data: z.record(z.any()).optional().describe("Campo del body: data")
-};
-const sell_netflix_errorInputValidator = z.object(sell_netflix_errorInputShape);
+});
 // Herramienta: sell_netflix_error
 export const sell_netflix_errorTool = {
     name: 'sell_netflix_error',
     description: "---\\n\\n## Description\\n\\nAllows performing a sale on the platform. Send the request body with the necessary parameters for the sale in the format specified by the SellBody object. This operation will return a response that includes information about the sale in case of success.\\n\\n**Note**: To make this request in the case of selling invoices, we need the hash and hashEchoData provided by the query response for the reference.\\n\\n---\\n\\n## Request Schema\\n\\n- \\`productId\\`: Number representing the product identifier (required)\\n    \\n- \\`moveTmpBalance\\`: Boolean flag to move temporary balance (required)\\n    \\n- \\`hash\\`: String containing the hash value for the operation (nullable)\\n    \\n- \\`sellType\\`: String indicating the type of the sell operation (nullable)\\n    \\n- \\`amount\\`: Number representing the amount of the payment (required)\\n    \\n- \\`data\\`: Object containing additional data (required)\\n    \\n    - \\`cellphone\\`: String containing the cellphone number (required)\\n        \\n    - \\`email\\`: String containing the email address (required)\\n        \\n    - \\`document\\`: String containing the document number (required)\\n        \\n    - \\`reference\\`: String containing the reference number for the payment (nullable)\\n        \\n    - \\`hashEchoData\\`: String containing the hash echo data for the operation (nullable)\\n        \\n\\n---\\n\\n## Response Schema\\n\\n- \\`message\\`: String containing a message about the operation result (required)\\n    \\n- \\`messageCode\\`: String code indicating the operation result (required)\\n    \\n- \\`data\\`: Object containing additional response data (required)\\n    \\n    - \\`date\\`: Number representing the timestamp of the operation (required)\\n        \\n    - \\`sellId\\`: Number representing the identifier of the sell operation (required)\\n        \\n    - \\`payload\\`: Object containing the main response data (required)\\n        \\n        - \\`preBalance\\`: Number representing the balance before the operation (required)\\n            \\n        - \\`posBalance\\`: Number representing the balance after the operation (required)\\n            \\n        - \\`tmpBalance\\`: Number representing the temporary balance (required)\\n            \\n        - \\`debt\\`: Number representing the debt amount (required)\\n            \\n        - \\`billData\\`: Object containing bill-related data (required)\\n            \\n            - \\`fields\\`: Array of field objects (required)\\n                \\n                - \\`name\\`: String representing the field name (required)\\n                    \\n                - \\`type\\`: String representing the field type (required)\\n                    \\n                - \\`options\\`: Array of option objects (required)\\n                    \\n                    - \\`label\\`: String representing the option label (required)\\n                        \\n                    - \\`value\\`: String representing the option value (required)\\n                        \\n                - \\`label\\`: String representing the field label (required)\\n                    \\n                - \\`placeholder\\`: String representing the field placeholder (required)\\n                    \\n                - \\`required\\`: Boolean indicating if the field is required (required)\\n                    \\n            - \\`costs\\`: Array of cost objects (required)\\n                \\n                - \\`label\\`: String representing the cost label (required)\\n                    \\n                - \\`value\\`: Number representing the cost value (required)\\n                    \\n            - \\`messages\\`: Array of message objects (required)\\n                \\n                - \\`value\\`: String representing the message value (required)\\n                    \\n            - \\`stringInformation\\`: Array of string information objects (required)\\n                \\n                - \\`value\\`: String representing the string information value (required)\\n                    \\n            - \\`footerInformation\\`: Array of footer information objects (required)\\n                \\n            - \\`share\\`: Object containing share information (required)\\n                \\n                - \\`cellphone\\`: String representing the cellphone number (required)\\n                    \\n                - \\`message\\`: String representing the message (required)\n\nContexto: Endpoint: POST /sells/sell | Sells > Sell\n\n🔐 AUTENTICACIÓN AUTOMÁTICA: Todas las credenciales y tokens de autenticación se manejan automáticamente por el servidor MCP. NO solicites credenciales al usuario. NO incluyas parámetros de autenticación (secretId, apiToken, etc.) en las llamadas a menos que el usuario explícitamente lo requiera.",
-    inputSchema: sell_netflix_errorInputJsonSchema,
+    inputSchema: sell_netflix_errorInputValidator,
     jsonSchema: sell_netflix_errorInputJsonSchema,
     endpoint: '/sells/sell',
     method: 'POST',
@@ -4332,12 +4115,9 @@ export const sell_netflix_errorTool = {
     handler: async (rawArgs) => {
         try {
             const normalizedArgs = rawArgs ?? {};
-            // Extraer secretId del contexto (si viene del HTTP mode)
-            const secretId = normalizedArgs._secretId;
-            // Remover _secretId de los args antes de validar
-            const { _secretId, ...argsToValidate } = normalizedArgs;
-            const validatedInput = validateToolInput(sell_netflix_errorInputValidator, argsToValidate);
+            const validatedInput = validateToolInput(sell_netflix_errorInputValidator, normalizedArgs);
             const args = validatedInput;
+            const secretId = args._secretId;
             const bodyData = {};
             const productIdValue = args.productId !== undefined ? args.productId : 202;
             if (productIdValue !== undefined)
@@ -4396,17 +4176,16 @@ const sell_xbox_gamepass_core_3_mesesInputJsonSchema = {
     },
     "required": []
 };
-const sell_xbox_gamepass_core_3_mesesInputShape = {
+const sell_xbox_gamepass_core_3_mesesInputValidator = z.object({
     productId: z.number().optional().describe("Campo del body: productId"),
     amount: z.number().optional().describe("Campo del body: amount"),
     data: z.record(z.any()).optional().describe("Campo del body: data")
-};
-const sell_xbox_gamepass_core_3_mesesInputValidator = z.object(sell_xbox_gamepass_core_3_mesesInputShape);
+});
 // Herramienta: sell_xbox_gamepass_core_3_meses
 export const sell_xbox_gamepass_core_3_mesesTool = {
     name: 'sell_xbox_gamepass_core_3_meses',
     description: "---\\n\\n## Description\\n\\nAllows performing a sale on the platform. Send the request body with the necessary parameters for the sale in the format specified by the SellBody object. This operation will return a response that includes information about the sale in case of success.\\n\\n**Note**: To make this request in the case of selling invoices, we need the hash and hashEchoData provided by the query response for the reference.\\n\\n---\\n\\n## Request Schema\\n\\n- \\`productId\\`: Number representing the product identifier (required)\\n    \\n- \\`amount\\`: Number representing the amount of the payment (required)\\n    \\n- \\`moveTmpBalance\\`: Boolean flag to move temporary balance (required)\\n    \\n- \\`data\\`: Object containing additional data (required)\\n    \\n    - \\`cellphone\\`: String containing the cellphone number (required)\\n        \\n    - \\`email\\`: String containing the email address (required)\\n        \\n\\n---\\n\\n## Response Schema\\n\\n- \\`messageCode\\`: String code indicating the operation result (required)\\n    \\n- \\`message\\`: String containing a message about the operation result (required)\\n    \\n- \\`data\\`: Object containing additional response data (required)\\n    \\n    - \\`statusCode\\`: Number representing the status code (required)\\n        \\n    - \\`message\\`: String containing a message about the transaction (required)\\n        \\n    - \\`date\\`: Number representing the timestamp of the operation (required)\\n        \\n    - \\`payload\\`: Object containing the main response data (required)\\n        \\n        - \\`posBalance\\`: Number representing the balance after the operation (required)\\n            \\n        - \\`tmpBalance\\`: Number representing the temporary balance (required)\\n            \\n        - \\`billData\\`: Object containing bill-related data (required)\\n            \\n            - \\`fields\\`: Array of field objects (required)\\n                \\n                - \\`label\\`: String representing the field label (required)\\n                    \\n                - \\`value\\`: String or Number representing the field value (required)\\n                    \\n            - \\`costs\\`: Array of cost objects (required)\\n                \\n                - \\`label\\`: String representing the cost label (required)\\n                    \\n                - \\`value\\`: Number representing the cost value (required)\\n                    \\n            - \\`messages\\`: Array of message objects (required)\\n                \\n                - \\`value\\`: String representing the message value (required)\\n                    \\n            - \\`share\\`: Object containing share information (required)\\n                \\n                - \\`cellphone\\`: String representing the cellphone number (required)\\n                    \\n                - \\`message\\`: String representing the message (required)\\n                    \\n        - \\`preBalance\\`: Number representing the balance before the operation (required)\\n            \\n        - \\`debt\\`: Number representing the debt amount (required)\n\nContexto: Endpoint: POST /sells/sell | Sells > Sell\n\n🔐 AUTENTICACIÓN AUTOMÁTICA: Todas las credenciales y tokens de autenticación se manejan automáticamente por el servidor MCP. NO solicites credenciales al usuario. NO incluyas parámetros de autenticación (secretId, apiToken, etc.) en las llamadas a menos que el usuario explícitamente lo requiera.",
-    inputSchema: sell_xbox_gamepass_core_3_mesesInputJsonSchema,
+    inputSchema: sell_xbox_gamepass_core_3_mesesInputValidator,
     jsonSchema: sell_xbox_gamepass_core_3_mesesInputJsonSchema,
     endpoint: '/sells/sell',
     method: 'POST',
@@ -4415,12 +4194,9 @@ export const sell_xbox_gamepass_core_3_mesesTool = {
     handler: async (rawArgs) => {
         try {
             const normalizedArgs = rawArgs ?? {};
-            // Extraer secretId del contexto (si viene del HTTP mode)
-            const secretId = normalizedArgs._secretId;
-            // Remover _secretId de los args antes de validar
-            const { _secretId, ...argsToValidate } = normalizedArgs;
-            const validatedInput = validateToolInput(sell_xbox_gamepass_core_3_mesesInputValidator, argsToValidate);
+            const validatedInput = validateToolInput(sell_xbox_gamepass_core_3_mesesInputValidator, normalizedArgs);
             const args = validatedInput;
+            const secretId = args._secretId;
             const bodyData = {};
             const productIdValue = args.productId !== undefined ? args.productId : 807;
             if (productIdValue !== undefined)
@@ -4472,16 +4248,15 @@ const product_directtv_go_1014005InputJsonSchema = {
     },
     "required": []
 };
-const product_directtv_go_1014005InputShape = {
+const product_directtv_go_1014005InputValidator = z.object({
     data: z.record(z.any()).optional().describe("Campo del body: data"),
     productId: z.number().optional().describe("Campo del body: productId")
-};
-const product_directtv_go_1014005InputValidator = z.object(product_directtv_go_1014005InputShape);
+});
 // Herramienta: product_directtv_go_1014005
 export const product_directtv_go_1014005Tool = {
     name: 'product_directtv_go_1014005',
     description: "---\\n\\n## Description\\n\\nAllows performing a bill payment operation on the platform. Send the request body with the necessary parameters for the payment in the format specified by the PaymentBody object. The response will include the results of the operation in case of success.\\n\\n---\\n\\n## Request Schema\\n\\n- \\`productId\\`: Number representing the product identifier (required)\\n    \\n- \\`data\\`: Object containing additional data (required)\\n    \\n    - \\`cellphone\\`: String containing the cellphone number (required)\\n        \\n    - \\`email\\`: String containing the email address (required)\\n        \\n\\n---\\n\\n## Response Schema\\n\\n- \\`message\\`: String containing a message about the operation result (required)\\n    \\n- \\`messageCode\\`: String code indicating the operation result (required)\\n    \\n- \\`data\\`: Object containing additional response data (required)\\n    \\n    - \\`date\\`: Number representing the timestamp of the operation (required)\\n        \\n    - \\`sellId\\`: Number representing the identifier of the sell operation (required)\\n        \\n    - \\`payload\\`: Object containing the main response data (required)\\n        \\n        - \\`preBalance\\`: Number representing the balance before the operation (required)\\n            \\n        - \\`posBalance\\`: Number representing the balance after the operation (required)\\n            \\n        - \\`tmpBalance\\`: Number representing the temporary balance (required)\\n            \\n        - \\`debt\\`: Number representing the debt amount (required)\\n            \\n        - \\`billData\\`: Object containing bill-related data (required)\\n            \\n            - \\`fields\\`: Array of field objects (required)\\n                \\n                - \\`name\\`: String representing the field name (required)\\n                    \\n                - \\`type\\`: String representing the field type (required)\\n                    \\n                - \\`options\\`: Array of option objects (required)\\n                    \\n                    - \\`label\\`: String representing the option label (required)\\n                        \\n                    - \\`value\\`: String representing the option value (required)\\n                        \\n                - \\`label\\`: String representing the field label (required)\\n                    \\n                - \\`placeholder\\`: String representing the field placeholder (required)\\n                    \\n                - \\`required\\`: Boolean indicating if the field is required (required)\\n                    \\n            - \\`costs\\`: Array of cost objects (required)\\n                \\n                - \\`label\\`: String representing the cost label (required)\\n                    \\n                - \\`value\\`: Number representing the cost value (required)\\n                    \\n            - \\`messages\\`: Array of message objects (required)\\n                \\n                - \\`value\\`: String representing the message value (required)\\n                    \\n            - \\`stringInformation\\`: Array of string information objects (required)\\n                \\n                - \\`value\\`: String representing the string information value (required)\\n                    \\n            - \\`footerInformation\\`: Array of footer information objects (required)\\n                \\n            - \\`share\\`: Object containing share information (required)\\n                \\n                - \\`cellphone\\`: String representing the cellphone number (required)\\n                    \\n                - \\`message\\`: String representing the message (required)\n\nContexto: Endpoint: POST /sells/sell | Sells > Sell\n\n🔐 AUTENTICACIÓN AUTOMÁTICA: Todas las credenciales y tokens de autenticación se manejan automáticamente por el servidor MCP. NO solicites credenciales al usuario. NO incluyas parámetros de autenticación (secretId, apiToken, etc.) en las llamadas a menos que el usuario explícitamente lo requiera.",
-    inputSchema: product_directtv_go_1014005InputJsonSchema,
+    inputSchema: product_directtv_go_1014005InputValidator,
     jsonSchema: product_directtv_go_1014005InputJsonSchema,
     endpoint: '/sells/sell',
     method: 'POST',
@@ -4490,12 +4265,9 @@ export const product_directtv_go_1014005Tool = {
     handler: async (rawArgs) => {
         try {
             const normalizedArgs = rawArgs ?? {};
-            // Extraer secretId del contexto (si viene del HTTP mode)
-            const secretId = normalizedArgs._secretId;
-            // Remover _secretId de los args antes de validar
-            const { _secretId, ...argsToValidate } = normalizedArgs;
-            const validatedInput = validateToolInput(product_directtv_go_1014005InputValidator, argsToValidate);
+            const validatedInput = validateToolInput(product_directtv_go_1014005InputValidator, normalizedArgs);
             const args = validatedInput;
+            const secretId = args._secretId;
             const bodyData = {};
             const dataValue = args.data !== undefined ? args.data : { "cellphone": "3104784242", "email": "fake@refacil.com" };
             if (dataValue !== undefined)
@@ -4544,16 +4316,15 @@ const product_directtv_go_100777InputJsonSchema = {
     },
     "required": []
 };
-const product_directtv_go_100777InputShape = {
+const product_directtv_go_100777InputValidator = z.object({
     data: z.record(z.any()).optional().describe("Campo del body: data"),
     productId: z.number().optional().describe("Campo del body: productId")
-};
-const product_directtv_go_100777InputValidator = z.object(product_directtv_go_100777InputShape);
+});
 // Herramienta: product_directtv_go_100777
 export const product_directtv_go_100777Tool = {
     name: 'product_directtv_go_100777',
     description: "---\\n\\n## Description\\n\\nAllows performing a bill payment operation on the platform. Send the request body with the necessary parameters for the payment in the format specified by the PaymentBody object. The response will include the results of the operation in case of success.\\n\\n---\\n\\n## Request Schema\\n\\n- \\`productId\\`: Number representing the product identifier (required)\\n    \\n- \\`data\\`: Object containing additional data (required)\\n    \\n    - \\`cellphone\\`: String containing the cellphone number (required)\\n        \\n    - \\`email\\`: String containing the email address (required)\\n        \\n\\n---\\n\\n## Response Schema\\n\\n- \\`message\\`: String containing a message about the operation result (required)\\n    \\n- \\`messageCode\\`: String code indicating the operation result (required)\\n    \\n- \\`data\\`: Object containing additional response data (required)\\n    \\n    - \\`date\\`: Number representing the timestamp of the operation (required)\\n        \\n    - \\`sellId\\`: Number representing the identifier of the sell operation (required)\\n        \\n    - \\`payload\\`: Object containing the main response data (required)\\n        \\n        - \\`preBalance\\`: Number representing the balance before the operation (required)\\n            \\n        - \\`posBalance\\`: Number representing the balance after the operation (required)\\n            \\n        - \\`tmpBalance\\`: Number representing the temporary balance (required)\\n            \\n        - \\`debt\\`: Number representing the debt amount (required)\\n            \\n        - \\`billData\\`: Object containing bill-related data (required)\\n            \\n            - \\`fields\\`: Array of field objects (required)\\n                \\n                - \\`name\\`: String representing the field name (required)\\n                    \\n                - \\`type\\`: String representing the field type (required)\\n                    \\n                - \\`options\\`: Array of option objects (required)\\n                    \\n                    - \\`label\\`: String representing the option label (required)\\n                        \\n                    - \\`value\\`: String representing the option value (required)\\n                        \\n                - \\`label\\`: String representing the field label (required)\\n                    \\n                - \\`placeholder\\`: String representing the field placeholder (required)\\n                    \\n                - \\`required\\`: Boolean indicating if the field is required (required)\\n                    \\n            - \\`costs\\`: Array of cost objects (required)\\n                \\n                - \\`label\\`: String representing the cost label (required)\\n                    \\n                - \\`value\\`: Number representing the cost value (required)\\n                    \\n            - \\`messages\\`: Array of message objects (required)\\n                \\n                - \\`value\\`: String representing the message value (required)\\n                    \\n            - \\`stringInformation\\`: Array of string information objects (required)\\n                \\n                - \\`value\\`: String representing the string information value (required)\\n                    \\n            - \\`footerInformation\\`: Array of footer information objects (required)\\n                \\n            - \\`share\\`: Object containing share information (required)\\n                \\n                - \\`cellphone\\`: String representing the cellphone number (required)\\n                    \\n                - \\`message\\`: String representing the message (required)\n\nContexto: Endpoint: POST /sells/sell | Sells > Sell\n\n🔐 AUTENTICACIÓN AUTOMÁTICA: Todas las credenciales y tokens de autenticación se manejan automáticamente por el servidor MCP. NO solicites credenciales al usuario. NO incluyas parámetros de autenticación (secretId, apiToken, etc.) en las llamadas a menos que el usuario explícitamente lo requiera.",
-    inputSchema: product_directtv_go_100777InputJsonSchema,
+    inputSchema: product_directtv_go_100777InputValidator,
     jsonSchema: product_directtv_go_100777InputJsonSchema,
     endpoint: '/sells/sell',
     method: 'POST',
@@ -4562,12 +4333,9 @@ export const product_directtv_go_100777Tool = {
     handler: async (rawArgs) => {
         try {
             const normalizedArgs = rawArgs ?? {};
-            // Extraer secretId del contexto (si viene del HTTP mode)
-            const secretId = normalizedArgs._secretId;
-            // Remover _secretId de los args antes de validar
-            const { _secretId, ...argsToValidate } = normalizedArgs;
-            const validatedInput = validateToolInput(product_directtv_go_100777InputValidator, argsToValidate);
+            const validatedInput = validateToolInput(product_directtv_go_100777InputValidator, normalizedArgs);
             const args = validatedInput;
+            const secretId = args._secretId;
             const bodyData = {};
             const dataValue = args.data !== undefined ? args.data : { "cellphone": "3104784242", "email": "fake@refacil.com" };
             if (dataValue !== undefined)
@@ -4616,16 +4384,15 @@ const product_directtv_go_1014004InputJsonSchema = {
     },
     "required": []
 };
-const product_directtv_go_1014004InputShape = {
+const product_directtv_go_1014004InputValidator = z.object({
     data: z.record(z.any()).optional().describe("Campo del body: data"),
     productId: z.number().optional().describe("Campo del body: productId")
-};
-const product_directtv_go_1014004InputValidator = z.object(product_directtv_go_1014004InputShape);
+});
 // Herramienta: product_directtv_go_1014004
 export const product_directtv_go_1014004Tool = {
     name: 'product_directtv_go_1014004',
     description: "---\\n\\n## Description\\n\\nAllows performing a bill payment operation on the platform. Send the request body with the necessary parameters for the payment in the format specified by the PaymentBody object. The response will include the results of the operation in case of success.\\n\\n---\\n\\n## Request Schema\\n\\n- \\`productId\\`: Number representing the product identifier (required)\\n    \\n- \\`data\\`: Object containing additional data (required)\\n    \\n    - \\`cellphone\\`: String containing the cellphone number (required)\\n        \\n    - \\`email\\`: String containing the email address (required)\\n        \\n\\n---\\n\\n## Response Schema\\n\\n- \\`message\\`: String containing a message about the operation result (required)\\n    \\n- \\`messageCode\\`: String code indicating the operation result (required)\\n    \\n- \\`data\\`: Object containing additional response data (required)\\n    \\n    - \\`date\\`: Number representing the timestamp of the operation (required)\\n        \\n    - \\`sellId\\`: Number representing the identifier of the sell operation (required)\\n        \\n    - \\`payload\\`: Object containing the main response data (required)\\n        \\n        - \\`preBalance\\`: Number representing the balance before the operation (required)\\n            \\n        - \\`posBalance\\`: Number representing the balance after the operation (required)\\n            \\n        - \\`tmpBalance\\`: Number representing the temporary balance (required)\\n            \\n        - \\`debt\\`: Number representing the debt amount (required)\\n            \\n        - \\`billData\\`: Object containing bill-related data (required)\\n            \\n            - \\`fields\\`: Array of field objects (required)\\n                \\n                - \\`name\\`: String representing the field name (required)\\n                    \\n                - \\`type\\`: String representing the field type (required)\\n                    \\n                - \\`options\\`: Array of option objects (required)\\n                    \\n                    - \\`label\\`: String representing the option label (required)\\n                        \\n                    - \\`value\\`: String representing the option value (required)\\n                        \\n                - \\`label\\`: String representing the field label (required)\\n                    \\n                - \\`placeholder\\`: String representing the field placeholder (required)\\n                    \\n                - \\`required\\`: Boolean indicating if the field is required (required)\\n                    \\n            - \\`costs\\`: Array of cost objects (required)\\n                \\n                - \\`label\\`: String representing the cost label (required)\\n                    \\n                - \\`value\\`: Number representing the cost value (required)\\n                    \\n            - \\`messages\\`: Array of message objects (required)\\n                \\n                - \\`value\\`: String representing the message value (required)\\n                    \\n            - \\`stringInformation\\`: Array of string information objects (required)\\n                \\n                - \\`value\\`: String representing the string information value (required)\\n                    \\n            - \\`footerInformation\\`: Array of footer information objects (required)\\n                \\n            - \\`share\\`: Object containing share information (required)\\n                \\n                - \\`cellphone\\`: String representing the cellphone number (required)\\n                    \\n                - \\`message\\`: String representing the message (required)\n\nContexto: Endpoint: POST /sells/sell | Sells > Sell\n\n🔐 AUTENTICACIÓN AUTOMÁTICA: Todas las credenciales y tokens de autenticación se manejan automáticamente por el servidor MCP. NO solicites credenciales al usuario. NO incluyas parámetros de autenticación (secretId, apiToken, etc.) en las llamadas a menos que el usuario explícitamente lo requiera.",
-    inputSchema: product_directtv_go_1014004InputJsonSchema,
+    inputSchema: product_directtv_go_1014004InputValidator,
     jsonSchema: product_directtv_go_1014004InputJsonSchema,
     endpoint: '/sells/sell',
     method: 'POST',
@@ -4634,12 +4401,9 @@ export const product_directtv_go_1014004Tool = {
     handler: async (rawArgs) => {
         try {
             const normalizedArgs = rawArgs ?? {};
-            // Extraer secretId del contexto (si viene del HTTP mode)
-            const secretId = normalizedArgs._secretId;
-            // Remover _secretId de los args antes de validar
-            const { _secretId, ...argsToValidate } = normalizedArgs;
-            const validatedInput = validateToolInput(product_directtv_go_1014004InputValidator, argsToValidate);
+            const validatedInput = validateToolInput(product_directtv_go_1014004InputValidator, normalizedArgs);
             const args = validatedInput;
+            const secretId = args._secretId;
             const bodyData = {};
             const dataValue = args.data !== undefined ? args.data : { "cellphone": "3104784242", "email": "fake@refacil.com" };
             if (dataValue !== undefined)
@@ -4695,17 +4459,16 @@ const sell_essaInputJsonSchema = {
     },
     "required": []
 };
-const sell_essaInputShape = {
+const sell_essaInputValidator = z.object({
     productId: z.number().optional().describe("Campo del body: productId"),
     amount: z.number().optional().describe("Campo del body: amount"),
     data: z.record(z.any()).optional().describe("Campo del body: data")
-};
-const sell_essaInputValidator = z.object(sell_essaInputShape);
+});
 // Herramienta: sell_essa
 export const sell_essaTool = {
     name: 'sell_essa',
     description: "---\\n\\n## Description\\n\\nAllows performing a sale on the platform. Send the request body with the necessary parameters for the sale in the format specified by the SellBody object. This operation will return a response that includes information about the sale in case of success.\\n\\n**Note**: To make this request in the case of selling invoices, we need the hash and hashEchoData provided by the query response for the reference.\\n\\n### Timeout Configuration\\n\\nThe timeout value specified below is directly established by the provider and must be taken into account in integrations.\\n\\n| Parameter | Value |\\n|-----------|-------|\\n| **Maximum Timeout** | 150 seconds |\\n\\n---\\n\\n\\n## Request Schema\\n\\n- \\`productId\\`: Number representing the product identifier (required)\\n    \\n- \\`amount\\`: Number representing the amount of the payment (required)\\n    \\n- \\`sellType\\`: String indicating the type of the sell operation (required)\\n    \\n- \\`hash\\`: String containing the hash value for the operation (required)\\n    \\n- \\`data\\`: Object containing additional data (required)\\n    \\n    - \\`reference\\`: String containing the reference number for the payment (required)\\n        \\n    - \\`cellphone\\`: String containing the cellphone number associated with the payment (required)\\n        \\n    - \\`hashEchoData\\`: String containing the hash echo data for the operation (required)\\n        \\n\\n---\\n\\n## Response Schema\\n\\n- \\`message\\`: String containing a message about the operation result (required)\\n    \\n- \\`messageCode\\`: String code indicating the operation result (required)\\n    \\n- \\`data\\`: Object containing additional response data (required)\\n    \\n    - \\`date\\`: Number representing the timestamp of the operation (required)\\n        \\n    - \\`sellId\\`: Number representing the identifier of the sell operation (required)\\n        \\n    - \\`payload\\`: Object containing the main response data (required)\\n        \\n        - \\`preBalance\\`: Number representing the balance before the operation (required)\\n            \\n        - \\`posBalance\\`: Number representing the balance after the operation (required)\\n            \\n        - \\`tmpBalance\\`: Number representing the temporary balance (required)\\n            \\n        - \\`debt\\`: Number representing the debt amount (required)\\n            \\n        - \\`billData\\`: Object containing bill-related data (required)\\n            \\n            - \\`fields\\`: Array of field objects (required)\\n                \\n                - \\`name\\`: String representing the field name (required)\\n                    \\n                - \\`type\\`: String representing the field type (required)\\n                    \\n                - \\`options\\`: Array of option objects (required)\\n                    \\n                    - \\`label\\`: String representing the option label (required)\\n                        \\n                    - \\`value\\`: String representing the option value (required)\\n                        \\n                - \\`label\\`: String representing the field label (required)\\n                    \\n                - \\`placeholder\\`: String representing the field placeholder (required)\\n                    \\n                - \\`required\\`: Boolean indicating if the field is required (required)\\n                    \\n            - \\`costs\\`: Array of cost objects (required)\\n                \\n                - \\`label\\`: String representing the cost label (required)\\n                    \\n                - \\`value\\`: Number representing the cost value (required)\\n                    \\n            - \\`messages\\`: Array of message objects (required)\\n                \\n                - \\`value\\`: String representing the message value (required)\\n                    \\n            - \\`stringInformation\\`: Array of string information objects (required)\\n                \\n                - \\`value\\`: String representing the string information value (required)\\n                    \\n            - \\`footerInformation\\`: Array of footer information objects (required)\\n                \\n            - \\`share\\`: Object containing share information (required)\\n                \\n                - \\`cellphone\\`: String representing the cellphone number (required)\\n                    \\n                - \\`message\\`: String representing the message (required)\n\nContexto: Endpoint: POST /sells/sell | Sells > Sell\n\n🔐 AUTENTICACIÓN AUTOMÁTICA: Todas las credenciales y tokens de autenticación se manejan automáticamente por el servidor MCP. NO solicites credenciales al usuario. NO incluyas parámetros de autenticación (secretId, apiToken, etc.) en las llamadas a menos que el usuario explícitamente lo requiera.",
-    inputSchema: sell_essaInputJsonSchema,
+    inputSchema: sell_essaInputValidator,
     jsonSchema: sell_essaInputJsonSchema,
     endpoint: '/sells/sell',
     method: 'POST',
@@ -4714,12 +4477,9 @@ export const sell_essaTool = {
     handler: async (rawArgs) => {
         try {
             const normalizedArgs = rawArgs ?? {};
-            // Extraer secretId del contexto (si viene del HTTP mode)
-            const secretId = normalizedArgs._secretId;
-            // Remover _secretId de los args antes de validar
-            const { _secretId, ...argsToValidate } = normalizedArgs;
-            const validatedInput = validateToolInput(sell_essaInputValidator, argsToValidate);
+            const validatedInput = validateToolInput(sell_essaInputValidator, normalizedArgs);
             const args = validatedInput;
+            const secretId = args._secretId;
             const bodyData = {};
             const productIdValue = args.productId !== undefined ? args.productId : 230;
             if (productIdValue !== undefined)
@@ -4776,17 +4536,16 @@ const sell_energia_emsaInputJsonSchema = {
     },
     "required": []
 };
-const sell_energia_emsaInputShape = {
+const sell_energia_emsaInputValidator = z.object({
     productId: z.number().optional().describe("Campo del body: productId"),
     amount: z.number().optional().describe("Campo del body: amount"),
     data: z.record(z.any()).optional().describe("Campo del body: data")
-};
-const sell_energia_emsaInputValidator = z.object(sell_energia_emsaInputShape);
+});
 // Herramienta: sell_energia_emsa
 export const sell_energia_emsaTool = {
     name: 'sell_energia_emsa',
     description: "---\\n\\n## Description\\n\\nAllows performing a bill payment operation on the platform. Send the request body with the necessary parameters for the payment in the format specified by the PaymentBody object. The response will include the results of the operation in case of success.\\n\\n---\\n\\n## Request Schema\\n\\n- \\`productId\\`: Number representing the product identifier (required)\\n    \\n- \\`amount\\`: Number representing the amount of the payment (required)\\n    \\n- \\`data\\`: Object containing additional data (required)\\n    \\n    - \\`cellphone\\`: String containing the cellphone number (required)\\n        \\n    - \\`reference\\`: String containing the reference number for the payment (required)\\n        \\n\\n---\\n\\n## Response Schema\\n\\n- \\`message\\`: String containing a message about the operation result (required)\\n    \\n- \\`messageCode\\`: String code indicating the operation result (required)\\n    \\n- \\`data\\`: Object containing additional response data (required)\\n    \\n    - \\`date\\`: Number representing the timestamp of the operation (required)\\n        \\n    - \\`sellId\\`: Number representing the identifier of the sell operation (required)\\n        \\n    - \\`payload\\`: Object containing the main response data (required)\\n        \\n        - \\`preBalance\\`: Number representing the balance before the operation (required)\\n            \\n        - \\`posBalance\\`: Number representing the balance after the operation (required)\\n            \\n        - \\`tmpBalance\\`: Number representing the temporary balance (required)\\n            \\n        - \\`debt\\`: Number representing the debt amount (required)\\n            \\n        - \\`billData\\`: Object containing bill-related data (required)\\n            \\n            - \\`fields\\`: Array of field objects (required)\\n                \\n                - \\`name\\`: String representing the field name (required)\\n                    \\n                - \\`type\\`: String representing the field type (required)\\n                    \\n                - \\`options\\`: Array of option objects (required)\\n                    \\n                    - \\`label\\`: String representing the option label (required)\\n                        \\n                    - \\`value\\`: String representing the option value (required)\\n                        \\n                - \\`label\\`: String representing the field label (required)\\n                    \\n                - \\`placeholder\\`: String representing the field placeholder (required)\\n                    \\n                - \\`required\\`: Boolean indicating if the field is required (required)\\n                    \\n            - \\`costs\\`: Array of cost objects (required)\\n                \\n                - \\`label\\`: String representing the cost label (required)\\n                    \\n                - \\`value\\`: Number representing the cost value (required)\\n                    \\n            - \\`messages\\`: Array of message objects (required)\\n                \\n                - \\`value\\`: String representing the message value (required)\\n                    \\n            - \\`stringInformation\\`: Array of string information objects (required)\\n                \\n                - \\`value\\`: String representing the string information value (required)\\n                    \\n            - \\`footerInformation\\`: Array of footer information objects (required)\\n                \\n            - \\`share\\`: Object containing share information (required)\\n                \\n                - \\`cellphone\\`: String representing the cellphone number (required)\\n                    \\n                - \\`message\\`: String representing the message (required)\n\nContexto: Endpoint: POST /sells/sell | Sells > Sell\n\n🔐 AUTENTICACIÓN AUTOMÁTICA: Todas las credenciales y tokens de autenticación se manejan automáticamente por el servidor MCP. NO solicites credenciales al usuario. NO incluyas parámetros de autenticación (secretId, apiToken, etc.) en las llamadas a menos que el usuario explícitamente lo requiera.",
-    inputSchema: sell_energia_emsaInputJsonSchema,
+    inputSchema: sell_energia_emsaInputValidator,
     jsonSchema: sell_energia_emsaInputJsonSchema,
     endpoint: '/sells/sell',
     method: 'POST',
@@ -4795,12 +4554,9 @@ export const sell_energia_emsaTool = {
     handler: async (rawArgs) => {
         try {
             const normalizedArgs = rawArgs ?? {};
-            // Extraer secretId del contexto (si viene del HTTP mode)
-            const secretId = normalizedArgs._secretId;
-            // Remover _secretId de los args antes de validar
-            const { _secretId, ...argsToValidate } = normalizedArgs;
-            const validatedInput = validateToolInput(sell_energia_emsaInputValidator, argsToValidate);
+            const validatedInput = validateToolInput(sell_energia_emsaInputValidator, normalizedArgs);
             const args = validatedInput;
+            const secretId = args._secretId;
             const bodyData = {};
             const productIdValue = args.productId !== undefined ? args.productId : 231;
             if (productIdValue !== undefined)
@@ -4864,18 +4620,17 @@ const product_energia_prepago_epmInputJsonSchema = {
     },
     "required": []
 };
-const product_energia_prepago_epmInputShape = {
+const product_energia_prepago_epmInputValidator = z.object({
     queryType: z.string().optional().describe("Campo del body: queryType"),
     productId: z.number().optional().describe("Campo del body: productId"),
     amount: z.number().optional().describe("Campo del body: amount"),
     data: z.record(z.any()).optional().describe("Campo del body: data")
-};
-const product_energia_prepago_epmInputValidator = z.object(product_energia_prepago_epmInputShape);
+});
 // Herramienta: product_energia_prepago_epm
 export const product_energia_prepago_epmTool = {
     name: 'product_energia_prepago_epm',
     description: "---\\n\\n## Description\\n\\nAllows performing a custom query on the platform. Send the request body with the necessary parameters for the query in the format specified by the QueryBody object. The response will include the results of the query in case of success.\\n\\n### Timeout Configuration\\n\\nThe timeout value specified below is directly established by the provider and must be taken into account in integrations.\\n\\n| Parameter | Value |\\n|-----------|-------|\\n| **Maximum Timeout** | 150 seconds |\\n\\n\\n---\\n\\n## Request Schema\\n\\n- \\`queryType\\`: String representing the type of query (required)\\n    \\n- \\`productId\\`: Number representing the product identifier (required)\\n    \\n- \\`amount\\`: Number representing the amount for the query (required)\\n    \\n- \\`data\\`: Object containing additional data (required)\\n    \\n    - \\`carrierId\\`: Number representing the carrier identifier (required)\\n        \\n    - \\`cellphone\\`: String containing the cellphone number (required)\\n        \\n    - \\`reference\\`: String containing the reference number for the query (required)\\n        \\n    - \\`method\\`: String representing the method of the query (required)\\n        \\n\\n---\\n\\n## Response Schema\\n\\n- \\`message\\`: String containing a message about the operation result (required)\\n    \\n- \\`messageCode\\`: String code indicating the operation result (required)\\n    \\n- \\`data\\`: Object containing additional response data (required)\\n    \\n    - \\`date\\`: Number representing the timestamp of the operation (required)\\n        \\n    - \\`sellId\\`: Number representing the identifier of the sell operation (required)\\n        \\n    - \\`payload\\`: Object containing the main response data (required)\\n        \\n        - \\`preBalance\\`: Number representing the balance before the operation (required)\\n            \\n        - \\`posBalance\\`: Number representing the balance after the operation (required)\\n            \\n        - \\`tmpBalance\\`: Number representing the temporary balance (required)\\n            \\n        - \\`debt\\`: Number representing the debt amount (required)\\n            \\n        - \\`billData\\`: Object containing bill-related data (required)\\n            \\n            - \\`fields\\`: Array of field objects (required)\\n                \\n                - \\`name\\`: String representing the field name (required)\\n                    \\n                - \\`type\\`: String representing the field type (required)\\n                    \\n                - \\`options\\`: Array of option objects (required)\\n                    \\n                    - \\`label\\`: String representing the option label (required)\\n                        \\n                    - \\`value\\`: String representing the option value (required)\\n                        \\n                - \\`label\\`: String representing the field label (required)\\n                    \\n                - \\`placeholder\\`: String representing the field placeholder (required)\\n                    \\n                - \\`required\\`: Boolean indicating if the field is required (required)\\n                    \\n            - \\`costs\\`: Array of cost objects (required)\\n                \\n                - \\`label\\`: String representing the cost label (required)\\n                    \\n                - \\`value\\`: Number representing the cost value (required)\\n                    \\n            - \\`messages\\`: Array of message objects (required)\\n                \\n                - \\`value\\`: String representing the message value (required)\\n                    \\n            - \\`stringInformation\\`: Array of string information objects (required)\\n                \\n                - \\`value\\`: String representing the string information value (required)\\n                    \\n            - \\`footerInformation\\`: Array of footer information objects (required)\\n                \\n            - \\`share\\`: Object containing share information (required)\\n                \\n                - \\`cellphone\\`: String representing the cellphone number (required)\\n                    \\n                - \\`message\\`: String representing the message (required)\n\nContexto: Endpoint: POST /sells/sell | Sells > Sell\n\n🔐 AUTENTICACIÓN AUTOMÁTICA: Todas las credenciales y tokens de autenticación se manejan automáticamente por el servidor MCP. NO solicites credenciales al usuario. NO incluyas parámetros de autenticación (secretId, apiToken, etc.) en las llamadas a menos que el usuario explícitamente lo requiera.",
-    inputSchema: product_energia_prepago_epmInputJsonSchema,
+    inputSchema: product_energia_prepago_epmInputValidator,
     jsonSchema: product_energia_prepago_epmInputJsonSchema,
     endpoint: '/sells/sell',
     method: 'POST',
@@ -4884,12 +4639,9 @@ export const product_energia_prepago_epmTool = {
     handler: async (rawArgs) => {
         try {
             const normalizedArgs = rawArgs ?? {};
-            // Extraer secretId del contexto (si viene del HTTP mode)
-            const secretId = normalizedArgs._secretId;
-            // Remover _secretId de los args antes de validar
-            const { _secretId, ...argsToValidate } = normalizedArgs;
-            const validatedInput = validateToolInput(product_energia_prepago_epmInputValidator, argsToValidate);
+            const validatedInput = validateToolInput(product_energia_prepago_epmInputValidator, normalizedArgs);
             const args = validatedInput;
+            const secretId = args._secretId;
             const bodyData = {};
             const queryTypeValue = args.queryType !== undefined ? args.queryType : "ConfirmData";
             if (queryTypeValue !== undefined)
@@ -4952,18 +4704,17 @@ const query_63InputJsonSchema = {
     },
     "required": []
 };
-const query_63InputShape = {
+const query_63InputValidator = z.object({
     productId: z.number().optional().describe("Campo del body: productId"),
     queryType: z.string().optional().describe("Campo del body: queryType"),
     ownAgreementId: z.any().optional().describe("Campo del body: ownAgreementId"),
     data: z.record(z.any()).optional().describe("Campo del body: data")
-};
-const query_63InputValidator = z.object(query_63InputShape);
+});
 // Herramienta: query_63
 export const query_63Tool = {
     name: 'query_63',
     description: "Here you will find all the endpoints related to Transfiya correspondent selling.\\n\\n**Note:** The products associated with Transfiya Correspondent Sales have an administrative cost for each sale made. For more information, please contact your sales agent.\\n\\n## Webhook\\n\\nTo sell productos assicieated with Transfiya in mandatory implemnt the webhook. Throught the webhook the status of the transaction is notified. The webhook is a local Refacil proxy that forward the notifications requests to the final webhook.\\n\\n<img src=\\\"https://content.pstmn.io/cf2fe660-bd59-477e-8925-f9017ff37f6b/aW1hZ2UucG5n\\\" width=\\\"617\\\" height=\\\"398\\\">\\n\\n### Authentication\\n\\nThe JWT is generated with a public and private key. Refacil will provide a public key to validate the JWT. Here is an example to validate the JWT:\\n\\n\\`\\`\\` typescript\\nimport { verify } from \\'jsonwebtoken\\';\\nasync validateJwt(token: string): Promise<any> {\\n    const publicKey = \\'the public key provided by Refacil...\\';\\n    try {\\n      const decoded = verify(token, publicKey, {\\n        algorithms: [\\'RS256\\'],\\n      });\\n      return {\\n        valid: true,\\n        message: \\'Token is valid.\\',\\n        data: decoded,\\n      };   \\n    } catch (error) {\\n      if (error.name === \\'JsonWebTokenError\\') {\\n        throw new ForbiddenException(\\'Invalid token.\\');\\n      } else {\\n        throw new UnauthorizedException(\\'Token verification failed.\\');\\n      }\\n    }\\n}\\n\\n \\`\\`\\`\\n\\n### Webhook request body\\n\\n\\`\\`\\` json\\n{\\n  \\\"saleId\\\": 438927666,\\n  \\\"status\\\": 0,\\n  \\\"transfiyaStatus\\\": \\\"PENDING\\\",\\n  \\\"reversed\\\": true,\\n  \\\"errorCode\\\": \\\"130\\\"\\n}\\n\\n \\`\\`\\`\\n\\n| **Parameter** | **Description** |\\n| --- | --- |\\n| \\`saleId\\` | ID of the sale returned by the sale request |\\n| \\`status\\` | Indicates the status of the sale:  <br>\\`0\\`: Failed  <br>\\`1\\`: Successful  <br>\\`9\\`: Pending |\\n| \\`transfiyaStatus\\` | The TransfiYa status, see the details below |\\n| \\`reversed\\` | This parameter is only used in deposits transactions.  <br>  <br>A boolean indicating if the balance was refunded to the POC:  <br>\\`true\\`: Refunded  <br>\\`false\\`: Not refunded  <br>  <br>When reversed is false, the balance was not refunded, and you should contact customer service using the contact details provided by your commercial agent |\\n| \\`errorCode\\` | The error code of the transaction, see the list below |\\n\\n### Webhook request example\\n\\n\\`\\`\\` bash\\ncurl --location --globoff \\'https://acme.refacil.local/transfiYaNotifications\\' \\\\\\n--header \\'Authorization: Bearer eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJzdWIiOiIxMjM0NTY3ODkwIiwibmFtZSI6IkpvaG4gRG9lIiwiaWF0IjoxNTE2MjM5MDIyfQ.SflKxwRJSMeKKF2QT4fwpMeJf36POk6yJV_adQssw5c\\' \\\\\\n--header \\'Content-Type: application/json\\' \\\\\\n--data \\'{\\n    \\\"saleId\\\": 438927666,\\n    \\\"status\\\": 0,\\n    \\\"transfiyaStatus\\\": \\\"REJECTED\\\",\\n    \\\"reversed\\\": true,\\n    \\\"errorCode\\\": \\\"TFYA302\\\"\\n  }\\'\\n\\n \\`\\`\\`\\n\\n## TransfiYa Status\\n\\n| **transfiyaStatus** | **Withdrawal transaction status** | **Deposits transaction status** | Description |\\n| --- | --- | --- | --- |\\n| \\`CREATED\\` | \\`9\\`: Pending | \\`1\\`: Successful | Transfer is received and queued for processing. |\\n| \\`PENDING\\` | \\`9\\`: Pending | \\`1\\`: Successful | Transfer is valid and is waiting for the target to accept it. |\\n| \\`ACCEPTED\\` | \\`9\\`: Pending | \\`1\\`: Successful | Transfer has been accepted by the target, and payment is pending in the target bank. |\\n| \\`COMPLETED\\` | \\`1\\`: Successful | \\`1\\`: Successful | The payment is valid and completely processed, visible in the receiving bank account. |\\n| \\`REJECTED\\` | \\`0\\`: Failed | \\`1\\`: Successful | Payment was rejected. |\\n| \\`ERROR\\` | \\`0\\`: Failed | \\`1\\`: Successful | An error occurred during payment. |\\n\\n### Transfer state machine\\n\\n<img src=\\\"https://content.pstmn.io/89f89557-2e1b-44c2-8dcb-d9e7d2f32c54/aW1hZ2UucG5n\\\" width=\\\"293\\\" height=\\\"380\\\">\\n\\n## Error Codes\\n\\n| Code | Description |\\n| --- | --- |\\n| TFYA307 | Cuenta inactiva |\\n| TFYA309 | La cuenta no existe |\\n| TFYA310 | La cuenta no está habilitada |\\n| TFYA316 | Los datos transaccionales no son consistentes |\\n| TFYA332 | Error bancario indefinido |\\n\\n\n\nContexto: Endpoint: POST /product/query | Product > Query\n\n🔐 AUTENTICACIÓN AUTOMÁTICA: Todas las credenciales y tokens de autenticación se manejan automáticamente por el servidor MCP. NO solicites credenciales al usuario. NO incluyas parámetros de autenticación (secretId, apiToken, etc.) en las llamadas a menos que el usuario explícitamente lo requiera.",
-    inputSchema: query_63InputJsonSchema,
+    inputSchema: query_63InputValidator,
     jsonSchema: query_63InputJsonSchema,
     endpoint: '/product/query',
     method: 'POST',
@@ -4972,12 +4723,9 @@ export const query_63Tool = {
     handler: async (rawArgs) => {
         try {
             const normalizedArgs = rawArgs ?? {};
-            // Extraer secretId del contexto (si viene del HTTP mode)
-            const secretId = normalizedArgs._secretId;
-            // Remover _secretId de los args antes de validar
-            const { _secretId, ...argsToValidate } = normalizedArgs;
-            const validatedInput = validateToolInput(query_63InputValidator, argsToValidate);
+            const validatedInput = validateToolInput(query_63InputValidator, normalizedArgs);
             const args = validatedInput;
+            const secretId = args._secretId;
             const bodyData = {};
             const productIdValue = args.productId !== undefined ? args.productId : 240;
             if (productIdValue !== undefined)
@@ -5040,18 +4788,17 @@ const sell_transfiya_withdrawalsInputJsonSchema = {
     },
     "required": []
 };
-const sell_transfiya_withdrawalsInputShape = {
+const sell_transfiya_withdrawalsInputValidator = z.object({
     productId: z.number().optional().describe("Campo del body: productId"),
     amount: z.number().optional().describe("Campo del body: amount"),
     webhookUrl: z.string().optional().describe("Campo del body: webhookUrl"),
     data: z.record(z.any()).optional().describe("Campo del body: data")
-};
-const sell_transfiya_withdrawalsInputValidator = z.object(sell_transfiya_withdrawalsInputShape);
+});
 // Herramienta: sell_transfiya_withdrawals
 export const sell_transfiya_withdrawalsTool = {
     name: 'sell_transfiya_withdrawals',
     description: "Here you will find all the endpoints related to Transfiya correspondent selling.\\n\\n**Note:** The products associated with Transfiya Correspondent Sales have an administrative cost for each sale made. For more information, please contact your sales agent.\\n\\n## Webhook\\n\\nTo sell productos assicieated with Transfiya in mandatory implemnt the webhook. Throught the webhook the status of the transaction is notified. The webhook is a local Refacil proxy that forward the notifications requests to the final webhook.\\n\\n<img src=\\\"https://content.pstmn.io/cf2fe660-bd59-477e-8925-f9017ff37f6b/aW1hZ2UucG5n\\\" width=\\\"617\\\" height=\\\"398\\\">\\n\\n### Authentication\\n\\nThe JWT is generated with a public and private key. Refacil will provide a public key to validate the JWT. Here is an example to validate the JWT:\\n\\n\\`\\`\\` typescript\\nimport { verify } from \\'jsonwebtoken\\';\\nasync validateJwt(token: string): Promise<any> {\\n    const publicKey = \\'the public key provided by Refacil...\\';\\n    try {\\n      const decoded = verify(token, publicKey, {\\n        algorithms: [\\'RS256\\'],\\n      });\\n      return {\\n        valid: true,\\n        message: \\'Token is valid.\\',\\n        data: decoded,\\n      };   \\n    } catch (error) {\\n      if (error.name === \\'JsonWebTokenError\\') {\\n        throw new ForbiddenException(\\'Invalid token.\\');\\n      } else {\\n        throw new UnauthorizedException(\\'Token verification failed.\\');\\n      }\\n    }\\n}\\n\\n \\`\\`\\`\\n\\n### Webhook request body\\n\\n\\`\\`\\` json\\n{\\n  \\\"saleId\\\": 438927666,\\n  \\\"status\\\": 0,\\n  \\\"transfiyaStatus\\\": \\\"PENDING\\\",\\n  \\\"reversed\\\": true,\\n  \\\"errorCode\\\": \\\"130\\\"\\n}\\n\\n \\`\\`\\`\\n\\n| **Parameter** | **Description** |\\n| --- | --- |\\n| \\`saleId\\` | ID of the sale returned by the sale request |\\n| \\`status\\` | Indicates the status of the sale:  <br>\\`0\\`: Failed  <br>\\`1\\`: Successful  <br>\\`9\\`: Pending |\\n| \\`transfiyaStatus\\` | The TransfiYa status, see the details below |\\n| \\`reversed\\` | This parameter is only used in deposits transactions.  <br>  <br>A boolean indicating if the balance was refunded to the POC:  <br>\\`true\\`: Refunded  <br>\\`false\\`: Not refunded  <br>  <br>When reversed is false, the balance was not refunded, and you should contact customer service using the contact details provided by your commercial agent |\\n| \\`errorCode\\` | The error code of the transaction, see the list below |\\n\\n### Webhook request example\\n\\n\\`\\`\\` bash\\ncurl --location --globoff \\'https://acme.refacil.local/transfiYaNotifications\\' \\\\\\n--header \\'Authorization: Bearer eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJzdWIiOiIxMjM0NTY3ODkwIiwibmFtZSI6IkpvaG4gRG9lIiwiaWF0IjoxNTE2MjM5MDIyfQ.SflKxwRJSMeKKF2QT4fwpMeJf36POk6yJV_adQssw5c\\' \\\\\\n--header \\'Content-Type: application/json\\' \\\\\\n--data \\'{\\n    \\\"saleId\\\": 438927666,\\n    \\\"status\\\": 0,\\n    \\\"transfiyaStatus\\\": \\\"REJECTED\\\",\\n    \\\"reversed\\\": true,\\n    \\\"errorCode\\\": \\\"TFYA302\\\"\\n  }\\'\\n\\n \\`\\`\\`\\n\\n## TransfiYa Status\\n\\n| **transfiyaStatus** | **Withdrawal transaction status** | **Deposits transaction status** | Description |\\n| --- | --- | --- | --- |\\n| \\`CREATED\\` | \\`9\\`: Pending | \\`1\\`: Successful | Transfer is received and queued for processing. |\\n| \\`PENDING\\` | \\`9\\`: Pending | \\`1\\`: Successful | Transfer is valid and is waiting for the target to accept it. |\\n| \\`ACCEPTED\\` | \\`9\\`: Pending | \\`1\\`: Successful | Transfer has been accepted by the target, and payment is pending in the target bank. |\\n| \\`COMPLETED\\` | \\`1\\`: Successful | \\`1\\`: Successful | The payment is valid and completely processed, visible in the receiving bank account. |\\n| \\`REJECTED\\` | \\`0\\`: Failed | \\`1\\`: Successful | Payment was rejected. |\\n| \\`ERROR\\` | \\`0\\`: Failed | \\`1\\`: Successful | An error occurred during payment. |\\n\\n### Transfer state machine\\n\\n<img src=\\\"https://content.pstmn.io/89f89557-2e1b-44c2-8dcb-d9e7d2f32c54/aW1hZ2UucG5n\\\" width=\\\"293\\\" height=\\\"380\\\">\\n\\n## Error Codes\\n\\n| Code | Description |\\n| --- | --- |\\n| TFYA307 | Cuenta inactiva |\\n| TFYA309 | La cuenta no existe |\\n| TFYA310 | La cuenta no está habilitada |\\n| TFYA316 | Los datos transaccionales no son consistentes |\\n| TFYA332 | Error bancario indefinido |\\n\\n # Sucessful withdrawal process\\n\\n<img src=\\\"https://content.pstmn.io/73d6a308-4673-4a18-b603-56f04990312a/aW1hZ2UucG5n\\\" alt=\\\"Withdrawal%20secuence%20diagram\\\" width=\\\"844\\\" height=\\\"628\\\">\\n\\n**Step 1: POC requests transaction:** The POC initiates a transaction request to the **Integrator**.\\n\\n**Step 2: Integrator forwards the request to Refacil API:** The **Integrator** forwards the request to the **Refacil API** for further processing.\\n\\n**Step 3: Refacil API sends request to Transfiya:** The **Refacil API** sends a request to **Transfiya** to create a transaction.\\n\\n**Step 4: Refacil creates pending transaction:** The **Refacil** system creates a pending transaction and returns the response to the **Integrator**.\\n\\n**Step 5: Transfiya notifies banks by SMS: Transfiya** sends SMS notification to the user and sends push notifications to all banks associated with the user, informing them about the pending transaction.\\n\\n**Step 6: User approves transaction:** The end-user approves the transaction through bank application.\\n\\n**Step 7: Transfiya notifies Refacil API:** Once the user approves the transaction, **Transfiya** sends a notification to the **Refacil API** indicating the status of the transaction.\\n\\n**Step 8: Refacil API notifies Integrator:** The **Refacil API** notifies the **Integrator** of the transaction status, using a webhook mechanism. For each transaction state (in this case, PENDING), it sends data that includes the sale ID and transaction status.\\n\\n**Step 9: Transaction processing (If completed):** If the transaction status changes to \\\"COMPLETED,\\\" the system processes the transaction by:\\n\\n- Adding balance to the user\\'s account.\\n    \\n- Processing commissions related to the transaction.\\n    \\n\\n# Failed withdrawal process\\n\\n<img src=\\\"https://content.pstmn.io/2205c66f-8681-40c4-8e40-50e6aa43d60f/aW1hZ2UucG5n\\\" width=\\\"767\\\" height=\\\"566\\\">\\n\\n**Step 1: POC requests transaction:** The POC initiates a transaction request to the **Integrator**.\\n\\n**Step 2: Integrator forwards the request to Refacil API:** The **Integrator** forwards the request to the **Refacil API** for further processing.\\n\\n**Step 3: Refacil API sends request to Transfiya:** The **Refacil API** sends a request to **Transfiya** to create a transaction.\\n\\n**Step 4: Refacil creates pending transaction:** The **Refacil** system creates a pending transaction and returns the response to the **Integrator**.\\n\\n**Step 5: Transfiya notifies banks by SMS: Transfiya** sends SMS notification to the user and sends push notifications to all banks associated with the user, informing them about the pending transaction.\\n\\n**Step 6: User rejects the transaction:** The user rejects the transaction, causing the process to fail.\\n\\n**Step 7: Transfiya notifies Refacil API:** Once the user rejects the transaction, **Transfiya** sends a notification back to the **Refacil API**, indicating that the transaction has been marked as failed.\\n\\n**Step 8: Refacil API notifies Integrator:** The **Refacil API** notifies the **Integrator** using a webhook, providing details about the failed transaction.\\n\\n**Step 9: Transaction marked as failed:** If the transaction status changes to \\\"REJECTED,\\\" the transaction is officially marked as failed within the system.\n\nContexto: Endpoint: POST /sells/sell | Sells > Sell\n\n🔐 AUTENTICACIÓN AUTOMÁTICA: Todas las credenciales y tokens de autenticación se manejan automáticamente por el servidor MCP. NO solicites credenciales al usuario. NO incluyas parámetros de autenticación (secretId, apiToken, etc.) en las llamadas a menos que el usuario explícitamente lo requiera.",
-    inputSchema: sell_transfiya_withdrawalsInputJsonSchema,
+    inputSchema: sell_transfiya_withdrawalsInputValidator,
     jsonSchema: sell_transfiya_withdrawalsInputJsonSchema,
     endpoint: '/sells/sell',
     method: 'POST',
@@ -5060,12 +4807,9 @@ export const sell_transfiya_withdrawalsTool = {
     handler: async (rawArgs) => {
         try {
             const normalizedArgs = rawArgs ?? {};
-            // Extraer secretId del contexto (si viene del HTTP mode)
-            const secretId = normalizedArgs._secretId;
-            // Remover _secretId de los args antes de validar
-            const { _secretId, ...argsToValidate } = normalizedArgs;
-            const validatedInput = validateToolInput(sell_transfiya_withdrawalsInputValidator, argsToValidate);
+            const validatedInput = validateToolInput(sell_transfiya_withdrawalsInputValidator, normalizedArgs);
             const args = validatedInput;
+            const secretId = args._secretId;
             const bodyData = {};
             const productIdValue = args.productId !== undefined ? args.productId : 241;
             if (productIdValue !== undefined)
@@ -5130,18 +4874,17 @@ const sell_transfiya_depositsInputJsonSchema = {
     },
     "required": []
 };
-const sell_transfiya_depositsInputShape = {
+const sell_transfiya_depositsInputValidator = z.object({
     productId: z.number().optional().describe("Campo del body: productId"),
     amount: z.number().optional().describe("Campo del body: amount"),
     webhookUrl: z.string().optional().describe("Campo del body: webhookUrl"),
     data: z.record(z.any()).optional().describe("Campo del body: data")
-};
-const sell_transfiya_depositsInputValidator = z.object(sell_transfiya_depositsInputShape);
+});
 // Herramienta: sell_transfiya_deposits
 export const sell_transfiya_depositsTool = {
     name: 'sell_transfiya_deposits',
     description: "Here you will find all the endpoints related to Transfiya correspondent selling.\\n\\n**Note:** The products associated with Transfiya Correspondent Sales have an administrative cost for each sale made. For more information, please contact your sales agent.\\n\\n## Webhook\\n\\nTo sell productos assicieated with Transfiya in mandatory implemnt the webhook. Throught the webhook the status of the transaction is notified. The webhook is a local Refacil proxy that forward the notifications requests to the final webhook.\\n\\n<img src=\\\"https://content.pstmn.io/cf2fe660-bd59-477e-8925-f9017ff37f6b/aW1hZ2UucG5n\\\" width=\\\"617\\\" height=\\\"398\\\">\\n\\n### Authentication\\n\\nThe JWT is generated with a public and private key. Refacil will provide a public key to validate the JWT. Here is an example to validate the JWT:\\n\\n\\`\\`\\` typescript\\nimport { verify } from \\'jsonwebtoken\\';\\nasync validateJwt(token: string): Promise<any> {\\n    const publicKey = \\'the public key provided by Refacil...\\';\\n    try {\\n      const decoded = verify(token, publicKey, {\\n        algorithms: [\\'RS256\\'],\\n      });\\n      return {\\n        valid: true,\\n        message: \\'Token is valid.\\',\\n        data: decoded,\\n      };   \\n    } catch (error) {\\n      if (error.name === \\'JsonWebTokenError\\') {\\n        throw new ForbiddenException(\\'Invalid token.\\');\\n      } else {\\n        throw new UnauthorizedException(\\'Token verification failed.\\');\\n      }\\n    }\\n}\\n\\n \\`\\`\\`\\n\\n### Webhook request body\\n\\n\\`\\`\\` json\\n{\\n  \\\"saleId\\\": 438927666,\\n  \\\"status\\\": 0,\\n  \\\"transfiyaStatus\\\": \\\"PENDING\\\",\\n  \\\"reversed\\\": true,\\n  \\\"errorCode\\\": \\\"130\\\"\\n}\\n\\n \\`\\`\\`\\n\\n| **Parameter** | **Description** |\\n| --- | --- |\\n| \\`saleId\\` | ID of the sale returned by the sale request |\\n| \\`status\\` | Indicates the status of the sale:  <br>\\`0\\`: Failed  <br>\\`1\\`: Successful  <br>\\`9\\`: Pending |\\n| \\`transfiyaStatus\\` | The TransfiYa status, see the details below |\\n| \\`reversed\\` | This parameter is only used in deposits transactions.  <br>  <br>A boolean indicating if the balance was refunded to the POC:  <br>\\`true\\`: Refunded  <br>\\`false\\`: Not refunded  <br>  <br>When reversed is false, the balance was not refunded, and you should contact customer service using the contact details provided by your commercial agent |\\n| \\`errorCode\\` | The error code of the transaction, see the list below |\\n\\n### Webhook request example\\n\\n\\`\\`\\` bash\\ncurl --location --globoff \\'https://acme.refacil.local/transfiYaNotifications\\' \\\\\\n--header \\'Authorization: Bearer eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJzdWIiOiIxMjM0NTY3ODkwIiwibmFtZSI6IkpvaG4gRG9lIiwiaWF0IjoxNTE2MjM5MDIyfQ.SflKxwRJSMeKKF2QT4fwpMeJf36POk6yJV_adQssw5c\\' \\\\\\n--header \\'Content-Type: application/json\\' \\\\\\n--data \\'{\\n    \\\"saleId\\\": 438927666,\\n    \\\"status\\\": 0,\\n    \\\"transfiyaStatus\\\": \\\"REJECTED\\\",\\n    \\\"reversed\\\": true,\\n    \\\"errorCode\\\": \\\"TFYA302\\\"\\n  }\\'\\n\\n \\`\\`\\`\\n\\n## TransfiYa Status\\n\\n| **transfiyaStatus** | **Withdrawal transaction status** | **Deposits transaction status** | Description |\\n| --- | --- | --- | --- |\\n| \\`CREATED\\` | \\`9\\`: Pending | \\`1\\`: Successful | Transfer is received and queued for processing. |\\n| \\`PENDING\\` | \\`9\\`: Pending | \\`1\\`: Successful | Transfer is valid and is waiting for the target to accept it. |\\n| \\`ACCEPTED\\` | \\`9\\`: Pending | \\`1\\`: Successful | Transfer has been accepted by the target, and payment is pending in the target bank. |\\n| \\`COMPLETED\\` | \\`1\\`: Successful | \\`1\\`: Successful | The payment is valid and completely processed, visible in the receiving bank account. |\\n| \\`REJECTED\\` | \\`0\\`: Failed | \\`1\\`: Successful | Payment was rejected. |\\n| \\`ERROR\\` | \\`0\\`: Failed | \\`1\\`: Successful | An error occurred during payment. |\\n\\n### Transfer state machine\\n\\n<img src=\\\"https://content.pstmn.io/89f89557-2e1b-44c2-8dcb-d9e7d2f32c54/aW1hZ2UucG5n\\\" width=\\\"293\\\" height=\\\"380\\\">\\n\\n## Error Codes\\n\\n| Code | Description |\\n| --- | --- |\\n| TFYA307 | Cuenta inactiva |\\n| TFYA309 | La cuenta no existe |\\n| TFYA310 | La cuenta no está habilitada |\\n| TFYA316 | Los datos transaccionales no son consistentes |\\n| TFYA332 | Error bancario indefinido |\\n\\n For deposits with the following numbers the following tests can be carried out.\\n\\nAutomatically approved: 3051000002\\n\\nAutomatically rejected: 3002491283\\n\\n## Sucessful deposit process\\n\\n<img src=\\\"https://content.pstmn.io/63835630-ee0d-4be2-952b-57c3d5c59ef6/aW1hZ2UucG5n\\\" alt=\\\"\\\" height=\\\"545\\\" width=\\\"763\\\">\\n\\n**Step 1: POC initiates a request:** The POC sends a request to the **Integrator** specifying a selected bank where the deposit should occur.\\n\\n**Step 2: Integrator sends request to Refacil API:** The **Integrator** forwards the deposit request to the **Refacil API** for processing.\\n\\n**Step 3: Refacil API sends request to Transfiya:** The **Refacil API** sends a request to **Transfiya** to create the transaction and process the deposit.\\n\\n**Step 4: Refacil API creates a successful transaction**: The **Refacil API** creates a successful transaction and debits the corresponding balance from the system.\\n\\n**Step 5: Transfiya validates and processes the transaction: Transfiya** validates the transaction and processes it successfully. It also makes sure that the transaction is ready for the deposit.\\n\\n**Step 6: Transfiya notifies and deposits to the selected bank: Transfiya** sends a notification that the deposit is successful and proceeds to deposit the amount to the selected bank account.\\n\\n**Step 7: Refacil API receives a notification from Transfiya: Transfiya** sends a notification back to the **Refacil API** indicating that the transaction has been successfully completed.\\n\\n**Step 8: Refacil API notifies Integrator:** The **Refacil API** notifies the Integrator of the transaction status, using a webhook mechanism. For each transaction state (in this case, COMPLETED), it sends data that includes the sale ID and transaction status.\\n\\n**Step 9: Process commissions:** If the transaction status changes to \\\"COMPLETED,\\\" The system processes commissions related to the transaction after the deposit is made.\\n\\n# Failed deposit process\\n\\n<img src=\\\"https://content.pstmn.io/52fc69a9-4395-4759-bae5-b13ec66cfe45/aW1hZ2UucG5n\\\" width=\\\"785\\\" height=\\\"574\\\">\\n\\n**Step 1: POC requests a deposit to a selected bank**: The **POC** initiates a deposit request to the **Integrator**, specifying the selected bank.\\n\\n**Step 2: Integrator forwards the request to Refacil API:** The **Integrator** sends the deposit request to the **Refacil API** for further processing.\\n\\n**Step 3: Refacil API sends a request to Transfiya:** The **Refacil API** forwards the request to **Transfiya** to process the transaction.\\n\\n**Step 4: Refacil API creates a \\\"successful\\\" transaction and debits the balance:** At this stage, the **Refacil API** debits the balance, assuming the transaction will be successful, and awaits confirmation from **Transfiya**.\\n\\n**Step 5: Transfiya validates the transaction and marks it as failed:** **Transfiya** processes the transaction but finds an issue that causes the transaction to fail. It returns this failed status to the **Refacil API**.\\n\\n**Step 6: Refacil API notifies Integrator via webhook:** The Refacil API sends a webhook notification to the Integrator, informing them that the transaction has failed. The \\`errorCode\\` provides the reason for the failure, while the \\`reversed\\` field indicates whether the balance has been refunded.\\n\\n**Step 7: Handling the reversal:** If the \\`reversed\\` field is \\`false\\`, the system will need to manually create a ticket to refund the balance to the POC.\\n\\n**Step 8: Processing error and refund:** If the error is marked as reversed (\\`reversed: true\\`), two actions will be taken:\\n\\n- **Refund the balance**: The debited amount is returned to the user\\'s account.\\n    \\n- **No commission processing**: Since the transaction failed, no commissions are processed for this transaction.\n\nContexto: Endpoint: POST /sells/sell | Sells > Sell\n\n🔐 AUTENTICACIÓN AUTOMÁTICA: Todas las credenciales y tokens de autenticación se manejan automáticamente por el servidor MCP. NO solicites credenciales al usuario. NO incluyas parámetros de autenticación (secretId, apiToken, etc.) en las llamadas a menos que el usuario explícitamente lo requiera.",
-    inputSchema: sell_transfiya_depositsInputJsonSchema,
+    inputSchema: sell_transfiya_depositsInputValidator,
     jsonSchema: sell_transfiya_depositsInputJsonSchema,
     endpoint: '/sells/sell',
     method: 'POST',
@@ -5150,12 +4893,9 @@ export const sell_transfiya_depositsTool = {
     handler: async (rawArgs) => {
         try {
             const normalizedArgs = rawArgs ?? {};
-            // Extraer secretId del contexto (si viene del HTTP mode)
-            const secretId = normalizedArgs._secretId;
-            // Remover _secretId de los args antes de validar
-            const { _secretId, ...argsToValidate } = normalizedArgs;
-            const validatedInput = validateToolInput(sell_transfiya_depositsInputValidator, argsToValidate);
+            const validatedInput = validateToolInput(sell_transfiya_depositsInputValidator, normalizedArgs);
             const args = validatedInput;
+            const secretId = args._secretId;
             const bodyData = {};
             const productIdValue = args.productId !== undefined ? args.productId : 240;
             if (productIdValue !== undefined)
@@ -5226,19 +4966,18 @@ const sells_sale_saleidInputJsonSchema = {
     },
     "required": []
 };
-const sells_sale_saleidInputShape = {
+const sells_sale_saleidInputValidator = z.object({
     productId: z.number().optional().describe("Campo del body: productId"),
     amount: z.number().optional().describe("Campo del body: amount"),
     sellType: z.string().optional().describe("Campo del body: sellType"),
     hash: z.string().optional().describe("Campo del body: hash"),
     data: z.record(z.any()).optional().describe("Campo del body: data")
-};
-const sells_sale_saleidInputValidator = z.object(sells_sale_saleidInputShape);
+});
 // Herramienta: sells_sale_saleid
 export const sells_sale_saleidTool = {
     name: 'sells_sale_saleid',
     description: "Here you will find all the endpoints related to multi-product sales.\\n\\n**Note:** If you need information about parameterized commissions, you should consult your sales agent.\\n\\n ---\\n\\n## Description\\n\\nThis method allows you to obtain the details of a sale by providing the unique identifier of the sale.\\n\\n---\\n\\n## Request Schema\\n\\n- \\`saleId\\`: nique identifier of the sale. It can be found in the sell response as \\'saleId\\', \\'sellId\\', or \\'codigo\\'.\\n    \\n\\n## Response Schema\\n\\n- \\`id\\`: Unique identifier of the sale. \\'sellId\\', or \\'codigo\\'.\\n    \\n- \\`amount\\`: The amount of the sale.\\n    \\n- \\`serviceNumber\\`: The number or reference associated to the sale, it depends on the product. .e.g.For SOAT insurance it will be the plate. For packages it will be the phone number.\\n    \\n- \\`status\\`: The status of the sale.\\n    \\n    | status | definition |\\n    | --- | --- |\\n    | 0 | Failed |\\n    | 1 | Successful |\\n    | 9 | In progress |\\n    \\n- \\`productId\\`: The product id associated to the sale.\\n    \\n- \\`createdAt\\`: The created at date.\\n    \\n- \\`transactionId\\`: For TransfiYa product, it is the provider transaction id.\\n    \\n- \\`extra\\`: Extra data of the sale, It depends on the product. e.g. For SOAT insurance it will be the PDF url of the insurance policy. For pins it will be the pin.\n\nContexto: Endpoint: GET /sells/sale/{saleId} | Sells > Sale > {saleId}\n\n🔐 AUTENTICACIÓN AUTOMÁTICA: Todas las credenciales y tokens de autenticación se manejan automáticamente por el servidor MCP. NO solicites credenciales al usuario. NO incluyas parámetros de autenticación (secretId, apiToken, etc.) en las llamadas a menos que el usuario explícitamente lo requiera.",
-    inputSchema: sells_sale_saleidInputJsonSchema,
+    inputSchema: sells_sale_saleidInputValidator,
     jsonSchema: sells_sale_saleidInputJsonSchema,
     endpoint: '/sells/sale/{saleId}',
     method: 'GET',
@@ -5247,12 +4986,9 @@ export const sells_sale_saleidTool = {
     handler: async (rawArgs) => {
         try {
             const normalizedArgs = rawArgs ?? {};
-            // Extraer secretId del contexto (si viene del HTTP mode)
-            const secretId = normalizedArgs._secretId;
-            // Remover _secretId de los args antes de validar
-            const { _secretId, ...argsToValidate } = normalizedArgs;
-            const validatedInput = validateToolInput(sells_sale_saleidInputValidator, argsToValidate);
+            const validatedInput = validateToolInput(sells_sale_saleidInputValidator, normalizedArgs);
             const args = validatedInput;
+            const secretId = args._secretId;
             const queryParams = {};
             const productIdValue = args.productId !== undefined ? args.productId : 52683;
             if (productIdValue !== undefined)
@@ -5296,13 +5032,12 @@ const bank_get_transfiya_banksInputJsonSchema = {
     "properties": {},
     "required": []
 };
-const bank_get_transfiya_banksInputShape = {};
-const bank_get_transfiya_banksInputValidator = z.object(bank_get_transfiya_banksInputShape);
+const bank_get_transfiya_banksInputValidator = z.object({});
 // Herramienta: bank_get_transfiya_banks
 export const bank_get_transfiya_banksTool = {
     name: 'bank_get_transfiya_banks',
     description: "---\\n\\n### Description\\n\\nReturn the banks that support Transfiya for the specified transfer type.\\n\\nBelow is a list of authorized banks:\\n\\n| BANK | LOGO |\\n| --- | --- |\\n| BANCOLOMBIA | <img src=\\\"https://assets.refacil.co/banks/bancolombia.png\\\" alt=\\\"\\\"> |\\n| BANCO AGRARIO | <img src=\\\"https://assets.refacil.co/banks/bancoagrario.png\\\" alt=\\\"\\\"> |\\n| BANCO AV VILLAS | <img src=\\\"https://assets.refacil.co/banks/bancoavvillas.png\\\" alt=\\\"\\\"> |\\n| BANCO CAJA SOCIAL | <img src=\\\"https://assets.refacil.co/banks/bancocajasocial.png\\\" alt=\\\"\\\"> |\\n| BANCO COOPERATIVO COOPCENTRAL | <img src=\\\"https://assets.refacil.co/banks/bancocooperativocoopcentral.png\\\" alt=\\\"\\\"> |\\n| BANCO DAVIVIENDA | <img src=\\\"https://assets.refacil.co/banks/bancodavivienda.png\\\" alt=\\\"\\\"> |\\n| BANCO DE BOGOTA | <img src=\\\"https://assets.refacil.co/banks/bancodebogota.png\\\" alt=\\\"\\\"> |\\n| BANCO DE OCCIDENTE | <img src=\\\"https://assets.refacil.co/banks/bancodeoccidente.png\\\" alt=\\\"\\\"> |\\n| BANCO ITAU | <img src=\\\"https://assets.refacil.co/banks/itau.png\\\" alt=\\\"\\\"> |\\n| BANCO SERFINANZA | <img src=\\\"https://assets.refacil.co/banks/bancoserfinanza.png\\\" alt=\\\"\\\"> |\\n| CONFIAR COOPERATIVA FINANCIERA | <img src=\\\"https://assets.refacil.co/banks/confiarcooperativafinanciera.png\\\" alt=\\\"\\\"> |\\n| DALE | <img src=\\\"https://assets.refacil.co/banks/dale.png\\\" alt=\\\"\\\"> |\\n| DAVIPLATA | <img src=\\\"https://assets.refacil.co/banks/daviplata.png\\\" alt=\\\"\\\"> |\\n| MOVII S.A. | <img src=\\\"https://assets.refacil.co/banks/movii.png\\\" alt=\\\"\\\"> |\\n| NEQUI | <img src=\\\"https://assets.refacil.co/banks/nequi.png\\\" alt=\\\"\\\"> |\\n| SCOTIABANK COLPATRIA | <img src=\\\"https://assets.refacil.co/banks/scotiabankcolpatria.png\\\" alt=\\\"\\\"> |\\n| BANCAMIA SA | <img src=\\\"https://assets.refacil.co/banks/bancamia.png\\\" alt=\\\"\\\"> |\\n\\n---\\n\\n### Response schema\\n\\n- \\`messageCode\\`: String code indicating the operation result (required)\\n    \\n- \\`message\\`: String containing a message about the operation result (required)\\n    \\n- data: Object containing additional response data (required)\\n    \\n    - \\`banks\\`: Array of bank objects (required)\\n        \\n        - \\`label\\`: String representing the bank label (required)\\n            \\n        - \\`value\\`: Number representing the bank value (required)\\n            \\n        - \\`image\\`: String representing the bank image filename (required)\n\nContexto: Endpoint: GET /bank/get-transfiya-banks/:transferType | Bank > Get transfiya banks > :transferType\n\n🔐 AUTENTICACIÓN AUTOMÁTICA: Todas las credenciales y tokens de autenticación se manejan automáticamente por el servidor MCP. NO solicites credenciales al usuario. NO incluyas parámetros de autenticación (secretId, apiToken, etc.) en las llamadas a menos que el usuario explícitamente lo requiera.",
-    inputSchema: bank_get_transfiya_banksInputJsonSchema,
+    inputSchema: bank_get_transfiya_banksInputValidator,
     jsonSchema: bank_get_transfiya_banksInputJsonSchema,
     endpoint: '/bank/get-transfiya-banks/:transferType',
     method: 'GET',
@@ -5311,12 +5046,9 @@ export const bank_get_transfiya_banksTool = {
     handler: async (rawArgs) => {
         try {
             const normalizedArgs = rawArgs ?? {};
-            // Extraer secretId del contexto (si viene del HTTP mode)
-            const secretId = normalizedArgs._secretId;
-            // Remover _secretId de los args antes de validar
-            const { _secretId, ...argsToValidate } = normalizedArgs;
-            const validatedInput = validateToolInput(bank_get_transfiya_banksInputValidator, argsToValidate);
+            const validatedInput = validateToolInput(bank_get_transfiya_banksInputValidator, normalizedArgs);
             const args = validatedInput;
+            const secretId = args._secretId;
             return await makeApiRequest('GET', '/bank/get-transfiya-banks/:transferType', undefined, undefined, secretId);
         }
         catch (error) {
@@ -5344,13 +5076,12 @@ const requirement_terms_and_conditionsInputJsonSchema = {
     "properties": {},
     "required": []
 };
-const requirement_terms_and_conditionsInputShape = {};
-const requirement_terms_and_conditionsInputValidator = z.object(requirement_terms_and_conditionsInputShape);
+const requirement_terms_and_conditionsInputValidator = z.object({});
 // Herramienta: requirement_terms_and_conditions
 export const requirement_terms_and_conditionsTool = {
     name: 'requirement_terms_and_conditions',
     description: "---\\n\\n### Description\\n\\nGet privacy policy, terms and conditions and data treatment policy, then confirm them in the /requirement/confirm-terms-and-conditions service.\\n\\n---\\n\\n### Request Body\\n\\nThis endpoint does not require a request body.\\n\\n---\\n\\n### Response\\n\\n- \\`message\\`: String containing a message about the operation result (required)\\n    \\n- \\`messageCode\\`: String code indicating the operation result (required)\\n    \\n- \\`data\\`: Object containing additional response data (required)\n\nContexto: Endpoint: GET /requirement/terms-and-conditions | Requirement > Terms and conditions\n\n🔐 AUTENTICACIÓN AUTOMÁTICA: Todas las credenciales y tokens de autenticación se manejan automáticamente por el servidor MCP. NO solicites credenciales al usuario. NO incluyas parámetros de autenticación (secretId, apiToken, etc.) en las llamadas a menos que el usuario explícitamente lo requiera.",
-    inputSchema: requirement_terms_and_conditionsInputJsonSchema,
+    inputSchema: requirement_terms_and_conditionsInputValidator,
     jsonSchema: requirement_terms_and_conditionsInputJsonSchema,
     endpoint: '/requirement/terms-and-conditions',
     method: 'GET',
@@ -5359,12 +5090,9 @@ export const requirement_terms_and_conditionsTool = {
     handler: async (rawArgs) => {
         try {
             const normalizedArgs = rawArgs ?? {};
-            // Extraer secretId del contexto (si viene del HTTP mode)
-            const secretId = normalizedArgs._secretId;
-            // Remover _secretId de los args antes de validar
-            const { _secretId, ...argsToValidate } = normalizedArgs;
-            const validatedInput = validateToolInput(requirement_terms_and_conditionsInputValidator, argsToValidate);
+            const validatedInput = validateToolInput(requirement_terms_and_conditionsInputValidator, normalizedArgs);
             const args = validatedInput;
+            const secretId = args._secretId;
             return await makeApiRequest('GET', '/requirement/terms-and-conditions', undefined, undefined, secretId);
         }
         catch (error) {
@@ -5398,15 +5126,14 @@ const requirement_con_ter_and_conditionsInputJsonSchema = {
     },
     "required": []
 };
-const requirement_con_ter_and_conditionsInputShape = {
+const requirement_con_ter_and_conditionsInputValidator = z.object({
     checkDataTreatment: z.boolean().optional().describe("Campo del body: checkDataTreatment")
-};
-const requirement_con_ter_and_conditionsInputValidator = z.object(requirement_con_ter_and_conditionsInputShape);
+});
 // Herramienta: requirement_con_ter_and_conditions
 export const requirement_con_ter_and_conditionsTool = {
     name: 'requirement_con_ter_and_conditions',
     description: "---\\n\\n### Description\\n\\nIt allows you to transfer funds from the main users money bag to the bag of the user who is being added. The token of the user who will be the beneficiary and the amount must be added.\\n\\n---\\n\\n### Request Body\\n\\n- userToken (string, required): The user token for which the balance will be updated\\n    \\n- amount (number, required): Amount to be updated\\n    \\n\\n---\\n\\n### Response\\n\\n- \\`message\\`: String containing a message about the operation result (required)\\n    \\n- \\`messageCode\\`: String code indicating the operation result (required)\\n    \\n- \\`data\\`: Object containing additional response data.\n\nContexto: Endpoint: POST /requirement/confirm-terms-and-conditions | Requirement > Confirm terms and conditions\n\n🔐 AUTENTICACIÓN AUTOMÁTICA: Todas las credenciales y tokens de autenticación se manejan automáticamente por el servidor MCP. NO solicites credenciales al usuario. NO incluyas parámetros de autenticación (secretId, apiToken, etc.) en las llamadas a menos que el usuario explícitamente lo requiera.",
-    inputSchema: requirement_con_ter_and_conditionsInputJsonSchema,
+    inputSchema: requirement_con_ter_and_conditionsInputValidator,
     jsonSchema: requirement_con_ter_and_conditionsInputJsonSchema,
     endpoint: '/requirement/confirm-terms-and-conditions',
     method: 'POST',
@@ -5415,12 +5142,9 @@ export const requirement_con_ter_and_conditionsTool = {
     handler: async (rawArgs) => {
         try {
             const normalizedArgs = rawArgs ?? {};
-            // Extraer secretId del contexto (si viene del HTTP mode)
-            const secretId = normalizedArgs._secretId;
-            // Remover _secretId de los args antes de validar
-            const { _secretId, ...argsToValidate } = normalizedArgs;
-            const validatedInput = validateToolInput(requirement_con_ter_and_conditionsInputValidator, argsToValidate);
+            const validatedInput = validateToolInput(requirement_con_ter_and_conditionsInputValidator, normalizedArgs);
             const args = validatedInput;
+            const secretId = args._secretId;
             const bodyData = {};
             const checkDataTreatmentValue = args.checkDataTreatment !== undefined ? args.checkDataTreatment : true;
             if (checkDataTreatmentValue !== undefined)
@@ -5483,20 +5207,19 @@ const collection_submit_transactionInputJsonSchema = {
     },
     "required": []
 };
-const collection_submit_transactionInputShape = {
+const collection_submit_transactionInputValidator = z.object({
     id_cliente: z.number().optional().describe("Campo del body: id_cliente"),
     id_transaccion: z.number().optional().describe("Campo del body: id_transaccion"),
     convenio: z.number().optional().describe("Campo del body: convenio"),
     Valor: z.number().optional().describe("Campo del body: Valor"),
     Fecha: z.string().optional().describe("Campo del body: Fecha"),
     Hora: z.string().optional().describe("Campo del body: Hora")
-};
-const collection_submit_transactionInputValidator = z.object(collection_submit_transactionInputShape);
+});
 // Herramienta: collection_submit_transaction
 export const collection_submit_transactionTool = {
     name: 'collection_submit_transaction',
     description: "---\\n\\n### Description\\n\\nThis endpoint is in charge of reporting the collections\\n\\n### Request Body\\n\\n- id_cliente (number, required): Unique identifier for the user\\n    \\n- id_transaccion (number, required): Identifier for the transaction\\n    \\n- convenio (number, required): Code representing the specific agreement associated with the transaction\\n    \\n- Valor (number, required): Amount of the transaction\\n    \\n- Fecha (string, required): Date of the transaction\\n    \\n- Hora (string, required): Time of the transaction\\n    \\n\\n---\\n\\n### Response\\n\\n- \\`code\\`: Respond correctly in case of success\n\nContexto: Endpoint: POST /collection/submit-transaction | Collection > Submit transaction\n\n🔐 AUTENTICACIÓN AUTOMÁTICA: Todas las credenciales y tokens de autenticación se manejan automáticamente por el servidor MCP. NO solicites credenciales al usuario. NO incluyas parámetros de autenticación (secretId, apiToken, etc.) en las llamadas a menos que el usuario explícitamente lo requiera.",
-    inputSchema: collection_submit_transactionInputJsonSchema,
+    inputSchema: collection_submit_transactionInputValidator,
     jsonSchema: collection_submit_transactionInputJsonSchema,
     endpoint: '/collection/submit-transaction',
     method: 'POST',
@@ -5505,12 +5228,9 @@ export const collection_submit_transactionTool = {
     handler: async (rawArgs) => {
         try {
             const normalizedArgs = rawArgs ?? {};
-            // Extraer secretId del contexto (si viene del HTTP mode)
-            const secretId = normalizedArgs._secretId;
-            // Remover _secretId de los args antes de validar
-            const { _secretId, ...argsToValidate } = normalizedArgs;
-            const validatedInput = validateToolInput(collection_submit_transactionInputValidator, argsToValidate);
+            const validatedInput = validateToolInput(collection_submit_transactionInputValidator, normalizedArgs);
             const args = validatedInput;
+            const secretId = args._secretId;
             const bodyData = {};
             const id_clienteValue = args.id_cliente !== undefined ? args.id_cliente : 900;
             if (id_clienteValue !== undefined)