@metronome/mcp 1.0.0 → 2.0.0

package/src/tools/v1/alerts/archive-v1-alerts.ts

@@ -18,17 +18,17 @@ export const metadata: Metadata = {
 export const tool: Tool = {
   name: 'archive_v1_alerts',
   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 an alert and remove it from active monitoring across all customers. Archived alerts stop evaluating immediately and can optionally release their uniqueness key for reuse in future alert configurations.\n\n### Use this endpoint to:\n- Decommission alerts that are no longer needed\n- Clean up test or deprecated alert configurations\n- Free up uniqueness keys for reuse with new alerts\n- Stop alert evaluations without losing historical configuration data\n- Disable outdated monitoring rules during pricing model transitions\n\n### Key response fields:\n- data: Object containing the archived alert's ID\n- Alert evaluation stops immediately for all affected customers\n- Historical alert data and configurations remain accessible for audit purposes\n\n### Usage guidelines:\n- Irreversible for evaluation: Archived alerts cannot be re-enabled; create a new alert to resume monitoring\n- Uniqueness key handling: Set `release_uniqueness_key` : `true` to reuse the key in future alerts\n- Immediate effect: Alert evaluation stops instantly across all customers\n- Historical preservation: Archive operation maintains alert history and configuration for compliance and auditing\n\n\n# Response Schema\n```json\n{\n  type: 'object',\n  properties: {\n    data: {\n      $ref: '#/$defs/id'\n    }\n  },\n  required: [    'data'\n  ],\n  $defs: {\n    id: {\n      type: 'object',\n      properties: {\n        id: {\n          type: 'string'\n        }\n      },\n      required: [        'id'\n      ]\n    }\n  }\n}\n```",
+    "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 threshold notification and remove it from active monitoring across all customers. Archived threshold notifications stop evaluating immediately and can optionally release their uniqueness key for reuse in future threshold notification configurations.\n\n### Use this endpoint to:\n- Decommission threshold notifications that are no longer needed\n- Clean up test or deprecated threshold notification configurations\n- Free up uniqueness keys for reuse with new threshold notifications\n- Stop threshold notification evaluations without losing historical configuration data\n- Disable outdated monitoring rules during pricing model transitions\n\n### Key response fields:\n- data: Object containing the archived threshold notification's ID\n\n### Usage guidelines:\n- Irreversible for evaluation: Archived threshold notifications cannot be re-enabled; create a new threshold notification to resume monitoring\n- Uniqueness key handling: Set `release_uniqueness_key` : `true` to reuse the key in future threshold notifications\n- Immediate effect: Threshold notification evaluation stops instantly across all customers\n- Historical preservation: Archive operation maintains threshold notification history and configuration for compliance and auditing\n\n\n# Response Schema\n```json\n{\n  $ref: '#/$defs/alert_archive_response',\n  $defs: {\n    alert_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',
-        description: 'The Metronome ID of the alert',
+        description: 'The Metronome ID of the threshold notification',
       },
       release_uniqueness_key: {
         type: 'boolean',
-        description: 'If true, resets the uniqueness key on this alert so it can be re-used',
+        description: 'If true, resets the uniqueness key on this threshold notification so it can be re-used',
       },
       jq_filter: {
         type: 'string',

package/src/tools/v1/alerts/create-v1-alerts.ts

@@ -18,13 +18,13 @@ export const metadata: Metadata = {
 export const tool: Tool = {
   name: 'create_v1_alerts',
   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 alert to monitor customer spending, balances, and billing metrics in real-time. Metronome's alert system provides industry-leading speed with immediate evaluation capabilities, enabling you to proactively manage customer accounts and prevent revenue leakage.\n\nThis endpoint creates configurable alerts that continuously monitor various billing thresholds including spend limits, credit balances, commitment utilization, and invoice totals. Alerts can be configured globally for all customers or targeted to specific customer accounts. Custom fields can be used on certain alert types to further target alerts to groups of customers.\n\n### Use this endpoint to:\n- Proactively monitor customer spending patterns to prevent unexpected overages or credit exhaustion\n- Automate notifications when customers approach commitment limits or credit thresholds\n- Enable real-time intervention for accounts at risk of churn or payment issues\n- Scale billing operations by automating threshold-based workflows and notifications\n\n### Key response fields: \nA successful response returns a CustomerAlert object containing:\n\n- The alert configuration with its unique ID and current status\n- The customer's evaluation status (ok, in_alarm, or evaluating)\n- Alert metadata including type, threshold values, and update timestamps\n\n### Usage guidelines:\n- Immediate evaluation: Set `evaluate_on_create` : `true` (default) for instant evaluation against existing customers\n- Uniqueness constraints: Each alert must have a unique `uniqueness_key` within your organization. Use `release_uniqueness_key` : `true` when archiving to reuse keys\n- Alert type requirements: Different alert types require specific fields (e.g., `billable_metric_id` for usage alerts, `credit_type_id` for credit-based alerts)\n- Webhook delivery: Alerts trigger webhook notifications for real-time integration with your systems. Configure webhook endpoints before creating alerts\n- Performance at scale: Metronome's event-driven architecture processes alert evaluations in real-time as usage events stream in, unlike competitors who rely on periodic polling or batch evaluation cycles\n\n\n# Response Schema\n```json\n{\n  type: 'object',\n  properties: {\n    data: {\n      $ref: '#/$defs/id'\n    }\n  },\n  required: [    'data'\n  ],\n  $defs: {\n    id: {\n      type: 'object',\n      properties: {\n        id: {\n          type: 'string'\n        }\n      },\n      required: [        'id'\n      ]\n    }\n  }\n}\n```",
+    "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 threshold notification to monitor customer spending, balances, and billing metrics in real-time. Metronome's notification system provides industry-leading speed with immediate evaluation capabilities, enabling you to proactively manage customer accounts and prevent revenue leakage.\n\nThis endpoint creates configurable threshold notifications that continuously monitor various billing thresholds including spend limits, credit balances, commitment utilization, and invoice totals. Threshold notifications can be configured globally for all customers or targeted to specific customer accounts.\n\n### Use this endpoint to:\n- Proactively monitor customer spending patterns to prevent unexpected overages or credit exhaustion\n- Automate notifications when customers approach commitment limits or credit thresholds\n- Enable real-time intervention for accounts at risk of churn or payment issues\n- Scale billing operations by automating threshold-based workflows and notifications\n\n### Key response fields: \nA successful response returns a CustomerAlert object containing:\n\n- The threshold notification configuration with its unique ID and current status\n- The customer's evaluation status (ok, in_alarm, or evaluating)\n- Threshold notification metadata including type, threshold values, and update timestamps\n\n### Usage guidelines:\n- Immediate evaluation: Set `evaluate_on_create` : `true` (default) for instant evaluation against existing customers\n- Uniqueness constraints: Each threshold notification must have a unique `uniqueness_key` within your organization. Use `release_uniqueness_key` : `true` when archiving to reuse keys\n- Notification type requirements: Different threshold notification types require specific fields (e.g., `billable_metric_id` for usage notifications, `credit_type_id` for credit-based threshold notifications)\n- Webhook delivery: Threshold notifications trigger webhook notifications for real-time integration with your systems. Configure webhook endpoints before creating threshold notifications\n- Performance at scale: Metronome's event-driven architecture processes threshold notification evaluations in real-time as usage events stream in, unlike competitors who rely on periodic polling or batch evaluation cycles\n\n\n# Response Schema\n```json\n{\n  $ref: '#/$defs/alert_create_response',\n  $defs: {\n    alert_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: {
       alert_type: {
         type: 'string',
-        description: 'Type of the alert',
+        description: 'Type of the threshold notification',
         enum: [
           'low_credit_balance_reached',
           'spend_threshold_reached',
@@ -44,22 +44,22 @@ export const tool: Tool = {
       },
       name: {
         type: 'string',
-        description: 'Name of the alert',
+        description: 'Name of the threshold notification',
       },
       threshold: {
         type: 'number',
         description:
-          'Threshold value of the alert policy.  Depending upon the alert type, this number may represent a financial amount, the days remaining, or a percentage reached.',
+          'Threshold value of the notification policy.  Depending upon the notification type, this number may represent a financial amount, the days remaining, or a percentage reached.',
       },
       billable_metric_id: {
         type: 'string',
         description:
-          'For alerts of type `usage_threshold_reached`, specifies which billable metric to track the usage for.',
+          'For threshold notifications of type `usage_threshold_reached`, specifies which billable metric to track the usage for.',
       },
       credit_grant_type_filters: {
         type: 'array',
         description:
-          'An array of strings, representing a way to filter the credit grant this alert applies to, by looking at the credit_grant_type field on the credit grant. This field is only defined for CreditPercentage and CreditBalance alerts',
+          'An array of strings, representing a way to filter the credit grant this threshold notification applies to, by looking at the credit_grant_type field on the credit grant. This field is only defined for CreditPercentage and CreditBalance notifications',
         items: {
           type: 'string',
         },
@@ -67,12 +67,12 @@ export const tool: Tool = {
       credit_type_id: {
         type: 'string',
         description:
-          "ID of the credit's currency, defaults to USD. If the specific alert type requires a pricing unit/currency, find the ID in the [Metronome app](https://app.metronome.com/offering/pricing-units).",
+          "ID of the credit's currency, defaults to USD. If the specific notification type requires a pricing unit/currency, find the ID in the [Metronome app](https://app.metronome.com/offering/pricing-units).",
       },
       custom_field_filters: {
         type: 'array',
         description:
-          'A list of custom field filters for alert types that support advanced filtering. Only present for contract invoices.',
+          'A list of custom field filters for threshold notification types that support advanced filtering. Only present for contract invoices.',
         items: {
           type: 'object',
           properties: {
@@ -93,17 +93,17 @@ export const tool: Tool = {
       customer_id: {
         type: 'string',
         description:
-          'If provided, will create this alert for this specific customer. To create an alert for all customers, do not specify a `customer_id`.',
+          'If provided, will create this threshold notification for this specific customer. To create a notification for all customers, do not specify a `customer_id`.',
       },
       evaluate_on_create: {
         type: 'boolean',
         description:
-          'If true, the alert will evaluate immediately on customers that already meet the alert threshold. If false, it will only evaluate on future customers that trigger the alert threshold. Defaults to true.',
+          'If true, the threshold notification will evaluate immediately on customers that already meet the notification threshold. If false, it will only evaluate on future customers that trigger the threshold. Defaults to true.',
       },
       group_values: {
         type: 'array',
         description:
-          'Only present for `spend_threshold_reached` alerts. Scope alert to a specific group key on individual line items.',
+          'Only present for `spend_threshold_reached` notifications. Scope notification to a specific group key on individual line items.',
         items: {
           type: 'object',
           properties: {
@@ -119,7 +119,8 @@ export const tool: Tool = {
       },
       invoice_types_filter: {
         type: 'array',
-        description: 'Only supported for invoice_total_reached alerts. A list of invoice types to evaluate.',
+        description:
+          'Only supported for invoice_total_reached threshold notifications. A list of invoice types to evaluate.',
         items: {
           type: 'string',
         },
@@ -127,7 +128,7 @@ export const tool: Tool = {
       plan_id: {
         type: 'string',
         description:
-          'If provided, will create this alert for this specific plan. To create an alert for all customers, do not specify a `plan_id`.',
+          'If provided, will create this threshold notification for this specific plan. To create a notification for all customers, do not specify a `plan_id`.',
       },
       uniqueness_key: {
         type: 'string',

package/src/tools/v1/audit-logs/list-v1-audit-logs.ts

@@ -18,7 +18,7 @@ export const metadata: Metadata = {
 export const tool: Tool = {
   name: 'list_v1_audit_logs',
   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 comprehensive audit trail of all operations performed in your Metronome account, whether initiated through the API, web interface, or automated processes. This endpoint provides detailed logs of who did what and when, enabling compliance reporting, security monitoring, and operational troubleshooting across all interaction channels.\n\n### Use this endpoint to:\n- Monitor all account activity for security and compliance purposes\n- Track configuration changes regardless of source (API, UI, or system)\n- Investigate issues by reviewing historical operations\n\n### Key response fields: \nAn array of AuditLog objects containing:\n- id: Unique identifier for the audit log entry\n- timestamp: When the action occurred (RFC 3339 format)\n- actor: Information about who performed the action\n- request: Details including request ID, IP address, and user agent\n- `resource_type`: The type of resource affected (e.g., customer, contract, invoice)\n- `resource_id`: The specific resource identifier\n- `action`: The operation performed\n- `next_page`: Cursor for continuous log retrieval\n\n### Usage guidelines:\n- Continuous retrieval: The next_page token enables uninterrupted log streaming—save it between requests to ensure no logs are missed\n- Empty responses: An empty data array means no new logs yet; continue polling with the same next_page token\n- Date filtering:\n    - `starting_on`: Earliest logs to return (inclusive)\n    - `ending_before`: Latest logs to return (exclusive)\n    - Cannot be used with `next_page`\n- Resource filtering: Must specify both `resource_type` and `resource_id` together\n- Sort order: Default is `date_asc`; use `date_desc` for newest first\n\n\n# Response Schema\n```json\n{\n  type: 'object',\n  properties: {\n    data: {\n      type: 'array',\n      items: {\n        type: 'object',\n        properties: {\n          id: {\n            type: 'string'\n          },\n          request: {\n            type: 'object',\n            properties: {\n              id: {\n                type: 'string'\n              },\n              ip: {\n                type: 'string'\n              },\n              user_agent: {\n                type: 'string'\n              }\n            },\n            required: [              'id'\n            ]\n          },\n          timestamp: {\n            type: 'string',\n            format: 'date-time'\n          },\n          action: {\n            type: 'string'\n          },\n          actor: {\n            type: 'object',\n            properties: {\n              id: {\n                type: 'string'\n              },\n              name: {\n                type: 'string'\n              },\n              email: {\n                type: 'string'\n              }\n            },\n            required: [              'id',\n              'name'\n            ]\n          },\n          description: {\n            type: 'string'\n          },\n          resource_id: {\n            type: 'string'\n          },\n          resource_type: {\n            type: 'string'\n          },\n          status: {\n            type: 'string',\n            enum: [              'success',\n              'failure',\n              'pending'\n            ]\n          }\n        },\n        required: [          'id',\n          'request',\n          'timestamp'\n        ]\n      }\n    },\n    next_page: {\n      type: 'string',\n      description: 'The next_page parameter is always returned to support ongoing log retrieval. It enables continuous querying, even when some requests return no new data. Save the next_page token from each response and use it for future requests to ensure no logs are missed. This setup is ideal for regular updates via automated processes, like cron jobs, to fetch logs continuously as they become available. When you receive an empty data array, it indicates a temporary absence of new logs, but subsequent requests might return new data.'\n    }\n  },\n  required: [    'data',\n    'next_page'\n  ]\n}\n```",
+    "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 comprehensive audit trail of all operations performed in your Metronome account, whether initiated through the API, web interface, or automated processes. This endpoint provides detailed logs of who did what and when, enabling compliance reporting, security monitoring, and operational troubleshooting across all interaction channels.\n\n### Use this endpoint to:\n- Monitor all account activity for security and compliance purposes\n- Track configuration changes regardless of source (API, UI, or system)\n- Investigate issues by reviewing historical operations\n\n### Key response fields: \nAn array of AuditLog objects containing:\n- id: Unique identifier for the audit log entry\n- timestamp: When the action occurred (RFC 3339 format)\n- actor: Information about who performed the action\n- request: Details including request ID, IP address, and user agent\n- `resource_type`: The type of resource affected (e.g., customer, contract, invoice)\n- `resource_id`: The specific resource identifier\n- `action`: The operation performed\n- `next_page`: Cursor for continuous log retrieval\n\n### Usage guidelines:\n- Continuous retrieval: The next_page token enables uninterrupted log streaming—save it between requests to ensure no logs are missed\n- Empty responses: An empty data array means no new logs yet; continue polling with the same next_page token\n- Date filtering:\n    - `starting_on`: Earliest logs to return (inclusive)\n    - `ending_before`: Latest logs to return (exclusive)\n    - Cannot be used with `next_page`\n- Resource filtering: Must specify both `resource_type` and `resource_id` together\n- Sort order: Default is `date_asc`; use `date_desc` for newest first\n\n\n# Response Schema\n```json\n{\n  type: 'object',\n  properties: {\n    data: {\n      type: 'array',\n      items: {\n        $ref: '#/$defs/audit_log_list_response'\n      }\n    },\n    next_page: {\n      type: 'string',\n      description: 'The next_page parameter is always returned to support ongoing log retrieval. It enables continuous querying, even when some requests return no new data. Save the next_page token from each response and use it for future requests to ensure no logs are missed. This setup is ideal for regular updates via automated processes, like cron jobs, to fetch logs continuously as they become available. When you receive an empty data array, it indicates a temporary absence of new logs, but subsequent requests might return new data.'\n    }\n  },\n  required: [    'data',\n    'next_page'\n  ],\n  $defs: {\n    audit_log_list_response: {\n      type: 'object',\n      properties: {\n        id: {\n          type: 'string'\n        },\n        request: {\n          type: 'object',\n          properties: {\n            id: {\n              type: 'string'\n            },\n            ip: {\n              type: 'string'\n            },\n            user_agent: {\n              type: 'string'\n            }\n          },\n          required: [            'id'\n          ]\n        },\n        timestamp: {\n          type: 'string',\n          format: 'date-time'\n        },\n        action: {\n          type: 'string'\n        },\n        actor: {\n          type: 'object',\n          properties: {\n            id: {\n              type: 'string'\n            },\n            name: {\n              type: 'string'\n            },\n            email: {\n              type: 'string'\n            }\n          },\n          required: [            'id',\n            'name'\n          ]\n        },\n        description: {\n          type: 'string'\n        },\n        resource_id: {\n          type: 'string'\n        },\n        resource_type: {\n          type: 'string'\n        },\n        status: {\n          type: 'string',\n          enum: [            'success',\n            'failure',\n            'pending'\n          ]\n        }\n      },\n      required: [        'id',\n        'request',\n        'timestamp'\n      ]\n    }\n  }\n}\n```",
   inputSchema: {
     type: 'object',
     properties: {

package/src/tools/v1/billable-metrics/archive-v1-billable-metrics.ts

@@ -18,7 +18,7 @@ export const metadata: Metadata = {
 export const tool: Tool = {
   name: 'archive_v1_billable_metrics',
   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\nUse this endpoint to retire billable metrics that are no longer used. After a billable metric is archived, that billable metric can no longer be used in any new Products to define how that product should be metered. If you archive a billable metric that is already associated with a Product, the Product will continue to function as usual, metering based on the definition of the archived billable metric. \n\nArchived billable metrics will be returned on the `getBillableMetric` and `listBillableMetrics` endpoints with a populated `archived_at` field.\n\n\n# Response Schema\n```json\n{\n  type: 'object',\n  properties: {\n    data: {\n      $ref: '#/$defs/id'\n    }\n  },\n  required: [    'data'\n  ],\n  $defs: {\n    id: {\n      type: 'object',\n      properties: {\n        id: {\n          type: 'string'\n        }\n      },\n      required: [        'id'\n      ]\n    }\n  }\n}\n```",
+    "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\nUse this endpoint to retire billable metrics that are no longer used. After a billable metric is archived, that billable metric can no longer be used in any new Products to define how that product should be metered. If you archive a billable metric that is already associated with a Product, the Product will continue to function as usual, metering based on the definition of the archived billable metric. \n\nArchived billable metrics will be returned on the `getBillableMetric` and `listBillableMetrics` endpoints with a populated `archived_at` field.\n\n\n# Response Schema\n```json\n{\n  $ref: '#/$defs/billable_metric_archive_response',\n  $defs: {\n    billable_metric_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: {

package/src/tools/v1/billable-metrics/create-v1-billable-metrics.ts

@@ -18,7 +18,7 @@ export const metadata: Metadata = {
 export const tool: Tool = {
   name: 'create_v1_billable_metrics',
   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 billable metrics programmatically with this endpoint—an essential step in configuring your pricing and packaging in Metronome.\n\nA billable metric is a customizable query that filters and aggregates events from your event stream. These metrics are continuously tracked as usage data enters Metronome through the ingestion pipeline. The ingestion process transforms raw usage data into actionable pricing metrics, enabling accurate metering and billing for your products.\n\n### Use this endpoint to: \n- Create individual or multiple billable metrics as part of a setup workflow.\n- Automate the entire pricing configuration process, from metric creation to customer contract setup.\n- Define metrics using either standard filtering/aggregation or a custom SQL query.\n\n### Key response fields: \n- The ID of the billable metric that was created\n- The created billable metric will be available to be used in Products, usage endpoints, and alerts. \n\n### Usage guidelines: \n- Metrics defined using standard filtering and aggregation are Streaming billable metrics, which have been optimized for ultra low latency and high throughput workflows. \n- Use SQL billable metrics if you require more flexible aggregation options.\n\n\n# Response Schema\n```json\n{\n  type: 'object',\n  properties: {\n    data: {\n      $ref: '#/$defs/id'\n    }\n  },\n  required: [    'data'\n  ],\n  $defs: {\n    id: {\n      type: 'object',\n      properties: {\n        id: {\n          type: 'string'\n        }\n      },\n      required: [        'id'\n      ]\n    }\n  }\n}\n```",
+    "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 billable metrics programmatically with this endpoint—an essential step in configuring your pricing and packaging in Metronome.\n\nA billable metric is a customizable query that filters and aggregates events from your event stream. These metrics are continuously tracked as usage data enters Metronome through the ingestion pipeline. The ingestion process transforms raw usage data into actionable pricing metrics, enabling accurate metering and billing for your products.\n\n### Use this endpoint to: \n- Create individual or multiple billable metrics as part of a setup workflow.\n- Automate the entire pricing configuration process, from metric creation to customer contract setup.\n- Define metrics using either standard filtering/aggregation or a custom SQL query.\n\n### Key response fields: \n- The ID of the billable metric that was created\n- The created billable metric will be available to be used in Products, usage endpoints, and alerts. \n\n### Usage guidelines: \n- Metrics defined using standard filtering and aggregation are Streaming billable metrics, which have been optimized for ultra low latency and high throughput workflows. \n- Use SQL billable metrics if you require more flexible aggregation options.\n\n\n# Response Schema\n```json\n{\n  $ref: '#/$defs/billable_metric_create_response',\n  $defs: {\n    billable_metric_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: {

package/src/tools/v1/billable-metrics/list-v1-billable-metrics.ts

@@ -18,7 +18,7 @@ export const metadata: Metadata = {
 export const tool: Tool = {
   name: 'list_v1_billable_metrics',
   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\nRetrieves all billable metrics with their complete configurations. Use this for programmatic discovery and management of billable metrics, such as associating metrics to products and auditing for orphaned or archived metrics. \nImportant: Archived metrics are excluded by default; use `include_archived`=`true` parameter to include them.\n\n\n# Response Schema\n```json\n{\n  type: 'object',\n  properties: {\n    data: {\n      type: 'array',\n      items: {\n        type: 'object',\n        properties: {\n          id: {\n            type: 'string',\n            description: 'ID of the billable metric'\n          },\n          name: {\n            type: 'string',\n            description: 'The display name of the billable metric.'\n          },\n          aggregation_key: {\n            type: 'string',\n            description: 'A key that specifies which property of the event is used to aggregate data. This key must be one of the property filter names and is not applicable when the aggregation type is \\'count\\'.'\n          },\n          aggregation_type: {\n            type: 'string',\n            description: 'Specifies the type of aggregation performed on matching events.',\n            enum: [              'COUNT',\n              'LATEST',\n              'MAX',\n              'SUM',\n              'UNIQUE'\n            ]\n          },\n          archived_at: {\n            type: 'string',\n            description: 'RFC 3339 timestamp indicating when the billable metric was archived. If not provided, the billable metric is not archived.',\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          event_type_filter: {\n            $ref: '#/$defs/event_type_filter'\n          },\n          group_keys: {\n            type: 'array',\n            description: 'Property names that are used to group usage costs on an invoice. Each entry represents a set of properties used to slice events into distinct buckets.',\n            items: {\n              type: 'array',\n              items: {\n                type: 'string'\n              }\n            }\n          },\n          property_filters: {\n            type: 'array',\n            description: 'A list of filters to match events to this billable metric. Each filter defines a rule on an event property. All rules must pass for the event to match the billable metric.',\n            items: {\n              $ref: '#/$defs/property_filter'\n            }\n          },\n          sql: {\n            type: 'string',\n            description: 'The SQL query associated with the billable metric'\n          }\n        },\n        required: [          'id',\n          'name'\n        ]\n      }\n    },\n    next_page: {\n      type: 'string'\n    }\n  },\n  required: [    'data',\n    'next_page'\n  ],\n  $defs: {\n    event_type_filter: {\n      type: 'object',\n      description: 'An optional filtering rule to match the \\'event_type\\' property of an event.',\n      properties: {\n        in_values: {\n          type: 'array',\n          description: 'A list of event types that are explicitly included in the billable metric. If specified, only events of these types will match the billable metric. Must be non-empty if present.',\n          items: {\n            type: 'string'\n          }\n        },\n        not_in_values: {\n          type: 'array',\n          description: 'A list of event types that are explicitly excluded from the billable metric. If specified, events of these types will not match the billable metric. Must be non-empty if present.',\n          items: {\n            type: 'string'\n          }\n        }\n      }\n    },\n    property_filter: {\n      type: 'object',\n      properties: {\n        name: {\n          type: 'string',\n          description: 'The name of the event property.'\n        },\n        exists: {\n          type: 'boolean',\n          description: 'Determines whether the property must exist in the event. If true, only events with this property will pass the filter. If false, only events without this property will pass the filter. If null or omitted, the existence of the property is optional.'\n        },\n        in_values: {\n          type: 'array',\n          description: 'Specifies the allowed values for the property to match an event. An event will pass the filter only if its property value is included in this list. If undefined, all property values will pass the filter. Must be non-empty if present.',\n          items: {\n            type: 'string'\n          }\n        },\n        not_in_values: {\n          type: 'array',\n          description: 'Specifies the values that prevent an event from matching the filter. An event will not pass the filter if its property value is included in this list. If null or empty, all property values will pass the filter. Must be non-empty if present.',\n          items: {\n            type: 'string'\n          }\n        }\n      },\n      required: [        'name'\n      ]\n    }\n  }\n}\n```",
+    "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\nRetrieves all billable metrics with their complete configurations. Use this for programmatic discovery and management of billable metrics, such as associating metrics to products and auditing for orphaned or archived metrics. \nImportant: Archived metrics are excluded by default; use `include_archived`=`true` parameter to include them.\n\n\n# Response Schema\n```json\n{\n  type: 'object',\n  properties: {\n    data: {\n      type: 'array',\n      items: {\n        $ref: '#/$defs/billable_metric_list_response'\n      }\n    },\n    next_page: {\n      type: 'string'\n    }\n  },\n  required: [    'data',\n    'next_page'\n  ],\n  $defs: {\n    billable_metric_list_response: {\n      type: 'object',\n      properties: {\n        id: {\n          type: 'string',\n          description: 'ID of the billable metric'\n        },\n        name: {\n          type: 'string',\n          description: 'The display name of the billable metric.'\n        },\n        aggregation_key: {\n          type: 'string',\n          description: 'A key that specifies which property of the event is used to aggregate data. This key must be one of the property filter names and is not applicable when the aggregation type is \\'count\\'.'\n        },\n        aggregation_type: {\n          type: 'string',\n          description: 'Specifies the type of aggregation performed on matching events.',\n          enum: [            'COUNT',\n            'LATEST',\n            'MAX',\n            'SUM',\n            'UNIQUE'\n          ]\n        },\n        archived_at: {\n          type: 'string',\n          description: 'RFC 3339 timestamp indicating when the billable metric was archived. If not provided, the billable metric is not archived.',\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        event_type_filter: {\n          $ref: '#/$defs/event_type_filter'\n        },\n        group_keys: {\n          type: 'array',\n          description: 'Property names that are used to group usage costs on an invoice. Each entry represents a set of properties used to slice events into distinct buckets.',\n          items: {\n            type: 'array',\n            items: {\n              type: 'string'\n            }\n          }\n        },\n        property_filters: {\n          type: 'array',\n          description: 'A list of filters to match events to this billable metric. Each filter defines a rule on an event property. All rules must pass for the event to match the billable metric.',\n          items: {\n            $ref: '#/$defs/property_filter'\n          }\n        },\n        sql: {\n          type: 'string',\n          description: 'The SQL query associated with the billable metric'\n        }\n      },\n      required: [        'id',\n        'name'\n      ]\n    },\n    event_type_filter: {\n      type: 'object',\n      description: 'An optional filtering rule to match the \\'event_type\\' property of an event.',\n      properties: {\n        in_values: {\n          type: 'array',\n          description: 'A list of event types that are explicitly included in the billable metric. If specified, only events of these types will match the billable metric. Must be non-empty if present.',\n          items: {\n            type: 'string'\n          }\n        },\n        not_in_values: {\n          type: 'array',\n          description: 'A list of event types that are explicitly excluded from the billable metric. If specified, events of these types will not match the billable metric. Must be non-empty if present.',\n          items: {\n            type: 'string'\n          }\n        }\n      }\n    },\n    property_filter: {\n      type: 'object',\n      properties: {\n        name: {\n          type: 'string',\n          description: 'The name of the event property.'\n        },\n        exists: {\n          type: 'boolean',\n          description: 'Determines whether the property must exist in the event. If true, only events with this property will pass the filter. If false, only events without this property will pass the filter. If null or omitted, the existence of the property is optional.'\n        },\n        in_values: {\n          type: 'array',\n          description: 'Specifies the allowed values for the property to match an event. An event will pass the filter only if its property value is included in this list. If undefined, all property values will pass the filter. Must be non-empty if present.',\n          items: {\n            type: 'string'\n          }\n        },\n        not_in_values: {\n          type: 'array',\n          description: 'Specifies the values that prevent an event from matching the filter. An event will not pass the filter if its property value is included in this list. If null or empty, all property values will pass the filter. Must be non-empty if present.',\n          items: {\n            type: 'string'\n          }\n        }\n      },\n      required: [        'name'\n      ]\n    }\n  }\n}\n```",
   inputSchema: {
     type: 'object',
     properties: {

package/src/tools/v1/billable-metrics/retrieve-v1-billable-metrics.ts

@@ -18,7 +18,7 @@ export const metadata: Metadata = {
 export const tool: Tool = {
   name: 'retrieve_v1_billable_metrics',
   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\nRetrieves the complete configuration for a specific billable metric by its ID. Use this to review billable metric setup before associating it with products. Returns the metric's `name`, `event_type_filter`, `property_filters`, `aggregation_type`, `aggregation_key`, `group_keys`, `custom fields`, and `SQL query` (if it's a SQL billable metric). \n\nImportant: \n- Archived billable metrics will include an `archived_at` timestamp; they no longer process new usage events but remain accessible for historical reference.\n\n\n# Response Schema\n```json\n{\n  type: 'object',\n  properties: {\n    data: {\n      type: 'object',\n      properties: {\n        id: {\n          type: 'string',\n          description: 'ID of the billable metric'\n        },\n        name: {\n          type: 'string',\n          description: 'The display name of the billable metric.'\n        },\n        aggregation_key: {\n          type: 'string',\n          description: 'A key that specifies which property of the event is used to aggregate data. This key must be one of the property filter names and is not applicable when the aggregation type is \\'count\\'.'\n        },\n        aggregation_type: {\n          type: 'string',\n          description: 'Specifies the type of aggregation performed on matching events.',\n          enum: [            'COUNT',\n            'LATEST',\n            'MAX',\n            'SUM',\n            'UNIQUE'\n          ]\n        },\n        archived_at: {\n          type: 'string',\n          description: 'RFC 3339 timestamp indicating when the billable metric was archived. If not provided, the billable metric is not archived.',\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        event_type_filter: {\n          $ref: '#/$defs/event_type_filter'\n        },\n        group_keys: {\n          type: 'array',\n          description: 'Property names that are used to group usage costs on an invoice. Each entry represents a set of properties used to slice events into distinct buckets.',\n          items: {\n            type: 'array',\n            items: {\n              type: 'string'\n            }\n          }\n        },\n        property_filters: {\n          type: 'array',\n          description: 'A list of filters to match events to this billable metric. Each filter defines a rule on an event property. All rules must pass for the event to match the billable metric.',\n          items: {\n            $ref: '#/$defs/property_filter'\n          }\n        },\n        sql: {\n          type: 'string',\n          description: 'The SQL query associated with the billable metric'\n        }\n      },\n      required: [        'id',\n        'name'\n      ]\n    }\n  },\n  required: [    'data'\n  ],\n  $defs: {\n    event_type_filter: {\n      type: 'object',\n      description: 'An optional filtering rule to match the \\'event_type\\' property of an event.',\n      properties: {\n        in_values: {\n          type: 'array',\n          description: 'A list of event types that are explicitly included in the billable metric. If specified, only events of these types will match the billable metric. Must be non-empty if present.',\n          items: {\n            type: 'string'\n          }\n        },\n        not_in_values: {\n          type: 'array',\n          description: 'A list of event types that are explicitly excluded from the billable metric. If specified, events of these types will not match the billable metric. Must be non-empty if present.',\n          items: {\n            type: 'string'\n          }\n        }\n      }\n    },\n    property_filter: {\n      type: 'object',\n      properties: {\n        name: {\n          type: 'string',\n          description: 'The name of the event property.'\n        },\n        exists: {\n          type: 'boolean',\n          description: 'Determines whether the property must exist in the event. If true, only events with this property will pass the filter. If false, only events without this property will pass the filter. If null or omitted, the existence of the property is optional.'\n        },\n        in_values: {\n          type: 'array',\n          description: 'Specifies the allowed values for the property to match an event. An event will pass the filter only if its property value is included in this list. If undefined, all property values will pass the filter. Must be non-empty if present.',\n          items: {\n            type: 'string'\n          }\n        },\n        not_in_values: {\n          type: 'array',\n          description: 'Specifies the values that prevent an event from matching the filter. An event will not pass the filter if its property value is included in this list. If null or empty, all property values will pass the filter. Must be non-empty if present.',\n          items: {\n            type: 'string'\n          }\n        }\n      },\n      required: [        'name'\n      ]\n    }\n  }\n}\n```",
+    "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\nRetrieves the complete configuration for a specific billable metric by its ID. Use this to review billable metric setup before associating it with products. Returns the metric's `name`, `event_type_filter`, `property_filters`, `aggregation_type`, `aggregation_key`, `group_keys`, `custom fields`, and `SQL query` (if it's a SQL billable metric). \n\nImportant: \n- Archived billable metrics will include an `archived_at` timestamp; they no longer process new usage events but remain accessible for historical reference.\n\n\n# Response Schema\n```json\n{\n  $ref: '#/$defs/billable_metric_retrieve_response',\n  $defs: {\n    billable_metric_retrieve_response: {\n      type: 'object',\n      properties: {\n        data: {\n          type: 'object',\n          properties: {\n            id: {\n              type: 'string',\n              description: 'ID of the billable metric'\n            },\n            name: {\n              type: 'string',\n              description: 'The display name of the billable metric.'\n            },\n            aggregation_key: {\n              type: 'string',\n              description: 'A key that specifies which property of the event is used to aggregate data. This key must be one of the property filter names and is not applicable when the aggregation type is \\'count\\'.'\n            },\n            aggregation_type: {\n              type: 'string',\n              description: 'Specifies the type of aggregation performed on matching events.',\n              enum: [                'COUNT',\n                'LATEST',\n                'MAX',\n                'SUM',\n                'UNIQUE'\n              ]\n            },\n            archived_at: {\n              type: 'string',\n              description: 'RFC 3339 timestamp indicating when the billable metric was archived. If not provided, the billable metric is not archived.',\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            event_type_filter: {\n              $ref: '#/$defs/event_type_filter'\n            },\n            group_keys: {\n              type: 'array',\n              description: 'Property names that are used to group usage costs on an invoice. Each entry represents a set of properties used to slice events into distinct buckets.',\n              items: {\n                type: 'array',\n                items: {\n                  type: 'string'\n                }\n              }\n            },\n            property_filters: {\n              type: 'array',\n              description: 'A list of filters to match events to this billable metric. Each filter defines a rule on an event property. All rules must pass for the event to match the billable metric.',\n              items: {\n                $ref: '#/$defs/property_filter'\n              }\n            },\n            sql: {\n              type: 'string',\n              description: 'The SQL query associated with the billable metric'\n            }\n          },\n          required: [            'id',\n            'name'\n          ]\n        }\n      },\n      required: [        'data'\n      ]\n    },\n    event_type_filter: {\n      type: 'object',\n      description: 'An optional filtering rule to match the \\'event_type\\' property of an event.',\n      properties: {\n        in_values: {\n          type: 'array',\n          description: 'A list of event types that are explicitly included in the billable metric. If specified, only events of these types will match the billable metric. Must be non-empty if present.',\n          items: {\n            type: 'string'\n          }\n        },\n        not_in_values: {\n          type: 'array',\n          description: 'A list of event types that are explicitly excluded from the billable metric. If specified, events of these types will not match the billable metric. Must be non-empty if present.',\n          items: {\n            type: 'string'\n          }\n        }\n      }\n    },\n    property_filter: {\n      type: 'object',\n      properties: {\n        name: {\n          type: 'string',\n          description: 'The name of the event property.'\n        },\n        exists: {\n          type: 'boolean',\n          description: 'Determines whether the property must exist in the event. If true, only events with this property will pass the filter. If false, only events without this property will pass the filter. If null or omitted, the existence of the property is optional.'\n        },\n        in_values: {\n          type: 'array',\n          description: 'Specifies the allowed values for the property to match an event. An event will pass the filter only if its property value is included in this list. If undefined, all property values will pass the filter. Must be non-empty if present.',\n          items: {\n            type: 'string'\n          }\n        },\n        not_in_values: {\n          type: 'array',\n          description: 'Specifies the values that prevent an event from matching the filter. An event will not pass the filter if its property value is included in this list. If null or empty, all property values will pass the filter. Must be non-empty if present.',\n          items: {\n            type: 'string'\n          }\n        }\n      },\n      required: [        'name'\n      ]\n    }\n  }\n}\n```",
   inputSchema: {
     type: 'object',
     properties: {

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

@@ -261,7 +261,7 @@ export const tool: Tool = {
                   type: 'string',
                   description:
                     'Stripe tax is only supported for Stripe payment gateway. Select NONE if you do not wish Metronome to calculate tax on your behalf. Leaving this field blank will default to NONE.',
-                  enum: ['NONE', 'STRIPE', 'ANROK', 'PRECALCULATED'],
+                  enum: ['NONE', 'STRIPE', 'ANROK', 'AVALARA', 'PRECALCULATED'],
                 },
               },
               required: ['payment_gate_type'],

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

@@ -18,7 +18,7 @@ export const metadata: Metadata = {
 export const tool: Tool = {
   name: 'archive_v1_contracts',
   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 end and archive a contract along with all its terms. Any draft invoices will be canceled, and all upcoming scheduled invoices will be voided–also all finalized invoices can optionally be voided. Use this in the event a contract was incorrectly created and needed to be removed from a customer.\n\n#### Impact on commits and credits:\nWhen archiving a contract, all associated commits and credits are also archived. For prepaid commits with active segments, Metronome automatically generates expiration ledger entries to close out any remaining balances, ensuring accurate accounting of unused prepaid amounts. These ledger entries will appear in the commit's transaction history with type `PREPAID_COMMIT_EXPIRATION`.\n\n#### Archived contract visibility: \nArchived contracts remain accessible for historical reporting and audit purposes. They can be retrieved using the `ListContracts` endpoint by setting the `include_archived` parameter to `true` or in the Metronome UI when the \"Show archived\" option is enabled.\n\n\n# Response Schema\n```json\n{\n  type: 'object',\n  properties: {\n    data: {\n      $ref: '#/$defs/id'\n    }\n  },\n  required: [    'data'\n  ],\n  $defs: {\n    id: {\n      type: 'object',\n      properties: {\n        id: {\n          type: 'string'\n        }\n      },\n      required: [        'id'\n      ]\n    }\n  }\n}\n```",
+    "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 end and archive a contract along with all its terms. Any draft invoices will be canceled, and all upcoming scheduled invoices will be voided–also all finalized invoices can optionally be voided. Use this in the event a contract was incorrectly created and needed to be removed from a customer.\n\n#### Impact on commits and credits:\nWhen archiving a contract, all associated commits and credits are also archived. For prepaid commits with active segments, Metronome automatically generates expiration ledger entries to close out any remaining balances, ensuring accurate accounting of unused prepaid amounts. These ledger entries will appear in the commit's transaction history with type `PREPAID_COMMIT_EXPIRATION`.\n\n#### Archived contract visibility: \nArchived contracts remain accessible for historical reporting and audit purposes. They can be retrieved using the `ListContracts` endpoint by setting the `include_archived` parameter to `true` or in the Metronome UI when the \"Show archived\" option is enabled.\n\n\n# Response Schema\n```json\n{\n  $ref: '#/$defs/contract_archive_response',\n  $defs: {\n    contract_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: {

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

@@ -278,7 +278,7 @@ export const tool: Tool = {
                   type: 'string',
                   description:
                     'Stripe tax is only supported for Stripe payment gateway. Select NONE if you do not wish Metronome to calculate tax on your behalf. Leaving this field blank will default to NONE.',
-                  enum: ['NONE', 'STRIPE', 'ANROK', 'PRECALCULATED'],
+                  enum: ['NONE', 'STRIPE', 'ANROK', 'AVALARA', 'PRECALCULATED'],
                 },
               },
               required: ['payment_gate_type'],
@@ -548,8 +548,29 @@ export const tool: Tool = {
             },
             required: ['contract_id', 'customer_id'],
           },
+          parent_behavior: {
+            type: 'object',
+            properties: {
+              invoice_consolidation_type: {
+                type: 'string',
+                description:
+                  'Indicates the desired behavior of consolidated invoices generated by the parent in a customer hierarchy\n**CONCATENATE**: Statements on the invoices of child customers will be appended to the consolidated invoice\n**NONE**: Do not generate consolidated invoices',
+                enum: ['CONCATENATE', 'NONE'],
+              },
+            },
+          },
+          payer: {
+            type: 'string',
+            description: "Indicates whether the parent should pay for the child's invoice charges",
+            enum: ['SELF', 'PARENT'],
+          },
+          usage_statement_behavior: {
+            type: 'string',
+            description:
+              "Indicates the behavior of the child's invoice statements on the parent's invoices\n**CONSOLIDATE**: Child's invoice statements will be added to parent's consolidated invoices\n**SEPARATE**: Child's invoice statements will appear not appear on parent's consolidated invoices",
+            enum: ['CONSOLIDATE', 'SEPARATE'],
+          },
         },
-        required: ['parent'],
       },
       multiplier_override_prioritization: {
         type: 'string',
@@ -1644,7 +1665,7 @@ export const tool: Tool = {
             type: 'string',
             description:
               'Stripe tax is only supported for Stripe payment gateway. Select NONE if you do not wish Metronome to calculate tax on your behalf. Leaving this field blank will default to NONE.',
-            enum: ['NONE', 'STRIPE', 'ANROK', 'PRECALCULATED'],
+            enum: ['NONE', 'STRIPE', 'ANROK', 'AVALARA', 'PRECALCULATED'],
           },
         },
         required: ['payment_gate_type'],

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

@@ -18,7 +18,7 @@ export const metadata: Metadata = {
 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  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```",
+    "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: {

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

@@ -18,7 +18,7 @@ export const metadata: Metadata = {
 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  type: 'object',\n  properties: {\n    data: {\n      $ref: '#/$defs/id'\n    }\n  },\n  required: [    'data'\n  ],\n  $defs: {\n    id: {\n      type: 'object',\n      properties: {\n        id: {\n          type: 'string'\n        }\n      },\n      required: [        'id'\n      ]\n    }\n  }\n}\n```",
+    "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: {

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

@@ -18,7 +18,7 @@ export const metadata: Metadata = {
 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  type: 'object',\n  properties: {\n    data: {\n      $ref: '#/$defs/id'\n    }\n  },\n  required: [    'data'\n  ],\n  $defs: {\n    id: {\n      type: 'object',\n      properties: {\n        id: {\n          type: 'string'\n        }\n      },\n      required: [        'id'\n      ]\n    }\n  }\n}\n```",
+    "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: {

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

@@ -18,7 +18,7 @@ export const metadata: Metadata = {
 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        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    },\n    next_page: {\n      type: 'string'\n    }\n  },\n  required: [    'data',\n    'next_page'\n  ],\n  $defs: {\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```",
+    "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: {

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

@@ -18,7 +18,7 @@ export const metadata: Metadata = {
 export const tool: Tool = {
   name: 'retrieve_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\nRetrieve a product by its ID, including all metadata and historical changes.\n\n\n# Response Schema\n```json\n{\n  type: 'object',\n  properties: {\n    data: {\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  },\n  required: [    'data'\n  ],\n  $defs: {\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```",
+    "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\nRetrieve a product by its ID, including all metadata and historical changes.\n\n\n# Response Schema\n```json\n{\n  $ref: '#/$defs/product_retrieve_response',\n  $defs: {\n    product_retrieve_response: {\n      type: 'object',\n      properties: {\n        data: {\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      },\n      required: [        'data'\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: {

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

@@ -18,7 +18,7 @@ export const metadata: Metadata = {
 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  type: 'object',\n  properties: {\n    data: {\n      $ref: '#/$defs/id'\n    }\n  },\n  required: [    'data'\n  ],\n  $defs: {\n    id: {\n      type: 'object',\n      properties: {\n        id: {\n          type: 'string'\n        }\n      },\n      required: [        'id'\n      ]\n    }\n  }\n}\n```",
+    "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: {

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

@@ -18,7 +18,7 @@ export const metadata: Metadata = {
 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  type: 'object',\n  properties: {\n    data: {\n      $ref: '#/$defs/id'\n    }\n  },\n  required: [    'data'\n  ],\n  $defs: {\n    id: {\n      type: 'object',\n      properties: {\n        id: {\n          type: 'string'\n        }\n      },\n      required: [        'id'\n      ]\n    }\n  }\n}\n```",
+    "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: {

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

@@ -18,7 +18,7 @@ export const metadata: Metadata = {
 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  type: 'object',\n  properties: {\n    data: {\n      $ref: '#/$defs/id'\n    }\n  },\n  required: [    'data'\n  ],\n  $defs: {\n    id: {\n      type: 'object',\n      properties: {\n        id: {\n          type: 'string'\n        }\n      },\n      required: [        'id'\n      ]\n    }\n  }\n}\n```",
+    "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: {