conductor-node-mcp 13.0.0 → 14.0.0

package/src/tools/qbd/sales-orders/create-qbd-sales-orders.ts

@@ -1,455 +0,0 @@
-// File generated from our OpenAPI spec by Stainless. See CONTRIBUTING.md for details.
-
-import { Metadata, asErrorResult, asTextContentResult } from 'conductor-node-mcp/tools/types';
-
-import { Tool } from '@modelcontextprotocol/sdk/types.js';
-import Conductor from 'conductor-node';
-
-export const metadata: Metadata = {
-  resource: 'qbd.sales_orders',
-  operation: 'write',
-  tags: [],
-  httpMethod: 'post',
-  httpPath: '/quickbooks-desktop/sales-orders',
-};
-
-export const tool: Tool = {
-  name: 'create_qbd_sales_orders',
-  description: 'Creates a new sales order.',
-  inputSchema: {
-    type: 'object',
-    properties: {
-      customerId: {
-        type: 'string',
-        description: 'The customer or customer-job associated with this sales order.',
-      },
-      transactionDate: {
-        type: 'string',
-        description: 'The date of this sales order, in ISO 8601 format (YYYY-MM-DD).',
-        format: 'date',
-      },
-      conductorEndUserId: {
-        type: 'string',
-        description: 'The ID of the End-User to receive this request.',
-      },
-      billingAddress: {
-        type: 'object',
-        description: "The sales order's billing address.",
-        properties: {
-          city: {
-            type: 'string',
-            description:
-              'The city, district, suburb, town, or village name of the address.\n\nMaximum length: 31 characters.',
-          },
-          country: {
-            type: 'string',
-            description: 'The country name of the address.',
-          },
-          line1: {
-            type: 'string',
-            description:
-              'The first line of the address (e.g., street, PO Box, or company name).\n\nMaximum length: 41 characters.',
-          },
-          line2: {
-            type: 'string',
-            description:
-              'The second line of the address, if needed (e.g., apartment, suite, unit, or building).\n\nMaximum length: 41 characters.',
-          },
-          line3: {
-            type: 'string',
-            description: 'The third line of the address, if needed.\n\nMaximum length: 41 characters.',
-          },
-          line4: {
-            type: 'string',
-            description: 'The fourth line of the address, if needed.\n\nMaximum length: 41 characters.',
-          },
-          line5: {
-            type: 'string',
-            description: 'The fifth line of the address, if needed.\n\nMaximum length: 41 characters.',
-          },
-          note: {
-            type: 'string',
-            description:
-              'A note written at the bottom of the address in the form in which it appears, such as the invoice form.',
-          },
-          postalCode: {
-            type: 'string',
-            description: 'The postal code or ZIP code of the address.\n\nMaximum length: 13 characters.',
-          },
-          state: {
-            type: 'string',
-            description:
-              'The state, county, province, or region name of the address.\n\nMaximum length: 21 characters.',
-          },
-        },
-      },
-      classId: {
-        type: 'string',
-        description:
-          "The sales order's class. Classes can be used to categorize objects into meaningful segments, such as department, location, or type of work. In QuickBooks, class tracking is off by default. A class defined here is automatically used in this sales order's line items unless overridden at the line item level.",
-      },
-      customerMessageId: {
-        type: 'string',
-        description: 'The message to display to the customer on the sales order.',
-      },
-      documentTemplateId: {
-        type: 'string',
-        description:
-          'The predefined template in QuickBooks that determines the layout and formatting for this sales order when printed or displayed.',
-      },
-      dueDate: {
-        type: 'string',
-        description: 'The date by which this sales order must be paid, in ISO 8601 format (YYYY-MM-DD).',
-        format: 'date',
-      },
-      exchangeRate: {
-        type: 'number',
-        description:
-          "The market exchange rate between this sales order's currency and the home currency in QuickBooks at the time of this transaction. Represented as a decimal value (e.g., 1.2345 for 1 EUR = 1.2345 USD if USD is the home currency).",
-      },
-      externalId: {
-        type: 'string',
-        description:
-          'A globally unique identifier (GUID) you, the developer, can provide for tracking this object in your external system. This field is immutable and can only be set during object creation.\n\n**IMPORTANT**: This field must be formatted as a valid GUID; otherwise, QuickBooks will return an error.',
-      },
-      isManuallyClosed: {
-        type: 'boolean',
-        description:
-          'Indicates whether this sales order has been manually marked as closed, even if it has not been invoiced.',
-      },
-      isQueuedForEmail: {
-        type: 'boolean',
-        description:
-          'Indicates whether this sales order is included in the queue of documents for QuickBooks to email to the customer.',
-      },
-      isQueuedForPrint: {
-        type: 'boolean',
-        description:
-          'Indicates whether this sales order is included in the queue of documents for QuickBooks to print.',
-      },
-      lineGroups: {
-        type: 'array',
-        description:
-          "The sales order's line item groups, each representing a predefined set of related items.\n\n**IMPORTANT**: You must specify `lines`, `lineGroups`, or both when creating a sales order.",
-        items: {
-          type: 'object',
-          properties: {
-            itemGroupId: {
-              type: 'string',
-              description:
-                "The sales order line group's item group, representing a predefined set of items bundled because they are commonly purchased together or grouped for faster entry.",
-            },
-            customFields: {
-              type: 'array',
-              description:
-                'The custom fields for the sales order line group object, added as user-defined data extensions, not included in the standard QuickBooks object.',
-              items: {
-                type: 'object',
-                properties: {
-                  name: {
-                    type: 'string',
-                    description:
-                      'The name of the custom field, unique for the specified `ownerId`. For public custom fields, this name is visible as a label in the QuickBooks UI.',
-                  },
-                  ownerId: {
-                    type: 'string',
-                    description:
-                      'The identifier of the owner of the custom field, which QuickBooks internally calls a "data extension". For public custom fields visible in the UI, such as those added by the QuickBooks user, this is always "0". For private custom fields that are only visible to the application that created them, this is a valid GUID identifying the owning application. Internally, Conductor always fetches all public custom fields (those with an `ownerId` of "0") for all objects.',
-                  },
-                  value: {
-                    type: 'string',
-                    description:
-                      "The value of this custom field. The maximum length depends on the field's data type.",
-                  },
-                },
-                required: ['name', 'ownerId', 'value'],
-              },
-            },
-            inventorySiteId: {
-              type: 'string',
-              description:
-                'The site location where inventory for the item group associated with this sales order line group is stored.',
-            },
-            inventorySiteLocationId: {
-              type: 'string',
-              description:
-                'The specific location (e.g., bin or shelf) within the inventory site where the item group associated with this sales order line group is stored.',
-            },
-            quantity: {
-              type: 'number',
-              description:
-                'The quantity of the item group associated with this sales order line group. This field cannot be cleared.\n\n**NOTE**: Do not use this field if the associated item group is a discount item group.',
-            },
-            unitOfMeasure: {
-              type: 'string',
-              description:
-                "The unit-of-measure used for the `quantity` in this sales order line group. Must be a valid unit within the item's available units of measure.",
-            },
-          },
-          required: ['itemGroupId'],
-        },
-      },
-      lines: {
-        type: 'array',
-        description:
-          "The sales order's line items, each representing a single product or service ordered.\n\n**IMPORTANT**: You must specify `lines`, `lineGroups`, or both when creating a sales order.",
-        items: {
-          type: 'object',
-          properties: {
-            amount: {
-              type: 'string',
-              description:
-                'The monetary amount of this sales order line, represented as a decimal string. If both `quantity` and `rate` are specified but not `amount`, QuickBooks will use them to calculate `amount`. If `amount`, `rate`, and `quantity` are all unspecified, then QuickBooks will calculate `amount` based on a `quantity` of `1` and the suggested `rate`. This field cannot be cleared.',
-            },
-            classId: {
-              type: 'string',
-              description:
-                "The sales order line's class. Classes can be used to categorize objects into meaningful segments, such as department, location, or type of work. In QuickBooks, class tracking is off by default. If a class is specified for the entire parent transaction, it is automatically applied to all sales order lines unless overridden here, at the transaction line level.",
-            },
-            customFields: {
-              type: 'array',
-              description:
-                'The custom fields for the sales order line object, added as user-defined data extensions, not included in the standard QuickBooks object.',
-              items: {
-                type: 'object',
-                properties: {
-                  name: {
-                    type: 'string',
-                    description:
-                      'The name of the custom field, unique for the specified `ownerId`. For public custom fields, this name is visible as a label in the QuickBooks UI.',
-                  },
-                  ownerId: {
-                    type: 'string',
-                    description:
-                      'The identifier of the owner of the custom field, which QuickBooks internally calls a "data extension". For public custom fields visible in the UI, such as those added by the QuickBooks user, this is always "0". For private custom fields that are only visible to the application that created them, this is a valid GUID identifying the owning application. Internally, Conductor always fetches all public custom fields (those with an `ownerId` of "0") for all objects.',
-                  },
-                  value: {
-                    type: 'string',
-                    description:
-                      "The value of this custom field. The maximum length depends on the field's data type.",
-                  },
-                },
-                required: ['name', 'ownerId', 'value'],
-              },
-            },
-            description: {
-              type: 'string',
-              description: 'A description of this sales order line.',
-            },
-            inventorySiteId: {
-              type: 'string',
-              description:
-                'The site location where inventory for the item associated with this sales order line is stored.',
-            },
-            inventorySiteLocationId: {
-              type: 'string',
-              description:
-                'The specific location (e.g., bin or shelf) within the inventory site where the item associated with this sales order line is stored.',
-            },
-            isManuallyClosed: {
-              type: 'boolean',
-              description:
-                'Indicates whether this sales order line has been manually marked as closed, even if it has not been invoiced.',
-            },
-            itemId: {
-              type: 'string',
-              description:
-                'The item associated with this sales order line. This can refer to any good or service that the business buys or sells, including item types such as a service item, inventory item, or special calculation item like a discount item or sales-tax item.',
-            },
-            lotNumber: {
-              type: 'string',
-              description:
-                'The lot number of the item associated with this sales order line. Used for tracking groups of inventory items that are purchased or manufactured together.',
-            },
-            otherCustomField1: {
-              type: 'string',
-              description:
-                "A built-in custom field for additional information specific to this sales order line. Unlike the user-defined fields in the `customFields` array, this is a standard QuickBooks field that exists for all sales order lines for convenience. Developers often use this field for tracking information that doesn't fit into other standard QuickBooks fields. Hidden by default in the QuickBooks UI.",
-            },
-            otherCustomField2: {
-              type: 'string',
-              description:
-                "A second built-in custom field for additional information specific to this sales order line. Unlike the user-defined fields in the `customFields` array, this is a standard QuickBooks field that exists for all sales order lines for convenience. Like `otherCustomField1`, developers often use this field for tracking information that doesn't fit into other standard QuickBooks fields. Hidden by default in the QuickBooks UI.",
-            },
-            priceLevelId: {
-              type: 'string',
-              description:
-                'The price level applied to this sales order line. This overrides any price level set on the corresponding customer. The resulting sales order line will not show this price level, only the final `rate` calculated from it.',
-            },
-            priceRuleConflictStrategy: {
-              type: 'string',
-              description:
-                'Specifies how to resolve price rule conflicts when adding or modifying this sales order line.',
-              enum: ['base_price', 'zero'],
-            },
-            quantity: {
-              type: 'number',
-              description:
-                'The quantity of the item associated with this sales order line. This field cannot be cleared.\n\n**NOTE**: Do not use this field if the associated item is a discount item.',
-            },
-            rate: {
-              type: 'string',
-              description:
-                'The price per unit for this sales order line. If both `rate` and `amount` are specified, `rate` will be ignored. If both `quantity` and `amount` are specified but not `rate`, QuickBooks will use them to calculate `rate`. Represented as a decimal string. This field cannot be cleared.',
-            },
-            ratePercent: {
-              type: 'string',
-              description:
-                'The price of this sales order line expressed as a percentage. Typically used for discount or markup items.',
-            },
-            salesTaxCodeId: {
-              type: 'string',
-              description:
-                'The sales-tax code for this sales order line, determining whether it is taxable or non-taxable. If set, this overrides any sales-tax codes defined on the parent transaction or the associated item.\n\nDefault codes include "Non" (non-taxable) and "Tax" (taxable), but custom codes can also be created in QuickBooks. If QuickBooks is not set up to charge sales tax (via the "Do You Charge Sales Tax?" preference), it will assign the default non-taxable code to all sales.',
-            },
-            serialNumber: {
-              type: 'string',
-              description:
-                'The serial number of the item associated with this sales order line. This is used for tracking individual units of serialized inventory items.',
-            },
-            unitOfMeasure: {
-              type: 'string',
-              description:
-                "The unit-of-measure used for the `quantity` in this sales order line. Must be a valid unit within the item's available units of measure.",
-            },
-          },
-        },
-      },
-      memo: {
-        type: 'string',
-        description: 'A memo or note for this sales order.',
-      },
-      otherCustomField: {
-        type: 'string',
-        description:
-          "A built-in custom field for additional information specific to this sales order. Unlike the user-defined fields in the `customFields` array, this is a standard QuickBooks field that exists for all sales orders for convenience. Developers often use this field for tracking information that doesn't fit into other standard QuickBooks fields. Unlike `otherCustomField1` and `otherCustomField2`, which are line item fields, this exists at the transaction level. Hidden by default in the QuickBooks UI.",
-      },
-      purchaseOrderNumber: {
-        type: 'string',
-        description:
-          "The customer's Purchase Order (PO) number associated with this sales order. This field is often used to cross-reference the sales order with the customer's purchasing system.\n\nMaximum length: 25 characters.",
-      },
-      refNumber: {
-        type: 'string',
-        description:
-          'The case-sensitive user-defined reference number for this sales order, which can be used to identify the transaction in QuickBooks. This value is not required to be unique and can be arbitrarily changed by the QuickBooks user. When left blank in this create request, this field will be left blank in QuickBooks (i.e., it does *not* auto-increment).',
-      },
-      salesChannelName: {
-        type: 'string',
-        description: 'The type of the sales channel for this sales order.',
-        enum: ['blank', 'ecommerce'],
-      },
-      salesRepresentativeId: {
-        type: 'string',
-        description:
-          "The sales order's sales representative. Sales representatives can be employees, vendors, or other names in QuickBooks.",
-      },
-      salesStoreName: {
-        type: 'string',
-        description: 'The name of the sales store for this sales order.',
-      },
-      salesStoreType: {
-        type: 'string',
-        description: 'The type of the sales store for this sales order.',
-      },
-      salesTaxCodeId: {
-        type: 'string',
-        description:
-          'The sales-tax code for this sales order, determining whether it is taxable or non-taxable. This can be overridden at the transaction-line level.\n\nDefault codes include "Non" (non-taxable) and "Tax" (taxable), but custom codes can also be created in QuickBooks. If QuickBooks is not set up to charge sales tax (via the "Do You Charge Sales Tax?" preference), it will assign the default non-taxable code to all sales.',
-      },
-      salesTaxItemId: {
-        type: 'string',
-        description:
-          "The sales-tax item used to calculate the actual tax amount for this sales order's transactions by applying a specific tax rate collected for a single tax agency. Unlike `salesTaxCode`, which only indicates general taxability, this field drives the actual tax calculation and reporting.",
-      },
-      shipmentOrigin: {
-        type: 'string',
-        description:
-          'The origin location from where the product associated with this sales order is shipped. This is the point at which ownership and liability for goods transfer from seller to buyer. Internally, QuickBooks uses the term "FOB" for this field, which stands for "freight on board". This field is informational and has no accounting implications.',
-      },
-      shippingAddress: {
-        type: 'object',
-        description: "The sales order's shipping address.",
-        properties: {
-          city: {
-            type: 'string',
-            description:
-              'The city, district, suburb, town, or village name of the address.\n\nMaximum length: 31 characters.',
-          },
-          country: {
-            type: 'string',
-            description: 'The country name of the address.',
-          },
-          line1: {
-            type: 'string',
-            description:
-              'The first line of the address (e.g., street, PO Box, or company name).\n\nMaximum length: 41 characters.',
-          },
-          line2: {
-            type: 'string',
-            description:
-              'The second line of the address, if needed (e.g., apartment, suite, unit, or building).\n\nMaximum length: 41 characters.',
-          },
-          line3: {
-            type: 'string',
-            description: 'The third line of the address, if needed.\n\nMaximum length: 41 characters.',
-          },
-          line4: {
-            type: 'string',
-            description: 'The fourth line of the address, if needed.\n\nMaximum length: 41 characters.',
-          },
-          line5: {
-            type: 'string',
-            description: 'The fifth line of the address, if needed.\n\nMaximum length: 41 characters.',
-          },
-          note: {
-            type: 'string',
-            description:
-              'A note written at the bottom of the address in the form in which it appears, such as the invoice form.',
-          },
-          postalCode: {
-            type: 'string',
-            description: 'The postal code or ZIP code of the address.\n\nMaximum length: 13 characters.',
-          },
-          state: {
-            type: 'string',
-            description:
-              'The state, county, province, or region name of the address.\n\nMaximum length: 21 characters.',
-          },
-        },
-      },
-      shippingDate: {
-        type: 'string',
-        description:
-          'The date when the products or services for this sales order were shipped or are expected to be shipped, in ISO 8601 format (YYYY-MM-DD).',
-        format: 'date',
-      },
-      shippingMethodId: {
-        type: 'string',
-        description:
-          'The shipping method used for this sales order, such as standard mail or overnight delivery.',
-      },
-      termsId: {
-        type: 'string',
-        description:
-          "The sales order's payment terms, defining when payment is due and any applicable discounts.",
-      },
-    },
-    required: ['customerId', 'transactionDate', 'conductorEndUserId'],
-  },
-  annotations: {},
-};
-
-export const handler = async (conductor: Conductor, args: Record<string, unknown> | undefined) => {
-  const body = args as any;
-  try {
-    return asTextContentResult(await conductor.qbd.salesOrders.create(body));
-  } catch (error) {
-    if (error instanceof Conductor.APIError) {
-      return asErrorResult(error.message);
-    }
-    throw error;
-  }
-};
-
-export default { metadata, tool, handler };

package/src/tools/qbd/sales-orders/delete-qbd-sales-orders.ts

@@ -1,60 +0,0 @@
-// File generated from our OpenAPI spec by Stainless. See CONTRIBUTING.md for details.
-
-import { isJqError, maybeFilter } from 'conductor-node-mcp/filtering';
-import { Metadata, asErrorResult, asTextContentResult } from 'conductor-node-mcp/tools/types';
-
-import { Tool } from '@modelcontextprotocol/sdk/types.js';
-import Conductor from 'conductor-node';
-
-export const metadata: Metadata = {
-  resource: 'qbd.sales_orders',
-  operation: 'write',
-  tags: [],
-  httpMethod: 'delete',
-  httpPath: '/quickbooks-desktop/sales-orders/{id}',
-};
-
-export const tool: Tool = {
-  name: 'delete_qbd_sales_orders',
-  description:
-    "When using this tool, always use the `jq_filter` parameter to reduce the response size and improve performance.\n\nOnly omit if you're sure you don't need the data.\n\nPermanently deletes a a sales order. The deletion will fail if the sales order is currently in use or has any linked transactions that are in use.\n\n# Response Schema\n```json\n{\n  $ref: '#/$defs/sales_order_delete_response',\n  $defs: {\n    sales_order_delete_response: {\n      type: 'object',\n      properties: {\n        id: {\n          type: 'string',\n          description: 'The QuickBooks-assigned unique identifier of the deleted sales order.'\n        },\n        deleted: {\n          type: 'boolean',\n          description: 'Indicates whether the sales order was deleted.'\n        },\n        objectType: {\n          type: 'string',\n          description: 'The type of object. This value is always `\"qbd_sales_order\"`.',\n          enum: [            'qbd_sales_order'\n          ]\n        },\n        refNumber: {\n          type: 'string',\n          description: 'The case-sensitive user-defined reference number of the deleted sales order.'\n        }\n      },\n      required: [        'id',\n        'deleted',\n        'objectType',\n        'refNumber'\n      ]\n    }\n  }\n}\n```",
-  inputSchema: {
-    type: 'object',
-    properties: {
-      id: {
-        type: 'string',
-        description: 'The QuickBooks-assigned unique identifier of the sales order to delete.',
-      },
-      conductorEndUserId: {
-        type: 'string',
-        description: 'The ID of the End-User to receive this request.',
-      },
-      jq_filter: {
-        type: 'string',
-        title: 'jq Filter',
-        description:
-          'A jq filter to apply to the response to include certain fields. Consult the output schema in the tool description to see the fields that are available.\n\nFor example: to include only the `name` field in every object of a results array, you can provide ".results[].name".\n\nFor more information, see the [jq documentation](https://jqlang.org/manual/).',
-      },
-    },
-    required: ['id', 'conductorEndUserId'],
-  },
-  annotations: {
-    idempotentHint: true,
-  },
-};
-
-export const handler = async (conductor: Conductor, args: Record<string, unknown> | undefined) => {
-  const { id, jq_filter, ...body } = args as any;
-  try {
-    return asTextContentResult(
-      await maybeFilter(jq_filter, await conductor.qbd.salesOrders.delete(id, body)),
-    );
-  } catch (error) {
-    if (error instanceof Conductor.APIError || isJqError(error)) {
-      return asErrorResult(error.message);
-    }
-    throw error;
-  }
-};
-
-export default { metadata, tool, handler };

package/src/tools/qbd/sales-orders/list-qbd-sales-orders.ts

@@ -1,143 +0,0 @@
-// File generated from our OpenAPI spec by Stainless. See CONTRIBUTING.md for details.
-
-import { Metadata, asErrorResult, asTextContentResult } from 'conductor-node-mcp/tools/types';
-
-import { Tool } from '@modelcontextprotocol/sdk/types.js';
-import Conductor from 'conductor-node';
-
-export const metadata: Metadata = {
-  resource: 'qbd.sales_orders',
-  operation: 'read',
-  tags: [],
-  httpMethod: 'get',
-  httpPath: '/quickbooks-desktop/sales-orders',
-};
-
-export const tool: Tool = {
-  name: 'list_qbd_sales_orders',
-  description: 'Returns a list of sales orders. Use the `cursor` parameter to paginate through the results.',
-  inputSchema: {
-    type: 'object',
-    properties: {
-      conductorEndUserId: {
-        type: 'string',
-        description: 'The ID of the End-User to receive this request.',
-      },
-      currencyIds: {
-        type: 'array',
-        description: 'Filter for sales orders in these currencies.',
-        items: {
-          type: 'string',
-        },
-      },
-      cursor: {
-        type: 'string',
-        description:
-          'The pagination token to fetch the next set of results when paginating with the `limit` parameter. Do not include this parameter on the first call. Use the `nextCursor` value returned in the previous response to request subsequent results.',
-      },
-      customerIds: {
-        type: 'array',
-        description: 'Filter for sales orders created for these customers.',
-        items: {
-          type: 'string',
-        },
-      },
-      ids: {
-        type: 'array',
-        description:
-          'Filter for specific sales orders by their QuickBooks-assigned unique identifier(s).\n\n**IMPORTANT**: If you include this parameter, QuickBooks will ignore all other query parameters for this request.\n\n**NOTE**: If any of the values you specify in this parameter are not found, the request will return an error.',
-        items: {
-          type: 'string',
-        },
-      },
-      includeLineItems: {
-        type: 'boolean',
-        description: 'Whether to include line items in the response. Defaults to `true`.',
-      },
-      includeLinkedTransactions: {
-        type: 'boolean',
-        description:
-          'Whether to include linked transactions in the response. Defaults to `false`. For example, a payment linked to the corresponding sales order.',
-      },
-      limit: {
-        type: 'integer',
-        description:
-          'The maximum number of objects to return. Accepts values ranging from 1 to 150, defaults to 150. When used with cursor-based pagination, this parameter controls how many results are returned per page. To paginate through results, combine this with the `cursor` parameter. Each response will include a `nextCursor` value that can be passed to subsequent requests to retrieve the next page of results.',
-      },
-      refNumberContains: {
-        type: 'string',
-        description:
-          'Filter for sales orders whose `refNumber` contains this substring.\n\n**NOTE**: If you use this parameter, you cannot also use `refNumberStartsWith` or `refNumberEndsWith`.',
-      },
-      refNumberEndsWith: {
-        type: 'string',
-        description:
-          'Filter for sales orders whose `refNumber` ends with this substring.\n\n**NOTE**: If you use this parameter, you cannot also use `refNumberContains` or `refNumberStartsWith`.',
-      },
-      refNumberFrom: {
-        type: 'string',
-        description:
-          'Filter for sales orders whose `refNumber` is greater than or equal to this value. If omitted, the range will begin with the first number of the list. Uses a numerical comparison for values that contain only digits; otherwise, uses a lexicographical comparison.',
-      },
-      refNumbers: {
-        type: 'array',
-        description:
-          'Filter for specific sales orders by their ref-number(s), case-sensitive. In QuickBooks, ref-numbers are not required to be unique and can be arbitrarily changed by the QuickBooks user.\n\n**IMPORTANT**: If you include this parameter, QuickBooks will ignore all other query parameters for this request.\n\n**NOTE**: If any of the values you specify in this parameter are not found, the request will return an error.',
-        items: {
-          type: 'string',
-        },
-      },
-      refNumberStartsWith: {
-        type: 'string',
-        description:
-          'Filter for sales orders whose `refNumber` starts with this substring.\n\n**NOTE**: If you use this parameter, you cannot also use `refNumberContains` or `refNumberEndsWith`.',
-      },
-      refNumberTo: {
-        type: 'string',
-        description:
-          'Filter for sales orders whose `refNumber` is less than or equal to this value. If omitted, the range will end with the last number of the list. Uses a numerical comparison for values that contain only digits; otherwise, uses a lexicographical comparison.',
-      },
-      transactionDateFrom: {
-        type: 'string',
-        description:
-          "Filter for sales orders whose `date` field is on or after this date, in ISO 8601 format (YYYY-MM-DD).\n\n**NOTE:** QuickBooks Desktop interprets this date as the **start of the specified day** in the local timezone of the end-user's computer (e.g., `2025-01-01` → `2025-01-01T00:00:00`).",
-        format: 'date',
-      },
-      transactionDateTo: {
-        type: 'string',
-        description:
-          "Filter for sales orders whose `date` field is on or before this date, in ISO 8601 format (YYYY-MM-DD).\n\n**NOTE:** QuickBooks Desktop interprets this date as the **end of the specified day** in the local timezone of the end-user's computer (e.g., `2025-01-01` → `2025-01-01T23:59:59`).",
-        format: 'date',
-      },
-      updatedAfter: {
-        type: 'string',
-        description:
-          "Filter for sales orders updated on or after this date/time. Accepts the following ISO 8601 formats:\n- **date-only** (YYYY-MM-DD) - QuickBooks Desktop interprets the date as the **start of the specified day** in the local timezone of the end-user's computer (e.g., `2025-01-01` → `2025-01-01T00:00:00`).\n- **datetime without timezone** (YYYY-MM-DDTHH:mm:ss) - QuickBooks Desktop interprets the timestamp in the local timezone of the end-user's computer.\n- **datetime with timezone** (YYYY-MM-DDTHH:mm:ss±HH:mm) - QuickBooks Desktop interprets the timestamp using the specified timezone.",
-      },
-      updatedBefore: {
-        type: 'string',
-        description:
-          "Filter for sales orders updated on or before this date/time. Accepts the following ISO 8601 formats:\n- **date-only** (YYYY-MM-DD) - QuickBooks Desktop interprets the date as the **end of the specified day** in the local timezone of the end-user's computer (e.g., `2025-01-01` → `2025-01-01T23:59:59`).\n- **datetime without timezone** (YYYY-MM-DDTHH:mm:ss) - QuickBooks Desktop interprets the timestamp in the local timezone of the end-user's computer.\n- **datetime with timezone** (YYYY-MM-DDTHH:mm:ss±HH:mm) - QuickBooks Desktop interprets the timestamp using the specified timezone.",
-      },
-    },
-    required: ['conductorEndUserId'],
-  },
-  annotations: {
-    readOnlyHint: true,
-  },
-};
-
-export const handler = async (conductor: Conductor, args: Record<string, unknown> | undefined) => {
-  const body = args as any;
-  const response = await conductor.qbd.salesOrders.list(body).asResponse();
-  try {
-    return asTextContentResult(await response.json());
-  } catch (error) {
-    if (error instanceof Conductor.APIError) {
-      return asErrorResult(error.message);
-    }
-    throw error;
-  }
-};
-
-export default { metadata, tool, handler };