@metronome/mcp 2.2.0 → 3.0.0

package/src/tools/v1/contracts/list-balances-v1-contracts.ts

@@ -1,93 +0,0 @@
-// File generated from our OpenAPI spec by Stainless. See CONTRIBUTING.md for details.
-
-import { Metadata, asErrorResult, 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',
-  operation: 'write',
-  tags: [],
-  httpMethod: 'post',
-  httpPath: '/v1/contracts/customerBalances/list',
-  operationId: 'listCustomerBalances-v1',
-};
-
-export const tool: Tool = {
-  name: 'list_balances_v1_contracts',
-  description:
-    'Retrieve a comprehensive view of all available balances (commits and credits) for a customer. This endpoint provides real-time visibility into prepaid funds, postpaid commitments, promotional credits, and other balance types that can offset usage charges, helping you build transparent billing experiences.\n\n### Use this endpoint to:\n- Display current available balances in customer dashboards\n- Verify available funds before approving high-usage operations\n- Generate balance reports for finance teams\n- Filter balances by contract or date ranges\n\n### Key response fields:\nAn array of balance objects (all credits and commits) containing:\n\n- Balance details: Current available amount for each commit or credit\n- Metadata: Product associations, priorities, applicable date ranges\n- Optional ledger entries: Detailed transaction history (if `include_ledgers=true`)\n- Balance calculations: Including pending transactions and future-dated entries\n- Custom fields: Any additional metadata attached to balances\n\n### Usage guidelines:\n- Date filtering: Use `effective_before` to include only balances with access before a specific date (exclusive)\n- Set `include_balance=true` for calculated balance amounts on each commit or credit\n- Set `include_ledgers=true` for full transaction history\n- Set `include_contract_balances = true` to see contract level balances\n- Balance logic: Reflects currently accessible amounts, excluding expired/future segments\n- Manual adjustments: Includes all manual ledger entries, even future-dated ones\n',
-  inputSchema: {
-    type: 'object',
-    properties: {
-      customer_id: {
-        type: 'string',
-      },
-      id: {
-        type: 'string',
-      },
-      covering_date: {
-        type: 'string',
-        description: 'Return only balances that have access schedules that "cover" the provided date',
-        format: 'date-time',
-      },
-      effective_before: {
-        type: 'string',
-        description: 'Include only balances that have any access before the provided date (exclusive)',
-        format: 'date-time',
-      },
-      exclude_zero_balances: {
-        type: 'boolean',
-        description: 'Exclude balances with zero amounts from the response.',
-      },
-      include_archived: {
-        type: 'boolean',
-        description: 'Include archived credits and credits from archived contracts.',
-      },
-      include_balance: {
-        type: 'boolean',
-        description:
-          'Include the balance of credits and commits in the response. Setting this flag may cause the query to be slower.',
-      },
-      include_contract_balances: {
-        type: 'boolean',
-        description: 'Include balances on the contract level.',
-      },
-      include_ledgers: {
-        type: 'boolean',
-        description: 'Include ledgers in the response. Setting this flag may cause the query to be slower.',
-      },
-      limit: {
-        type: 'integer',
-        description: 'The maximum number of commits to return. Defaults to 25.',
-      },
-      next_page: {
-        type: 'string',
-        description: 'The next page token from a previous response.',
-      },
-      starting_at: {
-        type: 'string',
-        description: 'Include only balances that have any access on or after the provided date',
-        format: 'date-time',
-      },
-    },
-    required: ['customer_id'],
-  },
-  annotations: {},
-};
-
-export const handler = async (client: Metronome, args: Record<string, unknown> | undefined) => {
-  const body = args as any;
-  const response = await client.v1.contracts.listBalances(body).asResponse();
-  try {
-    return asTextContentResult(await response.json());
-  } catch (error) {
-    if (error instanceof Metronome.APIError) {
-      return asErrorResult(error.message);
-    }
-    throw error;
-  }
-};
-
-export default { metadata, tool, handler };

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

@@ -1,71 +0,0 @@
-// File generated from our OpenAPI spec by Stainless. See CONTRIBUTING.md for details.
-
-import { Metadata, asErrorResult, 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',
-  operation: 'write',
-  tags: [],
-  httpMethod: 'post',
-  httpPath: '/v1/contracts/list',
-  operationId: 'listContracts-v1',
-};
-
-export const tool: Tool = {
-  name: 'list_v1_contracts',
-  description:
-    "Retrieves all contracts for a specific customer, including pricing, terms, credits, and commitments. Use this to view a customer's contract history and current agreements for billing management. Returns contract details with optional ledgers and balance information. \n\n⚠️ Note: This is the legacy v1 endpoint - new integrations should use the v2 endpoint for enhanced features.\n",
-  inputSchema: {
-    type: 'object',
-    properties: {
-      customer_id: {
-        type: 'string',
-      },
-      covering_date: {
-        type: 'string',
-        description:
-          'Optional RFC 3339 timestamp. If provided, the response will include only contracts effective on the provided date.  This cannot be provided if the starting_at filter is provided.',
-        format: 'date-time',
-      },
-      include_archived: {
-        type: 'boolean',
-        description: 'Include archived contracts in the response',
-      },
-      include_balance: {
-        type: 'boolean',
-        description:
-          'Include the balance of credits and commits in the response. Setting this flag may cause the query to be slower.',
-      },
-      include_ledgers: {
-        type: 'boolean',
-        description:
-          'Include commit ledgers in the response. Setting this flag may cause the query to be slower.',
-      },
-      starting_at: {
-        type: 'string',
-        description:
-          'Optional RFC 3339 timestamp. If provided, the response will include only contracts where effective_at is on or after the provided date.  This cannot be provided if the covering_date filter is provided.',
-        format: 'date-time',
-      },
-    },
-    required: ['customer_id'],
-  },
-  annotations: {},
-};
-
-export const handler = async (client: Metronome, args: Record<string, unknown> | undefined) => {
-  const body = args as any;
-  try {
-    return asTextContentResult(await client.v1.contracts.list(body));
-  } catch (error) {
-    if (error instanceof Metronome.APIError) {
-      return asErrorResult(error.message);
-    }
-    throw error;
-  }
-};
-
-export default { metadata, tool, handler };

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

@@ -1,65 +0,0 @@
-// File generated from our OpenAPI spec by Stainless. See CONTRIBUTING.md for details.
-
-import { isJqError, maybeFilter } from '@metronome/mcp/filtering';
-import { Metadata, asErrorResult, 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.named_schedules',
-  operation: 'write',
-  tags: [],
-  httpMethod: 'post',
-  httpPath: '/v1/contract-pricing/rate-cards/getNamedSchedule',
-  operationId: 'getRateCardNamedSchedule-v1',
-};
-
-export const tool: Tool = {
-  name: 'retrieve_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 rate card. 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: {
-      rate_card_id: {
-        type: 'string',
-        description: 'ID of the rate card 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: ['rate_card_id', 'schedule_name'],
-  },
-  annotations: {},
-};
-
-export const handler = async (client: Metronome, args: Record<string, unknown> | undefined) => {
-  const { jq_filter, ...body } = args as any;
-  try {
-    return asTextContentResult(
-      await maybeFilter(jq_filter, await client.v1.contracts.namedSchedules.retrieve(body)),
-    );
-  } catch (error) {
-    if (error instanceof Metronome.APIError || isJqError(error)) {
-      return asErrorResult(error.message);
-    }
-    throw error;
-  }
-};
-
-export default { metadata, tool, handler };

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

@@ -1,58 +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.named_schedules',
-  operation: 'write',
-  tags: [],
-  httpMethod: 'post',
-  httpPath: '/v1/contract-pricing/rate-cards/updateNamedSchedule',
-  operationId: 'updateRateCardNamedSchedule-v1',
-};
-
-export const tool: Tool = {
-  name: 'update_contracts_v1_named_schedules',
-  description:
-    "Update a named schedule for the given rate card. This endpoint's availability is dependent on your client's configuration.",
-  inputSchema: {
-    type: 'object',
-    properties: {
-      rate_card_id: {
-        type: 'string',
-        description: 'ID of the rate card 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: ['rate_card_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.namedSchedules.update(body).asResponse();
-  return asTextContentResult(await response.text());
-};
-
-export default { metadata, tool, handler };

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

@@ -1,55 +0,0 @@
-// File generated from our OpenAPI spec by Stainless. See CONTRIBUTING.md for details.
-
-import { isJqError, maybeFilter } from '@metronome/mcp/filtering';
-import { Metadata, asErrorResult, 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/archive',
-  operationId: 'archiveProductListItem-v1',
-};
-
-export const tool: Tool = {
-  name: 'archive_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\nArchive a product. Any current rate cards associated with this product will continue to function as normal. However, it will no longer be available as an option for newly created rates. Once you archive a product, you can still retrieve it in the UI and API, but you cannot unarchive it.\n\n\n# Response Schema\n```json\n{\n  $ref: '#/$defs/product_archive_response',\n  $defs: {\n    product_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: {
-      product_id: {
-        type: 'string',
-        description: 'ID of the product to be archived',
-      },
-      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'],
-  },
-  annotations: {},
-};
-
-export const handler = async (client: Metronome, args: Record<string, unknown> | undefined) => {
-  const { jq_filter, ...body } = args as any;
-  try {
-    return asTextContentResult(
-      await maybeFilter(jq_filter, await client.v1.contracts.products.archive(body)),
-    );
-  } catch (error) {
-    if (error instanceof Metronome.APIError || isJqError(error)) {
-      return asErrorResult(error.message);
-    }
-    throw error;
-  }
-};
-
-export default { metadata, tool, handler };

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

@@ -1,164 +0,0 @@
-// File generated from our OpenAPI spec by Stainless. See CONTRIBUTING.md for details.
-
-import { isJqError, maybeFilter } from '@metronome/mcp/filtering';
-import { Metadata, asErrorResult, 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/create',
-  operationId: 'createProduct-v1',
-};
-
-export const tool: Tool = {
-  name: 'create_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\nCreate a new product object. Products in Metronome represent your company's individual product or service offerings. A Product can be thought of as the basic unit of a line item on the invoice. This is analogous to SKUs or items in an ERP system. Give the product a meaningful name as they will appear on customer invoices.\n\n\n# Response Schema\n```json\n{\n  $ref: '#/$defs/product_create_response',\n  $defs: {\n    product_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: 'displayed on invoices',
-      },
-      type: {
-        type: 'string',
-        enum: ['FIXED', 'USAGE', 'COMPOSITE', 'SUBSCRIPTION', 'PROFESSIONAL_SERVICE', 'PRO_SERVICE'],
-      },
-      billable_metric_id: {
-        type: 'string',
-        description: 'Required for USAGE products',
-      },
-      composite_product_ids: {
-        type: 'array',
-        description: 'Required for COMPOSITE products',
-        items: {
-          type: 'string',
-        },
-      },
-      composite_tags: {
-        type: 'array',
-        description: 'Required for COMPOSITE products',
-        items: {
-          type: 'string',
-        },
-      },
-      custom_fields: {
-        type: 'object',
-        description: 'Custom fields to be added eg. { "key1": "value1", "key2": "value2" }',
-        additionalProperties: true,
-      },
-      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:
-          "This field's availability is dependent on your client's configuration. Defaults to true.",
-      },
-      netsuite_internal_item_id: {
-        type: 'string',
-        description: "This field's availability is dependent on your client's configuration.",
-      },
-      netsuite_overage_item_id: {
-        type: 'string',
-        description: "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',
-        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: ['name', 'type'],
-    $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;
-  try {
-    return asTextContentResult(await maybeFilter(jq_filter, await client.v1.contracts.products.create(body)));
-  } catch (error) {
-    if (error instanceof Metronome.APIError || isJqError(error)) {
-      return asErrorResult(error.message);
-    }
-    throw error;
-  }
-};
-
-export default { metadata, tool, handler };

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

@@ -1,63 +0,0 @@
-// File generated from our OpenAPI spec by Stainless. See CONTRIBUTING.md for details.
-
-import { isJqError, maybeFilter } from '@metronome/mcp/filtering';
-import { Metadata, asErrorResult, 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/list',
-  operationId: 'listProducts-v1',
-};
-
-export const tool: Tool = {
-  name: 'list_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\nGet a paginated list of all products in your organization with their complete configuration, version history, and metadata. By default excludes archived products unless explicitly requested via the `archive_filter` parameter.\n\n\n# Response Schema\n```json\n{\n  type: 'object',\n  properties: {\n    data: {\n      type: 'array',\n      items: {\n        $ref: '#/$defs/product_list_response'\n      }\n    },\n    next_page: {\n      type: 'string'\n    }\n  },\n  required: [    'data',\n    'next_page'\n  ],\n  $defs: {\n    product_list_response: {\n      type: 'object',\n      properties: {\n        id: {\n          type: 'string'\n        },\n        current: {\n          $ref: '#/$defs/product_list_item_state'\n        },\n        initial: {\n          $ref: '#/$defs/product_list_item_state'\n        },\n        type: {\n          type: 'string',\n          enum: [            'USAGE',\n            'SUBSCRIPTION',\n            'COMPOSITE',\n            'FIXED',\n            'PRO_SERVICE'\n          ]\n        },\n        updates: {\n          type: 'array',\n          items: {\n            type: 'object',\n            properties: {\n              created_at: {\n                type: 'string',\n                format: 'date-time'\n              },\n              created_by: {\n                type: 'string'\n              },\n              billable_metric_id: {\n                type: 'string'\n              },\n              composite_product_ids: {\n                type: 'array',\n                items: {\n                  type: 'string'\n                }\n              },\n              composite_tags: {\n                type: 'array',\n                items: {\n                  type: 'string'\n                }\n              },\n              exclude_free_usage: {\n                type: 'boolean'\n              },\n              is_refundable: {\n                type: 'boolean'\n              },\n              name: {\n                type: 'string'\n              },\n              netsuite_internal_item_id: {\n                type: 'string',\n                description: 'This field\\'s availability is dependent on your client\\'s configuration.'\n              },\n              netsuite_overage_item_id: {\n                type: 'string',\n                description: 'This field\\'s availability is dependent on your client\\'s configuration.'\n              },\n              presentation_group_key: {\n                type: 'array',\n                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.',\n                items: {\n                  type: 'string'\n                }\n              },\n              pricing_group_key: {\n                type: 'array',\n                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.',\n                items: {\n                  type: 'string'\n                }\n              },\n              quantity_conversion: {\n                $ref: '#/$defs/quantity_conversion'\n              },\n              quantity_rounding: {\n                $ref: '#/$defs/quantity_rounding'\n              },\n              starting_at: {\n                type: 'string',\n                format: 'date-time'\n              },\n              tags: {\n                type: 'array',\n                items: {\n                  type: 'string'\n                }\n              }\n            },\n            required: [              'created_at',\n              'created_by'\n            ]\n          }\n        },\n        archived_at: {\n          type: 'string',\n          format: 'date-time'\n        },\n        custom_fields: {\n          type: 'object',\n          description: 'Custom fields to be added eg. { \"key1\": \"value1\", \"key2\": \"value2\" }',\n          additionalProperties: true\n        }\n      },\n      required: [        'id',\n        'current',\n        'initial',\n        'type',\n        'updates'\n      ]\n    },\n    product_list_item_state: {\n      type: 'object',\n      properties: {\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        billable_metric_id: {\n          type: 'string'\n        },\n        composite_product_ids: {\n          type: 'array',\n          items: {\n            type: 'string'\n          }\n        },\n        composite_tags: {\n          type: 'array',\n          items: {\n            type: 'string'\n          }\n        },\n        exclude_free_usage: {\n          type: 'boolean'\n        },\n        is_refundable: {\n          type: 'boolean',\n          description: 'This field\\'s availability is dependent on your client\\'s configuration.'\n        },\n        netsuite_internal_item_id: {\n          type: 'string',\n          description: 'This field\\'s availability is dependent on your client\\'s configuration.'\n        },\n        netsuite_overage_item_id: {\n          type: 'string',\n          description: 'This field\\'s availability is dependent on your client\\'s configuration.'\n        },\n        presentation_group_key: {\n          type: 'array',\n          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.',\n          items: {\n            type: 'string'\n          }\n        },\n        pricing_group_key: {\n          type: 'array',\n          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.',\n          items: {\n            type: 'string'\n          }\n        },\n        quantity_conversion: {\n          $ref: '#/$defs/quantity_conversion'\n        },\n        quantity_rounding: {\n          $ref: '#/$defs/quantity_rounding'\n        },\n        starting_at: {\n          type: 'string',\n          format: 'date-time'\n        },\n        tags: {\n          type: 'array',\n          items: {\n            type: 'string'\n          }\n        }\n      },\n      required: [        'created_at',\n        'created_by',\n        'name'\n      ]\n    },\n    quantity_conversion: {\n      type: 'object',\n      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\".',\n      properties: {\n        conversion_factor: {\n          type: 'number',\n          description: 'The factor to multiply or divide the quantity by.'\n        },\n        operation: {\n          type: 'string',\n          description: 'The operation to perform on the quantity',\n          enum: [            'MULTIPLY',\n            'DIVIDE'\n          ]\n        },\n        name: {\n          type: 'string',\n          description: 'Optional name for this conversion.'\n        }\n      },\n      required: [        'conversion_factor',\n        'operation'\n      ]\n    },\n    quantity_rounding: {\n      type: 'object',\n      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.',\n      properties: {\n        decimal_places: {\n          type: 'number'\n        },\n        rounding_method: {\n          type: 'string',\n          enum: [            'ROUND_UP',\n            'ROUND_DOWN',\n            'ROUND_HALF_UP'\n          ]\n        }\n      },\n      required: [        'decimal_places',\n        'rounding_method'\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.',
-      },
-      archive_filter: {
-        type: 'string',
-        description: 'Filter options for the product list. If not provided, defaults to not archived.',
-        enum: ['ARCHIVED', 'NOT_ARCHIVED', 'ALL'],
-      },
-      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.products.list(body).asResponse();
-  try {
-    return asTextContentResult(await maybeFilter(jq_filter, await response.json()));
-  } catch (error) {
-    if (error instanceof Metronome.APIError || isJqError(error)) {
-      return asErrorResult(error.message);
-    }
-    throw error;
-  }
-};
-
-export default { metadata, tool, handler };