@metronome/mcp 2.1.0 → 3.0.0

package/src/tools/v1/contracts/products/update-contracts-v1-products.ts

@@ -1,164 +0,0 @@
-// File generated from our OpenAPI spec by Stainless. See CONTRIBUTING.md for details.
-
-import { maybeFilter } from '@metronome/mcp/filtering';
-import { Metadata, asTextContentResult } from '@metronome/mcp/tools/types';
-
-import { Tool } from '@modelcontextprotocol/sdk/types.js';
-import Metronome from '@metronome/sdk';
-
-export const metadata: Metadata = {
-  resource: 'v1.contracts.products',
-  operation: 'write',
-  tags: [],
-  httpMethod: 'post',
-  httpPath: '/v1/contract-pricing/products/update',
-  operationId: 'updateProduct-v1',
-};
-
-export const tool: Tool = {
-  name: 'update_contracts_v1_products',
-  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\nUpdates a product's configuration while maintaining billing continuity for active customers. Use this endpoint to modify product names, metrics, pricing rules, and composite settings without disrupting ongoing billing cycles. Changes are scheduled using the starting_at timestamp, which must be on an hour boundary—set future dates to schedule updates ahead of time, or past dates for retroactive changes. Returns the updated product ID upon success. \n\n### Usage guidance: \n- Product type cannot be changed after creation. For incorrect product types, create a new product and archive the original instead.\n\n\n# Response Schema\n```json\n{\n  $ref: '#/$defs/product_update_response',\n  $defs: {\n    product_update_response: {\n      type: 'object',\n      properties: {\n        data: {\n          $ref: '#/$defs/id'\n        }\n      },\n      required: [        'data'\n      ]\n    },\n    id: {\n      type: 'object',\n      properties: {\n        id: {\n          type: 'string'\n        }\n      },\n      required: [        'id'\n      ]\n    }\n  }\n}\n```",
-  inputSchema: {
-    type: 'object',
-    properties: {
-      product_id: {
-        type: 'string',
-        description: 'ID of the product to update',
-      },
-      starting_at: {
-        type: 'string',
-        description:
-          'Timestamp representing when the update should go into effect. It must be on an hour boundary (e.g. 1:00, not 1:30).',
-        format: 'date-time',
-      },
-      billable_metric_id: {
-        type: 'string',
-        description:
-          "Available for USAGE products only. If not provided, defaults to product's current billable metric.",
-      },
-      composite_product_ids: {
-        type: 'array',
-        description:
-          "Available for COMPOSITE products only. If not provided, defaults to product's current composite_product_ids.",
-        items: {
-          type: 'string',
-        },
-      },
-      composite_tags: {
-        type: 'array',
-        description:
-          "Available for COMPOSITE products only. If not provided, defaults to product's current composite_tags.",
-        items: {
-          type: 'string',
-        },
-      },
-      exclude_free_usage: {
-        type: 'boolean',
-        description:
-          'Beta feature only available for composite products. If true, products with $0 will not be included when computing composite usage. Defaults to false',
-      },
-      is_refundable: {
-        type: 'boolean',
-        description:
-          "Defaults to product's current refundability status. This field's availability is dependent on your client's configuration.",
-      },
-      name: {
-        type: 'string',
-        description: "displayed on invoices. If not provided, defaults to product's current name.",
-      },
-      netsuite_internal_item_id: {
-        type: 'string',
-        description:
-          "If not provided, defaults to product's current netsuite_internal_item_id. This field's availability is dependent on your client's configuration.",
-      },
-      netsuite_overage_item_id: {
-        type: 'string',
-        description:
-          "Available for USAGE and COMPOSITE products only. If not provided, defaults to product's current netsuite_overage_item_id. This field's availability is dependent on your client's configuration.",
-      },
-      presentation_group_key: {
-        type: 'array',
-        description:
-          'For USAGE products only. Groups usage line items on invoices. The superset of values in the pricing group key and presentation group key must be set as one compound group key on the billable metric.',
-        items: {
-          type: 'string',
-        },
-      },
-      pricing_group_key: {
-        type: 'array',
-        description:
-          'For USAGE products only. If set, pricing for this product will be determined for each pricing_group_key value, as opposed to the product as a whole. The superset of values in the pricing group key and presentation group key must be set as one compound group key on the billable metric.',
-        items: {
-          type: 'string',
-        },
-      },
-      quantity_conversion: {
-        $ref: '#/$defs/quantity_conversion',
-      },
-      quantity_rounding: {
-        $ref: '#/$defs/quantity_rounding',
-      },
-      tags: {
-        type: 'array',
-        description: "If not provided, defaults to product's current tags",
-        items: {
-          type: 'string',
-        },
-      },
-      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: ['product_id', 'starting_at'],
-    $defs: {
-      quantity_conversion: {
-        type: 'object',
-        description:
-          'Optional. Only valid for USAGE products. If provided, the quantity will be converted using the provided conversion factor and operation. For example, if the operation is "multiply" and the conversion factor is 100, then the quantity will be multiplied by 100. This can be used in cases where data is sent in one unit and priced in another.  For example, data could be sent in MB and priced in GB. In this case, the conversion factor would be 1024 and the operation would be "divide".',
-        properties: {
-          conversion_factor: {
-            type: 'number',
-            description: 'The factor to multiply or divide the quantity by.',
-          },
-          operation: {
-            type: 'string',
-            description: 'The operation to perform on the quantity',
-            enum: ['MULTIPLY', 'DIVIDE'],
-          },
-          name: {
-            type: 'string',
-            description: 'Optional name for this conversion.',
-          },
-        },
-        required: ['conversion_factor', 'operation'],
-      },
-      quantity_rounding: {
-        type: 'object',
-        description:
-          'Optional. Only valid for USAGE products. If provided, the quantity will be rounded using the provided rounding method and decimal places. For example, if the method is "round up" and the decimal places is 0, then the quantity will be rounded up to the nearest integer.',
-        properties: {
-          decimal_places: {
-            type: 'number',
-          },
-          rounding_method: {
-            type: 'string',
-            enum: ['ROUND_UP', 'ROUND_DOWN', 'ROUND_HALF_UP'],
-          },
-        },
-        required: ['decimal_places', 'rounding_method'],
-      },
-    },
-  },
-  annotations: {},
-};
-
-export const handler = async (client: Metronome, args: Record<string, unknown> | undefined) => {
-  const { jq_filter, ...body } = args as any;
-  return asTextContentResult(await maybeFilter(jq_filter, await client.v1.contracts.products.update(body)));
-};
-
-export default { metadata, tool, handler };

package/src/tools/v1/contracts/rate-cards/archive-contracts-v1-rate-cards.ts

@@ -1,45 +0,0 @@
-// File generated from our OpenAPI spec by Stainless. See CONTRIBUTING.md for details.
-
-import { maybeFilter } from '@metronome/mcp/filtering';
-import { Metadata, asTextContentResult } from '@metronome/mcp/tools/types';
-
-import { Tool } from '@modelcontextprotocol/sdk/types.js';
-import Metronome from '@metronome/sdk';
-
-export const metadata: Metadata = {
-  resource: 'v1.contracts.rateCards',
-  operation: 'write',
-  tags: [],
-  httpMethod: 'post',
-  httpPath: '/v1/contract-pricing/rate-cards/archive',
-  operationId: 'archiveRateCard-v1',
-};
-
-export const tool: Tool = {
-  name: 'archive_contracts_v1_rate_cards',
-  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 disable a rate card by archiving it, preventing use in new contracts while preserving existing contract pricing. Use this when retiring old pricing models, consolidating rate cards, or removing outdated pricing structures. Returns the archived rate card ID and stops the rate card from appearing in contract creation workflows.\n\n\n# Response Schema\n```json\n{\n  $ref: '#/$defs/rate_card_archive_response',\n  $defs: {\n    rate_card_archive_response: {\n      type: 'object',\n      properties: {\n        data: {\n          $ref: '#/$defs/id'\n        }\n      },\n      required: [        'data'\n      ]\n    },\n    id: {\n      type: 'object',\n      properties: {\n        id: {\n          type: 'string'\n        }\n      },\n      required: [        'id'\n      ]\n    }\n  }\n}\n```",
-  inputSchema: {
-    type: 'object',
-    properties: {
-      id: {
-        type: 'string',
-      },
-      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'],
-  },
-  annotations: {},
-};
-
-export const handler = async (client: Metronome, args: Record<string, unknown> | undefined) => {
-  const { jq_filter, ...body } = args as any;
-  return asTextContentResult(await maybeFilter(jq_filter, await client.v1.contracts.rateCards.archive(body)));
-};
-
-export default { metadata, tool, handler };

package/src/tools/v1/contracts/rate-cards/create-contracts-v1-rate-cards.ts

@@ -1,97 +0,0 @@
-// File generated from our OpenAPI spec by Stainless. See CONTRIBUTING.md for details.
-
-import { maybeFilter } from '@metronome/mcp/filtering';
-import { Metadata, asTextContentResult } from '@metronome/mcp/tools/types';
-
-import { Tool } from '@modelcontextprotocol/sdk/types.js';
-import Metronome from '@metronome/sdk';
-
-export const metadata: Metadata = {
-  resource: 'v1.contracts.rateCards',
-  operation: 'write',
-  tags: [],
-  httpMethod: 'post',
-  httpPath: '/v1/contract-pricing/rate-cards/create',
-  operationId: 'createRateCard-v1',
-};
-
-export const tool: Tool = {
-  name: 'create_contracts_v1_rate_cards',
-  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\nIn Metronome, the rate card is the central location for your pricing. Rate cards were built with new product launches and pricing changes in mind - you can update your products and pricing in one place, and that change will be automatically propagated across your customer cohorts. Most clients need only maintain one or a few rate cards within Metronome.\n\n### Use this endpoint to:\n- Create a rate card with a name and description\n- Define the rate card's single underlying fiat currency, and any number of conversion rates between that fiat currency and custom pricing units. You can then add products and associated rates in the fiat currency or custom pricing unit for which you have defined a conversion rate. \n- Set aliases for the rate card. Aliases are human-readable names that you can use in the place of the id of the rate card when provisioning a customer's contract. By using an alias, you can easily create a contract and provision a customer by choosing the paygo rate card, without storing the rate card id in your internal systems. This is helpful when launching a new rate card for paygo customers, you can update the alias for paygo to be scheduled to be assigned to the new rate card without updating your code.\n\n### Key response fields:\n- The ID of the rate card you just created\n\n### Usage guidelines:\n- After creating a rate card, you can now use the addRate or addRates endpoints to add products and their prices to it\n- A rate card alias can only be used by one rate card at a time. If you create a contract with a rate card alias that is already in use by another rate card, the original rate card's alias schedule will be updated. The alias will reference the rate card to which it was most recently assigned.\n\n\n# Response Schema\n```json\n{\n  $ref: '#/$defs/rate_card_create_response',\n  $defs: {\n    rate_card_create_response: {\n      type: 'object',\n      properties: {\n        data: {\n          $ref: '#/$defs/id'\n        }\n      },\n      required: [        'data'\n      ]\n    },\n    id: {\n      type: 'object',\n      properties: {\n        id: {\n          type: 'string'\n        }\n      },\n      required: [        'id'\n      ]\n    }\n  }\n}\n```",
-  inputSchema: {
-    type: 'object',
-    properties: {
-      name: {
-        type: 'string',
-        description: 'Used only in UI/API. It is not exposed to end customers.',
-      },
-      aliases: {
-        type: 'array',
-        description:
-          'Reference this alias when creating a contract. If the same alias is assigned to multiple rate cards, it will reference the rate card to which it was most recently assigned. It is not exposed to end customers.',
-        items: {
-          type: 'object',
-          properties: {
-            name: {
-              type: 'string',
-            },
-            ending_before: {
-              type: 'string',
-              format: 'date-time',
-            },
-            starting_at: {
-              type: 'string',
-              format: 'date-time',
-            },
-          },
-          required: ['name'],
-        },
-      },
-      credit_type_conversions: {
-        type: 'array',
-        description: 'Required when using custom pricing units in rates.',
-        items: {
-          type: 'object',
-          properties: {
-            custom_credit_type_id: {
-              type: 'string',
-            },
-            fiat_per_custom_credit: {
-              type: 'number',
-            },
-          },
-          required: ['custom_credit_type_id', 'fiat_per_custom_credit'],
-        },
-      },
-      custom_fields: {
-        type: 'object',
-        description: 'Custom fields to be added eg. { "key1": "value1", "key2": "value2" }',
-        additionalProperties: true,
-      },
-      description: {
-        type: 'string',
-      },
-      fiat_credit_type_id: {
-        type: 'string',
-        description:
-          'The Metronome ID of the credit type to associate with the rate card, defaults to USD (cents) if not passed.',
-      },
-      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: ['name'],
-  },
-  annotations: {},
-};
-
-export const handler = async (client: Metronome, args: Record<string, unknown> | undefined) => {
-  const { jq_filter, ...body } = args as any;
-  return asTextContentResult(await maybeFilter(jq_filter, await client.v1.contracts.rateCards.create(body)));
-};
-
-export default { metadata, tool, handler };

package/src/tools/v1/contracts/rate-cards/list-contracts-v1-rate-cards.ts

@@ -1,55 +0,0 @@
-// File generated from our OpenAPI spec by Stainless. See CONTRIBUTING.md for details.
-
-import { maybeFilter } from '@metronome/mcp/filtering';
-import { Metadata, asTextContentResult } from '@metronome/mcp/tools/types';
-
-import { Tool } from '@modelcontextprotocol/sdk/types.js';
-import Metronome from '@metronome/sdk';
-
-export const metadata: Metadata = {
-  resource: 'v1.contracts.rateCards',
-  operation: 'write',
-  tags: [],
-  httpMethod: 'post',
-  httpPath: '/v1/contract-pricing/rate-cards/list',
-  operationId: 'listRateCards-v1',
-};
-
-export const tool: Tool = {
-  name: 'list_contracts_v1_rate_cards',
-  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\nList all rate cards. Returns rate card IDs, names, descriptions, aliases, and other details. To view the rates associated with a given rate card, use the getRates or getRateSchedule endpoints.\n\n\n# Response Schema\n```json\n{\n  type: 'object',\n  properties: {\n    data: {\n      type: 'array',\n      items: {\n        $ref: '#/$defs/rate_card_list_response'\n      }\n    },\n    next_page: {\n      type: 'string'\n    }\n  },\n  required: [    'data',\n    'next_page'\n  ],\n  $defs: {\n    rate_card_list_response: {\n      type: 'object',\n      properties: {\n        id: {\n          type: 'string'\n        },\n        created_at: {\n          type: 'string',\n          format: 'date-time'\n        },\n        created_by: {\n          type: 'string'\n        },\n        name: {\n          type: 'string'\n        },\n        aliases: {\n          type: 'array',\n          items: {\n            type: 'object',\n            properties: {\n              name: {\n                type: 'string'\n              },\n              ending_before: {\n                type: 'string',\n                format: 'date-time'\n              },\n              starting_at: {\n                type: 'string',\n                format: 'date-time'\n              }\n            },\n            required: [              'name'\n            ]\n          }\n        },\n        credit_type_conversions: {\n          type: 'array',\n          items: {\n            type: 'object',\n            properties: {\n              custom_credit_type: {\n                $ref: '#/$defs/credit_type_data'\n              },\n              fiat_per_custom_credit: {\n                type: 'string'\n              }\n            },\n            required: [              'custom_credit_type',\n              'fiat_per_custom_credit'\n            ]\n          }\n        },\n        custom_fields: {\n          type: 'object',\n          description: 'Custom fields to be added eg. { \"key1\": \"value1\", \"key2\": \"value2\" }',\n          additionalProperties: true\n        },\n        description: {\n          type: 'string'\n        },\n        fiat_credit_type: {\n          $ref: '#/$defs/credit_type_data'\n        }\n      },\n      required: [        'id',\n        'created_at',\n        'created_by',\n        'name'\n      ]\n    },\n    credit_type_data: {\n      type: 'object',\n      properties: {\n        id: {\n          type: 'string'\n        },\n        name: {\n          type: 'string'\n        }\n      },\n      required: [        'id',\n        'name'\n      ]\n    }\n  }\n}\n```",
-  inputSchema: {
-    type: 'object',
-    properties: {
-      limit: {
-        type: 'integer',
-        description: 'Max number of results that should be returned',
-      },
-      next_page: {
-        type: 'string',
-        description: 'Cursor that indicates where the next page of results should start.',
-      },
-      body: {
-        type: 'object',
-        additionalProperties: true,
-      },
-      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: [],
-  },
-  annotations: {},
-};
-
-export const handler = async (client: Metronome, args: Record<string, unknown> | undefined) => {
-  const { jq_filter, ...body } = args as any;
-  const response = await client.v1.contracts.rateCards.list(body).asResponse();
-  return asTextContentResult(await maybeFilter(jq_filter, await response.json()));
-};
-
-export default { metadata, tool, handler };

package/src/tools/v1/contracts/rate-cards/named-schedules/retrieve-rate-cards-contracts-v1-named-schedules.ts

@@ -1,62 +0,0 @@
-// File generated from our OpenAPI spec by Stainless. See CONTRIBUTING.md for details.
-
-import { maybeFilter } from '@metronome/mcp/filtering';
-import { Metadata, asTextContentResult } from '@metronome/mcp/tools/types';
-
-import { Tool } from '@modelcontextprotocol/sdk/types.js';
-import Metronome from '@metronome/sdk';
-
-export const metadata: Metadata = {
-  resource: 'v1.contracts.rateCards.named_schedules',
-  operation: 'write',
-  tags: [],
-  httpMethod: 'post',
-  httpPath: '/v1/contracts/getNamedSchedule',
-  operationId: 'getContractNamedSchedule-v1',
-};
-
-export const tool: Tool = {
-  name: 'retrieve_rate_cards_contracts_v1_named_schedules',
-  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\nGet a named schedule for the given contract. This endpoint's availability is dependent on your client's configuration.\n\n# Response Schema\n```json\n{\n  $ref: '#/$defs/named_schedule_retrieve_response',\n  $defs: {\n    named_schedule_retrieve_response: {\n      type: 'object',\n      properties: {\n        data: {\n          type: 'array',\n          items: {\n            type: 'object',\n            properties: {\n              starting_at: {\n                type: 'string',\n                format: 'date-time'\n              },\n              value: {\n                type: 'object',\n                additionalProperties: true\n              },\n              ending_before: {\n                type: 'string',\n                format: 'date-time'\n              }\n            },\n            required: [              'starting_at',\n              'value'\n            ]\n          }\n        }\n      },\n      required: [        'data'\n      ]\n    }\n  }\n}\n```",
-  inputSchema: {
-    type: 'object',
-    properties: {
-      contract_id: {
-        type: 'string',
-        description: 'ID of the contract whose named schedule is to be retrieved',
-      },
-      customer_id: {
-        type: 'string',
-        description: 'ID of the customer whose named schedule is to be retrieved',
-      },
-      schedule_name: {
-        type: 'string',
-        description: 'The identifier for the schedule to be retrieved',
-      },
-      covering_date: {
-        type: 'string',
-        description:
-          'If provided, at most one schedule segment will be returned (the one that covers this date). If not provided, all segments will be returned.',
-        format: 'date-time',
-      },
-      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: ['contract_id', 'customer_id', 'schedule_name'],
-  },
-  annotations: {},
-};
-
-export const handler = async (client: Metronome, args: Record<string, unknown> | undefined) => {
-  const { jq_filter, ...body } = args as any;
-  return asTextContentResult(
-    await maybeFilter(jq_filter, await client.v1.contracts.rateCards.namedSchedules.retrieve(body)),
-  );
-};
-
-export default { metadata, tool, handler };

package/src/tools/v1/contracts/rate-cards/named-schedules/update-rate-cards-contracts-v1-named-schedules.ts

@@ -1,62 +0,0 @@
-// File generated from our OpenAPI spec by Stainless. See CONTRIBUTING.md for details.
-
-import { Metadata, asTextContentResult } from '@metronome/mcp/tools/types';
-
-import { Tool } from '@modelcontextprotocol/sdk/types.js';
-import Metronome from '@metronome/sdk';
-
-export const metadata: Metadata = {
-  resource: 'v1.contracts.rateCards.named_schedules',
-  operation: 'write',
-  tags: [],
-  httpMethod: 'post',
-  httpPath: '/v1/contracts/updateNamedSchedule',
-  operationId: 'updateContractNamedSchedule-v1',
-};
-
-export const tool: Tool = {
-  name: 'update_rate_cards_contracts_v1_named_schedules',
-  description:
-    "Update a named schedule for the given contract. This endpoint's availability is dependent on your client's configuration.",
-  inputSchema: {
-    type: 'object',
-    properties: {
-      contract_id: {
-        type: 'string',
-        description: 'ID of the contract whose named schedule is to be updated',
-      },
-      customer_id: {
-        type: 'string',
-        description: 'ID of the customer whose named schedule is to be updated',
-      },
-      schedule_name: {
-        type: 'string',
-        description: 'The identifier for the schedule to be updated',
-      },
-      starting_at: {
-        type: 'string',
-        format: 'date-time',
-      },
-      value: {
-        type: 'object',
-        description:
-          'The value to set for the named schedule. The structure of this object is specific to the named schedule.',
-        additionalProperties: true,
-      },
-      ending_before: {
-        type: 'string',
-        format: 'date-time',
-      },
-    },
-    required: ['contract_id', 'customer_id', 'schedule_name', 'starting_at', 'value'],
-  },
-  annotations: {},
-};
-
-export const handler = async (client: Metronome, args: Record<string, unknown> | undefined) => {
-  const body = args as any;
-  const response = await client.v1.contracts.rateCards.namedSchedules.update(body).asResponse();
-  return asTextContentResult(await response.text());
-};
-
-export default { metadata, tool, handler };

package/src/tools/v1/contracts/rate-cards/product-orders/set-rate-cards-contracts-v1-product-orders.ts

@@ -1,54 +0,0 @@
-// File generated from our OpenAPI spec by Stainless. See CONTRIBUTING.md for details.
-
-import { maybeFilter } from '@metronome/mcp/filtering';
-import { Metadata, asTextContentResult } from '@metronome/mcp/tools/types';
-
-import { Tool } from '@modelcontextprotocol/sdk/types.js';
-import Metronome from '@metronome/sdk';
-
-export const metadata: Metadata = {
-  resource: 'v1.contracts.rateCards.product_orders',
-  operation: 'write',
-  tags: [],
-  httpMethod: 'post',
-  httpPath: '/v1/contract-pricing/rate-cards/setRateCardProductsOrder',
-  operationId: 'setRateCardProductsOrder-v1',
-};
-
-export const tool: Tool = {
-  name: 'set_rate_cards_contracts_v1_product_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\nThe ordering of products on a rate card determines the order in which the products will appear on customers' invoices. Use this endpoint to set the order of products on the rate card.\n\n\n# Response Schema\n```json\n{\n  $ref: '#/$defs/product_order_set_response',\n  $defs: {\n    product_order_set_response: {\n      type: 'object',\n      properties: {\n        data: {\n          $ref: '#/$defs/id'\n        }\n      },\n      required: [        'data'\n      ]\n    },\n    id: {\n      type: 'object',\n      properties: {\n        id: {\n          type: 'string'\n        }\n      },\n      required: [        'id'\n      ]\n    }\n  }\n}\n```",
-  inputSchema: {
-    type: 'object',
-    properties: {
-      product_order: {
-        type: 'array',
-        items: {
-          type: 'string',
-        },
-      },
-      rate_card_id: {
-        type: 'string',
-        description: 'ID of the rate card to update',
-      },
-      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: ['product_order', 'rate_card_id'],
-  },
-  annotations: {},
-};
-
-export const handler = async (client: Metronome, args: Record<string, unknown> | undefined) => {
-  const { jq_filter, ...body } = args as any;
-  return asTextContentResult(
-    await maybeFilter(jq_filter, await client.v1.contracts.rateCards.productOrders.set(body)),
-  );
-};
-
-export default { metadata, tool, handler };

package/src/tools/v1/contracts/rate-cards/product-orders/update-rate-cards-contracts-v1-product-orders.ts

@@ -1,65 +0,0 @@
-// File generated from our OpenAPI spec by Stainless. See CONTRIBUTING.md for details.
-
-import { maybeFilter } from '@metronome/mcp/filtering';
-import { Metadata, asTextContentResult } from '@metronome/mcp/tools/types';
-
-import { Tool } from '@modelcontextprotocol/sdk/types.js';
-import Metronome from '@metronome/sdk';
-
-export const metadata: Metadata = {
-  resource: 'v1.contracts.rateCards.product_orders',
-  operation: 'write',
-  tags: [],
-  httpMethod: 'post',
-  httpPath: '/v1/contract-pricing/rate-cards/moveRateCardProducts',
-  operationId: 'moveRateCardProducts-v1',
-};
-
-export const tool: Tool = {
-  name: 'update_rate_cards_contracts_v1_product_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\nThe ordering of products on a rate card determines the order in which the products will appear on customers' invoices. Use this endpoint to set the order of specific products on the rate card by moving them relative to their current location.\n\n\n# Response Schema\n```json\n{\n  $ref: '#/$defs/product_order_update_response',\n  $defs: {\n    product_order_update_response: {\n      type: 'object',\n      properties: {\n        data: {\n          $ref: '#/$defs/id'\n        }\n      },\n      required: [        'data'\n      ]\n    },\n    id: {\n      type: 'object',\n      properties: {\n        id: {\n          type: 'string'\n        }\n      },\n      required: [        'id'\n      ]\n    }\n  }\n}\n```",
-  inputSchema: {
-    type: 'object',
-    properties: {
-      product_moves: {
-        type: 'array',
-        items: {
-          type: 'object',
-          properties: {
-            position: {
-              type: 'number',
-              description: '0-based index of the new position of the product',
-            },
-            product_id: {
-              type: 'string',
-              description: 'ID of the product to move',
-            },
-          },
-          required: ['position', 'product_id'],
-        },
-      },
-      rate_card_id: {
-        type: 'string',
-        description: 'ID of the rate card to update',
-      },
-      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: ['product_moves', 'rate_card_id'],
-  },
-  annotations: {},
-};
-
-export const handler = async (client: Metronome, args: Record<string, unknown> | undefined) => {
-  const { jq_filter, ...body } = args as any;
-  return asTextContentResult(
-    await maybeFilter(jq_filter, await client.v1.contracts.rateCards.productOrders.update(body)),
-  );
-};
-
-export default { metadata, tool, handler };