@metronome/mcp 0.3.0 → 2.0.0

package/src/tools/v1/customers/preview-events-v1-customers.ts

@@ -17,7 +17,7 @@ export const metadata: Metadata = {
 export const tool: Tool = {
   name: 'preview_events_v1_customers',
   description:
-    "Preview how a set of events will affect a customer's invoice. Generates a draft invoice for a customer using their current contract configuration and the provided events. This is useful for testing how new events will affect the customer's invoice before they are actually processed.",
+    "Preview how a set of events will affect a customer's invoices. Generates draft invoices for a customer using their current contract configuration and the provided events.  This is useful for testing how new events will affect the customer's invoices before they are actually processed.\n",
   inputSchema: {
     type: 'object',
     properties: {
@@ -32,11 +32,6 @@ export const tool: Tool = {
             event_type: {
               type: 'string',
             },
-            customer_id: {
-              type: 'string',
-              description:
-                "This has no effect for preview events, but may be set for consistency with Event objects. They will be processed even if they do not match the customer's ID or ingest aliases.",
-            },
             properties: {
               type: 'object',
               additionalProperties: true,
@@ -48,7 +43,7 @@ export const tool: Tool = {
             transaction_id: {
               type: 'string',
               description:
-                'This has no effect for preview events, but may be set for consistency with Event objects. Duplicate transaction_ids are NOT filtered out, even within the same request.',
+                'Optional unique identifier for event deduplication. When provided, preview events are automatically deduplicated against historical events from the past 34 days.  Duplicate transaction IDs within the same request will return an error.\n',
             },
           },
           required: ['event_type'],

package/src/tools/v1/customers/retrieve-billing-configurations-v1-customers.ts

@@ -0,0 +1,50 @@
+// File generated from our OpenAPI spec by Stainless. See CONTRIBUTING.md for details.
+
+import { maybeFilter } from '@metronome/mcp/filtering';
+import { Metadata, asTextContentResult } from '@metronome/mcp/tools/types';
+
+import { Tool } from '@modelcontextprotocol/sdk/types.js';
+import Metronome from '@metronome/sdk';
+
+export const metadata: Metadata = {
+  resource: 'v1.customers',
+  operation: 'write',
+  tags: [],
+  httpMethod: 'post',
+  httpPath: '/v1/getCustomerBillingProviderConfigurations',
+  operationId: 'getCustomerBillingProviderConfigurations-v1',
+};
+
+export const tool: Tool = {
+  name: 'retrieve_billing_configurations_v1_customers',
+  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\nReturns all billing configurations previously set for the customer. Use during the contract provisioning process to fetch the `billing_provider_configuration_id` needed to set the contract billing configuration.\n\n\n# Response Schema\n```json\n{\n  $ref: '#/$defs/customer_retrieve_billing_configurations_response',\n  $defs: {\n    customer_retrieve_billing_configurations_response: {\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 this configuration; can be provided as the billing_provider_configuration_id when creating a contract.'\n              },\n              archived_at: {\n                type: 'string',\n                format: 'date-time'\n              },\n              billing_provider: {\n                type: 'string',\n                description: 'The billing provider set for this configuration.',\n                enum: [                  'aws_marketplace',\n                  'stripe',\n                  'netsuite',\n                  'custom',\n                  'azure_marketplace',\n                  'quickbooks_online',\n                  'workday',\n                  'gcp_marketplace'\n                ]\n              },\n              configuration: {\n                type: 'object',\n                description: 'Configuration for the billing provider. The structure of this object is specific to the billing provider.',\n                additionalProperties: true\n              },\n              customer_id: {\n                type: 'string'\n              },\n              delivery_method: {\n                type: 'string',\n                description: 'The method to use for delivering invoices to this customer.',\n                enum: [                  'direct_to_billing_provider',\n                  'aws_sqs',\n                  'tackle',\n                  'aws_sns'\n                ]\n              },\n              delivery_method_configuration: {\n                type: 'object',\n                description: 'Configuration for the delivery method. The structure of this object is specific to the delivery method.',\n                additionalProperties: true\n              },\n              delivery_method_id: {\n                type: 'string',\n                description: 'ID of the delivery method to use for this customer.'\n              }\n            },\n            required: [              'id',\n              'archived_at',\n              'billing_provider',\n              'configuration',\n              'customer_id',\n              'delivery_method',\n              'delivery_method_configuration',\n              'delivery_method_id'\n            ]\n          }\n        }\n      },\n      required: [        'data'\n      ]\n    }\n  }\n}\n```",
+  inputSchema: {
+    type: 'object',
+    properties: {
+      customer_id: {
+        type: 'string',
+      },
+      include_archived: {
+        type: 'boolean',
+      },
+      jq_filter: {
+        type: 'string',
+        title: 'jq Filter',
+        description:
+          'A jq filter to apply to the response to include certain fields. Consult the output schema in the tool description to see the fields that are available.\n\nFor example: to include only the `name` field in every object of a results array, you can provide ".results[].name".\n\nFor more information, see the [jq documentation](https://jqlang.org/manual/).',
+      },
+    },
+    required: ['customer_id'],
+  },
+  annotations: {},
+};
+
+export const handler = async (client: Metronome, args: Record<string, unknown> | undefined) => {
+  const { jq_filter, ...body } = args as any;
+  return asTextContentResult(
+    await maybeFilter(jq_filter, await client.v1.customers.retrieveBillingConfigurations(body)),
+  );
+};
+
+export default { metadata, tool, handler };

package/src/tools/v1/customers/retrieve-v1-customers.ts

@@ -18,7 +18,7 @@ export const metadata: Metadata = {
 export const tool: Tool = {
   name: 'retrieve_v1_customers',
   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 customer by Metronome ID.\n\n# Response Schema\n```json\n{\n  type: 'object',\n  properties: {\n    data: {\n      $ref: '#/$defs/customer_detail'\n    }\n  },\n  required: [    'data'\n  ],\n  $defs: {\n    customer_detail: {\n      type: 'object',\n      properties: {\n        id: {\n          type: 'string',\n          description: 'the Metronome ID of the customer'\n        },\n        created_at: {\n          type: 'string',\n          description: 'RFC 3339 timestamp indicating when the customer was created.',\n          format: 'date-time'\n        },\n        custom_fields: {\n          type: 'object',\n          additionalProperties: true\n        },\n        customer_config: {\n          type: 'object',\n          properties: {\n            salesforce_account_id: {\n              type: 'string',\n              description: 'The Salesforce account ID for the customer'\n            }\n          },\n          required: [            'salesforce_account_id'\n          ]\n        },\n        external_id: {\n          type: 'string',\n          description: '(deprecated, use ingest_aliases instead) the first ID (Metronome or ingest alias) that can be used in usage events'\n        },\n        ingest_aliases: {\n          type: 'array',\n          description: 'aliases for this customer that can be used instead of the Metronome customer ID in usage events',\n          items: {\n            type: 'string'\n          }\n        },\n        name: {\n          type: 'string'\n        },\n        archived_at: {\n          type: 'string',\n          description: 'RFC 3339 timestamp indicating when the customer was archived. Null if the customer is active.',\n          format: 'date-time'\n        },\n        current_billable_status: {\n          type: 'object',\n          description: 'This field\\'s availability is dependent on your client\\'s configuration.',\n          properties: {\n            value: {\n              type: 'string',\n              enum: [                'billable',\n                'unbillable'\n              ]\n            },\n            effective_at: {\n              type: 'string',\n              format: 'date-time'\n            }\n          },\n          required: [            'value'\n          ]\n        }\n      },\n      required: [        'id',\n        'created_at',\n        'custom_fields',\n        'customer_config',\n        'external_id',\n        'ingest_aliases',\n        '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\nGet detailed information for a specific customer by their Metronome ID. Returns customer profile data including name, creation date, ingest aliases, configuration settings, and custom fields. Use this endpoint to fetch complete customer details for billing operations or account management.\n\nNote: If searching for a customer billing configuration, use the `/getCustomerBillingConfigurations` endpoint.\n\n\n# Response Schema\n```json\n{\n  $ref: '#/$defs/customer_retrieve_response',\n  $defs: {\n    customer_retrieve_response: {\n      type: 'object',\n      properties: {\n        data: {\n          $ref: '#/$defs/customer_detail'\n        }\n      },\n      required: [        'data'\n      ]\n    },\n    customer_detail: {\n      type: 'object',\n      properties: {\n        id: {\n          type: 'string',\n          description: 'the Metronome ID of the customer'\n        },\n        created_at: {\n          type: 'string',\n          description: 'RFC 3339 timestamp indicating when the customer was created.',\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        customer_config: {\n          type: 'object',\n          properties: {\n            salesforce_account_id: {\n              type: 'string',\n              description: 'The Salesforce account ID for the customer'\n            }\n          },\n          required: [            'salesforce_account_id'\n          ]\n        },\n        external_id: {\n          type: 'string',\n          description: '(deprecated, use ingest_aliases instead) the first ID (Metronome or ingest alias) that can be used in usage events'\n        },\n        ingest_aliases: {\n          type: 'array',\n          description: 'aliases for this customer that can be used instead of the Metronome customer ID in usage events',\n          items: {\n            type: 'string'\n          }\n        },\n        name: {\n          type: 'string'\n        },\n        updated_at: {\n          type: 'string',\n          description: 'RFC 3339 timestamp indicating when the customer was last updated.',\n          format: 'date-time'\n        },\n        archived_at: {\n          type: 'string',\n          description: 'RFC 3339 timestamp indicating when the customer was archived. Null if the customer is active.',\n          format: 'date-time'\n        },\n        current_billable_status: {\n          type: 'object',\n          description: 'This field\\'s availability is dependent on your client\\'s configuration.',\n          properties: {\n            value: {\n              type: 'string',\n              enum: [                'billable',\n                'unbillable'\n              ]\n            },\n            effective_at: {\n              type: 'string',\n              format: 'date-time'\n            }\n          },\n          required: [            'value'\n          ]\n        }\n      },\n      required: [        'id',\n        'created_at',\n        'custom_fields',\n        'customer_config',\n        'external_id',\n        'ingest_aliases',\n        'name',\n        'updated_at'\n      ]\n    }\n  }\n}\n```",
   inputSchema: {
     type: 'object',
     properties: {

package/src/tools/v1/customers/set-billing-configurations-v1-customers.ts

@@ -0,0 +1,85 @@
+// File generated from our OpenAPI spec by Stainless. See CONTRIBUTING.md for details.
+
+import { Metadata, asTextContentResult } from '@metronome/mcp/tools/types';
+
+import { Tool } from '@modelcontextprotocol/sdk/types.js';
+import Metronome from '@metronome/sdk';
+
+export const metadata: Metadata = {
+  resource: 'v1.customers',
+  operation: 'write',
+  tags: [],
+  httpMethod: 'post',
+  httpPath: '/v1/setCustomerBillingProviderConfigurations',
+  operationId: 'setCustomerBillingProviderConfigurations-v1',
+};
+
+export const tool: Tool = {
+  name: 'set_billing_configurations_v1_customers',
+  description:
+    "Create a billing configuration for a customer. Once created, these configurations are available to associate to a contract and dictates which downstream system to collect payment in or send the invoice to. You can create multiple configurations per customer. The configuration formats are distinct for each downstream provider.\n\n### Use this endpoint to:\n- Add the initial configuration to an existing customer. Once created, the billing configuration can then be associated to the customer's contract.\n- Add a new configuration to an existing customer. This might be used as part of an upgrade or downgrade workflow where the customer was previously billed through system A (e.g. Stripe) but will now be billed through system B (e.g. AWS). Once created, the new configuration can then be associated to the customer's contract.\n- Multiple configurations can be added per destination. For example, you can create two Stripe billing configurations for a Metronome customer that each have a distinct `collection_method`.\n\n### Delivery method options:\n- `direct_to_billing_provider`: Use when Metronome should send invoices directly to the billing provider's API (e.g., Stripe, NetSuite). This is the most common method for automated billing workflows.\n- `tackle`: Use specifically for AWS Marketplace transactions that require Tackle's co-selling platform for partner attribution and commission tracking.\n- `aws_sqs`: Use when you want invoice data delivered to an AWS SQS queue for custom processing before sending to your billing system.\n- `aws_sns`: Use when you want invoice notifications published to an AWS SNS topic for event-driven billing workflows.\n\n### Key response fields: \nThe id for the customer billing configuration. This id can be used to associate the billing configuration to a contract.\n\n### Usage guidelines:\nMust use the `delivery_method_id` if you have multiple Stripe accounts connected to Metronome.\n",
+  inputSchema: {
+    type: 'object',
+    properties: {
+      data: {
+        type: 'array',
+        items: {
+          type: 'object',
+          properties: {
+            billing_provider: {
+              type: 'string',
+              description: 'The billing provider set for this configuration.',
+              enum: [
+                'aws_marketplace',
+                'stripe',
+                'netsuite',
+                'custom',
+                'azure_marketplace',
+                'quickbooks_online',
+                'workday',
+                'gcp_marketplace',
+              ],
+            },
+            customer_id: {
+              type: 'string',
+            },
+            configuration: {
+              type: 'object',
+              description:
+                'Configuration for the billing provider. The structure of this object is specific to the billing provider and delivery method combination. Defaults to an empty object, however, for most billing provider + delivery method combinations, it will not be a valid configuration.  For AWS marketplace configurations, the aws_is_subscription_product flag can be used to indicate a product with usage-based pricing.  More information can be found [here](https://docs.metronome.com/invoice-customers/solutions/marketplaces/invoice-aws/#provision-aws-marketplace-customers-in-metronome).',
+              additionalProperties: true,
+            },
+            delivery_method: {
+              type: 'string',
+              description:
+                'The method to use for delivering invoices to this customer. If not provided, the `delivery_method_id` must be provided.',
+              enum: ['direct_to_billing_provider', 'aws_sqs', 'tackle', 'aws_sns'],
+            },
+            delivery_method_id: {
+              type: 'string',
+              description:
+                'ID of the delivery method to use for this customer. If not provided, the `delivery_method` must be provided.',
+            },
+            tax_provider: {
+              type: 'string',
+              description:
+                'Specifies which tax provider Metronome should use for tax calculation when billing through Stripe. This is only supported for Stripe billing provider configurations with auto_charge_payment_intent or manual_charge_payment_intent collection methods.',
+              enum: ['anrok', 'avalara', 'stripe'],
+            },
+          },
+          required: ['billing_provider', 'customer_id'],
+        },
+      },
+    },
+    required: ['data'],
+  },
+  annotations: {},
+};
+
+export const handler = async (client: Metronome, args: Record<string, unknown> | undefined) => {
+  const body = args as any;
+  const response = await client.v1.customers.setBillingConfigurations(body).asResponse();
+  return asTextContentResult(await response.text());
+};
+
+export default { metadata, tool, handler };

package/src/tools/v1/customers/set-ingest-aliases-v1-customers.ts

@@ -17,7 +17,7 @@ export const metadata: Metadata = {
 export const tool: Tool = {
   name: 'set_ingest_aliases_v1_customers',
   description:
-    'Sets the ingest aliases for a customer. Ingest aliases can be used in the `customer_id` field when sending usage events to Metronome. This call is idempotent. It fully replaces the set of ingest aliases for the given customer.\n',
+    'Sets the ingest aliases for a customer. Use this endpoint to associate a Metronome customer with an internal ID for easier tracking between systems. Ingest aliases can be used in the `customer_id` field when sending usage events to Metronome. \n\n### Usage guidelines:\n- This call is idempotent and fully replaces the set of ingest aliases for the given customer.\n- Switching an ingest alias from one customer to another will associate all corresponding usage to the new customer.\n- Use multiple ingest aliases to model child organizations within a single Metronome customer.\n',
   inputSchema: {
     type: 'object',
     properties: {

package/src/tools/v1/customers/set-name-v1-customers.ts

@@ -18,7 +18,7 @@ export const metadata: Metadata = {
 export const tool: Tool = {
   name: 'set_name_v1_customers',
   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 the specified customer's name.\n\n\n# Response Schema\n```json\n{\n  type: 'object',\n  properties: {\n    data: {\n      $ref: '#/$defs/customer'\n    }\n  },\n  required: [    'data'\n  ],\n  $defs: {\n    customer: {\n      type: 'object',\n      properties: {\n        id: {\n          type: 'string',\n          description: 'the Metronome ID of the customer'\n        },\n        external_id: {\n          type: 'string',\n          description: '(deprecated, use ingest_aliases instead) the first ID (Metronome or ingest alias) that can be used in usage events'\n        },\n        ingest_aliases: {\n          type: 'array',\n          description: 'aliases for this customer that can be used instead of the Metronome customer ID in usage events',\n          items: {\n            type: 'string'\n          }\n        },\n        name: {\n          type: 'string'\n        },\n        custom_fields: {\n          type: 'object',\n          additionalProperties: true\n        }\n      },\n      required: [        'id',\n        'external_id',\n        'ingest_aliases',\n        '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\nUpdates the display name for a customer record. Use this to correct customer names, update business names after rebranding, or maintain accurate customer information for invoicing and reporting. Returns the updated customer object with the new name applied immediately across all billing documents and interfaces.\n\n\n# Response Schema\n```json\n{\n  $ref: '#/$defs/customer_set_name_response',\n  $defs: {\n    customer_set_name_response: {\n      type: 'object',\n      properties: {\n        data: {\n          $ref: '#/$defs/customer'\n        }\n      },\n      required: [        'data'\n      ]\n    },\n    customer: {\n      type: 'object',\n      properties: {\n        id: {\n          type: 'string',\n          description: 'the Metronome ID of the customer'\n        },\n        external_id: {\n          type: 'string',\n          description: '(deprecated, use ingest_aliases instead) the first ID (Metronome or ingest alias) that can be used in usage events'\n        },\n        ingest_aliases: {\n          type: 'array',\n          description: 'aliases for this customer that can be used instead of the Metronome customer ID in usage events',\n          items: {\n            type: 'string'\n          }\n        },\n        name: {\n          type: 'string'\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        'external_id',\n        'ingest_aliases',\n        'name'\n      ]\n    }\n  }\n}\n```",
   inputSchema: {
     type: 'object',
     properties: {

package/src/tools/v1/customers/update-config-v1-customers.ts

@@ -16,7 +16,8 @@ export const metadata: Metadata = {
 
 export const tool: Tool = {
   name: 'update_config_v1_customers',
-  description: "Updates the specified customer's config.\n",
+  description:
+    'Update configuration settings for a specific customer, such as external system integrations (e.g., Salesforce account ID) and other customer-specific billing parameters. Use this endpoint to modify customer configurations without affecting core customer data like name or ingest aliases.\n',
   inputSchema: {
     type: 'object',
     properties: {

package/src/tools/v1/dashboards/get-embeddable-url-v1-dashboards.ts

@@ -18,7 +18,7 @@ export const metadata: Metadata = {
 export const tool: Tool = {
   name: 'get_embeddable_url_v1_dashboards',
   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 an embeddable dashboard url for a customer.  The dashboard can be embedded using an iframe in a website.  This will show information such as usage data and customer invoices.\n\n# Response Schema\n```json\n{\n  type: 'object',\n  properties: {\n    data: {\n      type: 'object',\n      properties: {\n        url: {\n          type: 'string'\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\nGenerate secure, embeddable dashboard URLs that allow you to seamlessly integrate Metronome's billing visualizations directly into your application. This endpoint creates authenticated iframe-ready URLs for customer-specific dashboards, providing a white-labeled billing experience without building custom UI.\n\n### Use this endpoint to:\n- Embed billing dashboards directly in your customer portal or admin interface\n- Provide self-service access to invoices, usage data, and credit balances\n- Build white-labeled billing experiences with minimal development effort\n\n### Key response fields:\n- A secure, time-limited URL that can be embedded in an iframe\n- The URL includes authentication tokens and configuration parameters\n- URLs are customer-specific and respect your security settings\n\n### Usage guidelines:\n- Dashboard types: Choose from `invoices`, `usage`, or `commits_and_credits`\n- Customization options:\n    - `dashboard_options`: Configure whether you want invoices to show zero usage line items\n    - `color_overrides`: Match your brand's color palette\n    - `bm_group_key_overrides`: Customize how dimensions are displayed (for the usage embeddable dashboard)\n- Iframe implementation: Embed the returned URL directly in an iframe element\n- Responsive design: Dashboards automatically adapt to container dimensions\n\n\n# Response Schema\n```json\n{\n  $ref: '#/$defs/dashboard_get_embeddable_url_response',\n  $defs: {\n    dashboard_get_embeddable_url_response: {\n      type: 'object',\n      properties: {\n        data: {\n          type: 'object',\n          properties: {\n            url: {\n              type: 'string'\n            }\n          }\n        }\n      },\n      required: [        'data'\n      ]\n    }\n  }\n}\n```",
   inputSchema: {
     type: 'object',
     properties: {

package/src/tools/v1/invoices/regenerate-v1-invoices.ts

@@ -18,7 +18,7 @@ export const metadata: Metadata = {
 export const tool: Tool = {
   name: 'regenerate_v1_invoices',
   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\nRegenerate a voided contract invoice\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: 'The new invoice id'\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\nThis endpoint regenerates a voided invoice and recalculates the invoice based on up-to-date rates, available balances, and other fees regardless of the billing period.\n\n### Use this endpoint to:\nRecalculate an invoice with updated rate terms, available balance, and fees to correct billing disputes or discrepancies\n\n### Key response fields:\nThe regenerated invoice id, which is distinct from the previously voided invoice.\n\n### Usage guidelines:\nIf an invoice is attached to a contract with a billing provider on it, the regenerated invoice will be distributed based on the configuration.\n\n\n# Response Schema\n```json\n{\n  $ref: '#/$defs/invoice_regenerate_response',\n  $defs: {\n    invoice_regenerate_response: {\n      type: 'object',\n      properties: {\n        data: {\n          type: 'object',\n          properties: {\n            id: {\n              type: 'string',\n              description: 'The new invoice id'\n            }\n          },\n          required: [            'id'\n          ]\n        }\n      }\n    }\n  }\n}\n```",
   inputSchema: {
     type: 'object',
     properties: {

package/src/tools/v1/invoices/void-v1-invoices.ts

@@ -18,7 +18,7 @@ export const metadata: Metadata = {
 export const tool: Tool = {
   name: 'void_v1_invoices',
   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\nVoid an invoice\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      },\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 cancels an invoice by setting its status to voided, preventing collection and removing it from customer billing. Use this to correct billing errors, cancel incorrect charges, or handle disputed invoices that should not be collected. Returns the voided invoice ID with the status change applied immediately to stop any payment processing.\n\n\n# Response Schema\n```json\n{\n  $ref: '#/$defs/invoice_void_response',\n  $defs: {\n    invoice_void_response: {\n      type: 'object',\n      properties: {\n        data: {\n          type: 'object',\n          properties: {\n            id: {\n              type: 'string'\n            }\n          },\n          required: [            'id'\n          ]\n        }\n      }\n    }\n  }\n}\n```",
   inputSchema: {
     type: 'object',
     properties: {

package/src/tools/v1/payments/attempt-v1-payments.ts

@@ -0,0 +1,48 @@
+// File generated from our OpenAPI spec by Stainless. See CONTRIBUTING.md for details.
+
+import { maybeFilter } from '@metronome/mcp/filtering';
+import { Metadata, asTextContentResult } from '@metronome/mcp/tools/types';
+
+import { Tool } from '@modelcontextprotocol/sdk/types.js';
+import Metronome from '@metronome/sdk';
+
+export const metadata: Metadata = {
+  resource: 'v1.payments',
+  operation: 'write',
+  tags: [],
+  httpMethod: 'post',
+  httpPath: '/v1/payments/attempt',
+  operationId: 'attemptPayment-v1',
+};
+
+export const tool: Tool = {
+  name: 'attempt_v1_payments',
+  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\nTrigger a new attempt by canceling any existing attempts for this invoice and creating a new Payment. This will trigger another attempt to charge the Customer's configured Payment Gateway. \nPayment can only be attempted if all of the following are true:\n  - The Metronome Invoice is finalized\n  - PLG Invoicing is configured for the Customer\n  - You cannot attempt payments for invoices that have already been `paid` or `voided`.\n\nAttempting to payment on an ineligible Invoice or Customer will result in a `400` response.\n\n\n# Response Schema\n```json\n{\n  $ref: '#/$defs/payment_attempt_response',\n  $defs: {\n    payment_attempt_response: {\n      type: 'object',\n      properties: {\n        data: {\n          $ref: '#/$defs/payment'\n        }\n      },\n      required: [        'data'\n      ]\n    },\n    payment: {\n      type: 'object',\n      properties: {\n        id: {\n          type: 'string'\n        },\n        amount: {\n          type: 'number'\n        },\n        amount_paid: {\n          type: 'number'\n        },\n        contract_id: {\n          type: 'string'\n        },\n        created_at: {\n          type: 'string',\n          format: 'date-time'\n        },\n        customer_id: {\n          type: 'string'\n        },\n        error_message: {\n          type: 'string'\n        },\n        fiat_credit_type: {\n          $ref: '#/$defs/credit_type_data'\n        },\n        invoice_id: {\n          type: 'string'\n        },\n        payment_gateway: {\n          type: 'object',\n          properties: {\n            stripe: {\n              type: 'object',\n              properties: {\n                payment_intent_id: {\n                  type: 'string'\n                },\n                error: {\n                  type: 'object',\n                  properties: {\n                    code: {\n                      type: 'string'\n                    },\n                    decline_code: {\n                      type: 'string'\n                    },\n                    type: {\n                      type: 'string'\n                    }\n                  }\n                }\n              },\n              required: [                'payment_intent_id'\n              ]\n            },\n            type: {\n              type: 'string',\n              enum: [                'stripe'\n              ]\n            }\n          },\n          required: [            'stripe',\n            'type'\n          ]\n        },\n        status: {\n          $ref: '#/$defs/payment_status'\n        },\n        updated_at: {\n          type: 'string',\n          format: 'date-time'\n        }\n      },\n      required: [        'id'\n      ]\n    },\n    credit_type_data: {\n      type: 'object',\n      properties: {\n        id: {\n          type: 'string'\n        },\n        name: {\n          type: 'string'\n        }\n      },\n      required: [        'id',\n        'name'\n      ]\n    },\n    payment_status: {\n      type: 'string',\n      enum: [        'pending',\n        'requires_intervention',\n        'paid',\n        'canceled'\n      ]\n    }\n  }\n}\n```",
+  inputSchema: {
+    type: 'object',
+    properties: {
+      customer_id: {
+        type: 'string',
+      },
+      invoice_id: {
+        type: 'string',
+      },
+      jq_filter: {
+        type: 'string',
+        title: 'jq Filter',
+        description:
+          'A jq filter to apply to the response to include certain fields. Consult the output schema in the tool description to see the fields that are available.\n\nFor example: to include only the `name` field in every object of a results array, you can provide ".results[].name".\n\nFor more information, see the [jq documentation](https://jqlang.org/manual/).',
+      },
+    },
+    required: ['customer_id', 'invoice_id'],
+  },
+  annotations: {},
+};
+
+export const handler = async (client: Metronome, args: Record<string, unknown> | undefined) => {
+  const { jq_filter, ...body } = args as any;
+  return asTextContentResult(await maybeFilter(jq_filter, await client.v1.payments.attempt(body)));
+};
+
+export default { metadata, tool, handler };

package/src/tools/v1/payments/cancel-v1-payments.ts

@@ -0,0 +1,48 @@
+// File generated from our OpenAPI spec by Stainless. See CONTRIBUTING.md for details.
+
+import { maybeFilter } from '@metronome/mcp/filtering';
+import { Metadata, asTextContentResult } from '@metronome/mcp/tools/types';
+
+import { Tool } from '@modelcontextprotocol/sdk/types.js';
+import Metronome from '@metronome/sdk';
+
+export const metadata: Metadata = {
+  resource: 'v1.payments',
+  operation: 'write',
+  tags: [],
+  httpMethod: 'post',
+  httpPath: '/v1/payments/cancel',
+  operationId: 'cancelPayment-v1',
+};
+
+export const tool: Tool = {
+  name: 'cancel_v1_payments',
+  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\nCancel an existing payment attempt for an invoice.\n\n\n# Response Schema\n```json\n{\n  $ref: '#/$defs/payment_cancel_response',\n  $defs: {\n    payment_cancel_response: {\n      type: 'object',\n      properties: {\n        data: {\n          $ref: '#/$defs/payment'\n        }\n      },\n      required: [        'data'\n      ]\n    },\n    payment: {\n      type: 'object',\n      properties: {\n        id: {\n          type: 'string'\n        },\n        amount: {\n          type: 'number'\n        },\n        amount_paid: {\n          type: 'number'\n        },\n        contract_id: {\n          type: 'string'\n        },\n        created_at: {\n          type: 'string',\n          format: 'date-time'\n        },\n        customer_id: {\n          type: 'string'\n        },\n        error_message: {\n          type: 'string'\n        },\n        fiat_credit_type: {\n          $ref: '#/$defs/credit_type_data'\n        },\n        invoice_id: {\n          type: 'string'\n        },\n        payment_gateway: {\n          type: 'object',\n          properties: {\n            stripe: {\n              type: 'object',\n              properties: {\n                payment_intent_id: {\n                  type: 'string'\n                },\n                error: {\n                  type: 'object',\n                  properties: {\n                    code: {\n                      type: 'string'\n                    },\n                    decline_code: {\n                      type: 'string'\n                    },\n                    type: {\n                      type: 'string'\n                    }\n                  }\n                }\n              },\n              required: [                'payment_intent_id'\n              ]\n            },\n            type: {\n              type: 'string',\n              enum: [                'stripe'\n              ]\n            }\n          },\n          required: [            'stripe',\n            'type'\n          ]\n        },\n        status: {\n          $ref: '#/$defs/payment_status'\n        },\n        updated_at: {\n          type: 'string',\n          format: 'date-time'\n        }\n      },\n      required: [        'id'\n      ]\n    },\n    credit_type_data: {\n      type: 'object',\n      properties: {\n        id: {\n          type: 'string'\n        },\n        name: {\n          type: 'string'\n        }\n      },\n      required: [        'id',\n        'name'\n      ]\n    },\n    payment_status: {\n      type: 'string',\n      enum: [        'pending',\n        'requires_intervention',\n        'paid',\n        'canceled'\n      ]\n    }\n  }\n}\n```",
+  inputSchema: {
+    type: 'object',
+    properties: {
+      customer_id: {
+        type: 'string',
+      },
+      invoice_id: {
+        type: 'string',
+      },
+      jq_filter: {
+        type: 'string',
+        title: 'jq Filter',
+        description:
+          'A jq filter to apply to the response to include certain fields. Consult the output schema in the tool description to see the fields that are available.\n\nFor example: to include only the `name` field in every object of a results array, you can provide ".results[].name".\n\nFor more information, see the [jq documentation](https://jqlang.org/manual/).',
+      },
+    },
+    required: ['customer_id', 'invoice_id'],
+  },
+  annotations: {},
+};
+
+export const handler = async (client: Metronome, args: Record<string, unknown> | undefined) => {
+  const { jq_filter, ...body } = args as any;
+  return asTextContentResult(await maybeFilter(jq_filter, await client.v1.payments.cancel(body)));
+};
+
+export default { metadata, tool, handler };

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

@@ -0,0 +1,69 @@
+// File generated from our OpenAPI spec by Stainless. See CONTRIBUTING.md for details.
+
+import { maybeFilter } from '@metronome/mcp/filtering';
+import { Metadata, asTextContentResult } from '@metronome/mcp/tools/types';
+
+import { Tool } from '@modelcontextprotocol/sdk/types.js';
+import Metronome from '@metronome/sdk';
+
+export const metadata: Metadata = {
+  resource: 'v1.payments',
+  operation: 'write',
+  tags: [],
+  httpMethod: 'post',
+  httpPath: '/v1/payments/list',
+  operationId: 'listPayments-v1',
+};
+
+export const tool: Tool = {
+  name: 'list_v1_payments',
+  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\nFetch all payment attempts for the given invoice.\n\n\n# Response Schema\n```json\n{\n  type: 'object',\n  properties: {\n    data: {\n      type: 'array',\n      items: {\n        $ref: '#/$defs/payment'\n      }\n    },\n    next_page: {\n      type: 'string'\n    }\n  },\n  required: [    'data'\n  ],\n  $defs: {\n    payment: {\n      type: 'object',\n      properties: {\n        id: {\n          type: 'string'\n        },\n        amount: {\n          type: 'number'\n        },\n        amount_paid: {\n          type: 'number'\n        },\n        contract_id: {\n          type: 'string'\n        },\n        created_at: {\n          type: 'string',\n          format: 'date-time'\n        },\n        customer_id: {\n          type: 'string'\n        },\n        error_message: {\n          type: 'string'\n        },\n        fiat_credit_type: {\n          $ref: '#/$defs/credit_type_data'\n        },\n        invoice_id: {\n          type: 'string'\n        },\n        payment_gateway: {\n          type: 'object',\n          properties: {\n            stripe: {\n              type: 'object',\n              properties: {\n                payment_intent_id: {\n                  type: 'string'\n                },\n                error: {\n                  type: 'object',\n                  properties: {\n                    code: {\n                      type: 'string'\n                    },\n                    decline_code: {\n                      type: 'string'\n                    },\n                    type: {\n                      type: 'string'\n                    }\n                  }\n                }\n              },\n              required: [                'payment_intent_id'\n              ]\n            },\n            type: {\n              type: 'string',\n              enum: [                'stripe'\n              ]\n            }\n          },\n          required: [            'stripe',\n            'type'\n          ]\n        },\n        status: {\n          $ref: '#/$defs/payment_status'\n        },\n        updated_at: {\n          type: 'string',\n          format: 'date-time'\n        }\n      },\n      required: [        'id'\n      ]\n    },\n    credit_type_data: {\n      type: 'object',\n      properties: {\n        id: {\n          type: 'string'\n        },\n        name: {\n          type: 'string'\n        }\n      },\n      required: [        'id',\n        'name'\n      ]\n    },\n    payment_status: {\n      type: 'string',\n      enum: [        'pending',\n        'requires_intervention',\n        'paid',\n        'canceled'\n      ]\n    }\n  }\n}\n```",
+  inputSchema: {
+    type: 'object',
+    properties: {
+      customer_id: {
+        type: 'string',
+      },
+      invoice_id: {
+        type: 'string',
+      },
+      limit: {
+        type: 'integer',
+        description: 'The maximum number of payments to return. Defaults to 25.',
+      },
+      next_page: {
+        type: 'string',
+        description: 'The next page token from a previous response.',
+      },
+      statuses: {
+        type: 'array',
+        items: {
+          $ref: '#/$defs/payment_status',
+        },
+      },
+      jq_filter: {
+        type: 'string',
+        title: 'jq Filter',
+        description:
+          'A jq filter to apply to the response to include certain fields. Consult the output schema in the tool description to see the fields that are available.\n\nFor example: to include only the `name` field in every object of a results array, you can provide ".results[].name".\n\nFor more information, see the [jq documentation](https://jqlang.org/manual/).',
+      },
+    },
+    required: ['customer_id', 'invoice_id'],
+    $defs: {
+      payment_status: {
+        type: 'string',
+        enum: ['pending', 'requires_intervention', 'paid', 'canceled'],
+      },
+    },
+  },
+  annotations: {},
+};
+
+export const handler = async (client: Metronome, args: Record<string, unknown> | undefined) => {
+  const { jq_filter, ...body } = args as any;
+  const response = await client.v1.payments.list(body).asResponse();
+  return asTextContentResult(await maybeFilter(jq_filter, await response.json()));
+};
+
+export default { metadata, tool, handler };

package/src/tools/v1/plans/get-details-v1-plans.ts

@@ -18,7 +18,7 @@ export const metadata: Metadata = {
 export const tool: Tool = {
   name: 'get_details_v1_plans',
   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\nFetch high level details of a specific plan.\n\n# Response Schema\n```json\n{\n  type: 'object',\n  properties: {\n    data: {\n      $ref: '#/$defs/plan_detail'\n    }\n  },\n  required: [    'data'\n  ],\n  $defs: {\n    plan_detail: {\n      type: 'object',\n      properties: {\n        id: {\n          type: 'string'\n        },\n        custom_fields: {\n          type: 'object',\n          additionalProperties: true\n        },\n        name: {\n          type: 'string'\n        },\n        credit_grants: {\n          type: 'array',\n          items: {\n            type: 'object',\n            properties: {\n              amount_granted: {\n                type: 'number'\n              },\n              amount_granted_credit_type: {\n                $ref: '#/$defs/credit_type_data'\n              },\n              amount_paid: {\n                type: 'number'\n              },\n              amount_paid_credit_type: {\n                $ref: '#/$defs/credit_type_data'\n              },\n              effective_duration: {\n                type: 'number'\n              },\n              name: {\n                type: 'string'\n              },\n              priority: {\n                type: 'string'\n              },\n              send_invoice: {\n                type: 'boolean'\n              },\n              reason: {\n                type: 'string'\n              },\n              recurrence_duration: {\n                type: 'number'\n              },\n              recurrence_interval: {\n                type: 'number'\n              }\n            },\n            required: [              'amount_granted',\n              'amount_granted_credit_type',\n              'amount_paid',\n              'amount_paid_credit_type',\n              'effective_duration',\n              'name',\n              'priority',\n              'send_invoice'\n            ]\n          }\n        },\n        description: {\n          type: 'string'\n        },\n        minimums: {\n          type: 'array',\n          items: {\n            type: 'object',\n            properties: {\n              credit_type: {\n                $ref: '#/$defs/credit_type_data'\n              },\n              name: {\n                type: 'string'\n              },\n              start_period: {\n                type: 'number',\n                description: 'Used in price ramps.  Indicates how many billing periods pass before the charge applies.'\n              },\n              value: {\n                type: 'number'\n              }\n            },\n            required: [              'credit_type',\n              'name',\n              'start_period',\n              'value'\n            ]\n          }\n        },\n        overage_rates: {\n          type: 'array',\n          items: {\n            type: 'object',\n            properties: {\n              credit_type: {\n                $ref: '#/$defs/credit_type_data'\n              },\n              fiat_credit_type: {\n                $ref: '#/$defs/credit_type_data'\n              },\n              start_period: {\n                type: 'number',\n                description: 'Used in price ramps.  Indicates how many billing periods pass before the charge applies.'\n              },\n              to_fiat_conversion_factor: {\n                type: 'number'\n              }\n            },\n            required: [              'credit_type',\n              'fiat_credit_type',\n              'start_period',\n              'to_fiat_conversion_factor'\n            ]\n          }\n        }\n      },\n      required: [        'id',\n        'custom_fields',\n        'name'\n      ]\n    },\n    credit_type_data: {\n      type: 'object',\n      properties: {\n        id: {\n          type: 'string'\n        },\n        name: {\n          type: 'string'\n        }\n      },\n      required: [        'id',\n        'name'\n      ]\n    }\n  }\n}\n```",
+    "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\nFetch high level details of a specific plan.\n\n# Response Schema\n```json\n{\n  $ref: '#/$defs/plan_get_details_response',\n  $defs: {\n    plan_get_details_response: {\n      type: 'object',\n      properties: {\n        data: {\n          $ref: '#/$defs/plan_detail'\n        }\n      },\n      required: [        'data'\n      ]\n    },\n    plan_detail: {\n      type: 'object',\n      properties: {\n        id: {\n          type: 'string'\n        },\n        custom_fields: {\n          type: 'object',\n          description: 'Custom fields to be added eg. { \"key1\": \"value1\", \"key2\": \"value2\" }',\n          additionalProperties: true\n        },\n        name: {\n          type: 'string'\n        },\n        credit_grants: {\n          type: 'array',\n          items: {\n            type: 'object',\n            properties: {\n              amount_granted: {\n                type: 'number'\n              },\n              amount_granted_credit_type: {\n                $ref: '#/$defs/credit_type_data'\n              },\n              amount_paid: {\n                type: 'number'\n              },\n              amount_paid_credit_type: {\n                $ref: '#/$defs/credit_type_data'\n              },\n              effective_duration: {\n                type: 'number'\n              },\n              name: {\n                type: 'string'\n              },\n              priority: {\n                type: 'string'\n              },\n              send_invoice: {\n                type: 'boolean'\n              },\n              reason: {\n                type: 'string'\n              },\n              recurrence_duration: {\n                type: 'number'\n              },\n              recurrence_interval: {\n                type: 'number'\n              }\n            },\n            required: [              'amount_granted',\n              'amount_granted_credit_type',\n              'amount_paid',\n              'amount_paid_credit_type',\n              'effective_duration',\n              'name',\n              'priority',\n              'send_invoice'\n            ]\n          }\n        },\n        description: {\n          type: 'string'\n        },\n        minimums: {\n          type: 'array',\n          items: {\n            type: 'object',\n            properties: {\n              credit_type: {\n                $ref: '#/$defs/credit_type_data'\n              },\n              name: {\n                type: 'string'\n              },\n              start_period: {\n                type: 'number',\n                description: 'Used in price ramps.  Indicates how many billing periods pass before the charge applies.'\n              },\n              value: {\n                type: 'number'\n              }\n            },\n            required: [              'credit_type',\n              'name',\n              'start_period',\n              'value'\n            ]\n          }\n        },\n        overage_rates: {\n          type: 'array',\n          items: {\n            type: 'object',\n            properties: {\n              credit_type: {\n                $ref: '#/$defs/credit_type_data'\n              },\n              fiat_credit_type: {\n                $ref: '#/$defs/credit_type_data'\n              },\n              start_period: {\n                type: 'number',\n                description: 'Used in price ramps.  Indicates how many billing periods pass before the charge applies.'\n              },\n              to_fiat_conversion_factor: {\n                type: 'number'\n              }\n            },\n            required: [              'credit_type',\n              'fiat_credit_type',\n              'start_period',\n              'to_fiat_conversion_factor'\n            ]\n          }\n        }\n      },\n      required: [        'id',\n        'custom_fields',\n        'name'\n      ]\n    },\n    credit_type_data: {\n      type: 'object',\n      properties: {\n        id: {\n          type: 'string'\n        },\n        name: {\n          type: 'string'\n        }\n      },\n      required: [        'id',\n        'name'\n      ]\n    }\n  }\n}\n```",
   inputSchema: {
     type: 'object',
     properties: {

package/src/tools/v1/plans/list-charges-v1-plans.ts

@@ -18,7 +18,7 @@ export const metadata: Metadata = {
 export const tool: Tool = {
   name: 'list_charges_v1_plans',
   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\nFetches a list of charges of a specific plan.\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          charge_type: {\n            type: 'string',\n            enum: [              'usage',\n              'fixed',\n              'composite',\n              'minimum',\n              'seat'\n            ]\n          },\n          credit_type: {\n            $ref: '#/$defs/credit_type_data'\n          },\n          custom_fields: {\n            type: 'object',\n            additionalProperties: true\n          },\n          name: {\n            type: 'string'\n          },\n          prices: {\n            type: 'array',\n            items: {\n              type: 'object',\n              properties: {\n                tier: {\n                  type: 'number',\n                  description: 'Used in pricing tiers.  Indicates at what metric value the price applies.'\n                },\n                value: {\n                  type: 'number'\n                },\n                collection_interval: {\n                  type: 'number'\n                },\n                collection_schedule: {\n                  type: 'string'\n                },\n                quantity: {\n                  type: 'number'\n                }\n              },\n              required: [                'tier',\n                'value'\n              ]\n            }\n          },\n          product_id: {\n            type: 'string'\n          },\n          product_name: {\n            type: 'string'\n          },\n          quantity: {\n            type: 'number'\n          },\n          start_period: {\n            type: 'number',\n            description: 'Used in price ramps.  Indicates how many billing periods pass before the charge applies.'\n          },\n          tier_reset_frequency: {\n            type: 'number',\n            description: 'Used in pricing tiers.  Indicates how often the tier resets. Default is 1 - the tier count resets every billing period.'\n          },\n          unit_conversion: {\n            type: 'object',\n            description: 'Specifies how quantities for usage based charges will be converted.',\n            properties: {\n              division_factor: {\n                type: 'number',\n                description: 'The conversion factor'\n              },\n              rounding_behavior: {\n                type: 'string',\n                description: 'Whether usage should be rounded down or up to the nearest whole number. If null, quantity will be rounded to 20 decimal places.',\n                enum: [                  'floor',\n                  'ceiling'\n                ]\n              }\n            },\n            required: [              'division_factor'\n            ]\n          }\n        },\n        required: [          'id',\n          'charge_type',\n          'credit_type',\n          'custom_fields',\n          'name',\n          'prices',\n          'product_id',\n          'product_name'\n        ]\n      }\n    },\n    next_page: {\n      type: 'string'\n    }\n  },\n  required: [    'data',\n    'next_page'\n  ],\n  $defs: {\n    credit_type_data: {\n      type: 'object',\n      properties: {\n        id: {\n          type: 'string'\n        },\n        name: {\n          type: 'string'\n        }\n      },\n      required: [        'id',\n        'name'\n      ]\n    }\n  }\n}\n```",
+    "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\nFetches a list of charges of a specific plan.\n\n# Response Schema\n```json\n{\n  type: 'object',\n  properties: {\n    data: {\n      type: 'array',\n      items: {\n        $ref: '#/$defs/plan_list_charges_response'\n      }\n    },\n    next_page: {\n      type: 'string'\n    }\n  },\n  required: [    'data',\n    'next_page'\n  ],\n  $defs: {\n    plan_list_charges_response: {\n      type: 'object',\n      properties: {\n        id: {\n          type: 'string'\n        },\n        charge_type: {\n          type: 'string',\n          enum: [            'usage',\n            'fixed',\n            'composite',\n            'minimum',\n            'seat'\n          ]\n        },\n        credit_type: {\n          $ref: '#/$defs/credit_type_data'\n        },\n        custom_fields: {\n          type: 'object',\n          description: 'Custom fields to be added eg. { \"key1\": \"value1\", \"key2\": \"value2\" }',\n          additionalProperties: true\n        },\n        name: {\n          type: 'string'\n        },\n        prices: {\n          type: 'array',\n          items: {\n            type: 'object',\n            properties: {\n              tier: {\n                type: 'number',\n                description: 'Used in pricing tiers.  Indicates at what metric value the price applies.'\n              },\n              value: {\n                type: 'number'\n              },\n              collection_interval: {\n                type: 'number'\n              },\n              collection_schedule: {\n                type: 'string'\n              },\n              quantity: {\n                type: 'number'\n              }\n            },\n            required: [              'tier',\n              'value'\n            ]\n          }\n        },\n        product_id: {\n          type: 'string'\n        },\n        product_name: {\n          type: 'string'\n        },\n        quantity: {\n          type: 'number'\n        },\n        start_period: {\n          type: 'number',\n          description: 'Used in price ramps.  Indicates how many billing periods pass before the charge applies.'\n        },\n        tier_reset_frequency: {\n          type: 'number',\n          description: 'Used in pricing tiers.  Indicates how often the tier resets. Default is 1 - the tier count resets every billing period.'\n        },\n        unit_conversion: {\n          type: 'object',\n          description: 'Specifies how quantities for usage based charges will be converted.',\n          properties: {\n            division_factor: {\n              type: 'number',\n              description: 'The conversion factor'\n            },\n            rounding_behavior: {\n              type: 'string',\n              description: 'Whether usage should be rounded down or up to the nearest whole number. If null, quantity will be rounded to 20 decimal places.',\n              enum: [                'floor',\n                'ceiling'\n              ]\n            }\n          },\n          required: [            'division_factor'\n          ]\n        }\n      },\n      required: [        'id',\n        'charge_type',\n        'credit_type',\n        'custom_fields',\n        'name',\n        'prices',\n        'product_id',\n        'product_name'\n      ]\n    },\n    credit_type_data: {\n      type: 'object',\n      properties: {\n        id: {\n          type: 'string'\n        },\n        name: {\n          type: 'string'\n        }\n      },\n      required: [        'id',\n        'name'\n      ]\n    }\n  }\n}\n```",
   inputSchema: {
     type: 'object',
     properties: {

package/src/tools/v1/plans/list-customers-v1-plans.ts

@@ -18,7 +18,7 @@ export const metadata: Metadata = {
 export const tool: Tool = {
   name: 'list_customers_v1_plans',
   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\nFetches a list of customers on a specific plan (by default, only currently active plans are included)\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          customer_details: {\n            $ref: '#/$defs/customer_detail'\n          },\n          plan_details: {\n            type: 'object',\n            properties: {\n              id: {\n                type: 'string'\n              },\n              custom_fields: {\n                type: 'object',\n                additionalProperties: true\n              },\n              customer_plan_id: {\n                type: 'string'\n              },\n              name: {\n                type: 'string'\n              },\n              starting_on: {\n                type: 'string',\n                description: 'The start date of the plan',\n                format: 'date-time'\n              },\n              ending_before: {\n                type: 'string',\n                description: 'The end date of the plan',\n                format: 'date-time'\n              }\n            },\n            required: [              'id',\n              'custom_fields',\n              'customer_plan_id',\n              'name',\n              'starting_on'\n            ]\n          }\n        },\n        required: [          'customer_details',\n          'plan_details'\n        ]\n      }\n    },\n    next_page: {\n      type: 'string'\n    }\n  },\n  required: [    'data',\n    'next_page'\n  ],\n  $defs: {\n    customer_detail: {\n      type: 'object',\n      properties: {\n        id: {\n          type: 'string',\n          description: 'the Metronome ID of the customer'\n        },\n        created_at: {\n          type: 'string',\n          description: 'RFC 3339 timestamp indicating when the customer was created.',\n          format: 'date-time'\n        },\n        custom_fields: {\n          type: 'object',\n          additionalProperties: true\n        },\n        customer_config: {\n          type: 'object',\n          properties: {\n            salesforce_account_id: {\n              type: 'string',\n              description: 'The Salesforce account ID for the customer'\n            }\n          },\n          required: [            'salesforce_account_id'\n          ]\n        },\n        external_id: {\n          type: 'string',\n          description: '(deprecated, use ingest_aliases instead) the first ID (Metronome or ingest alias) that can be used in usage events'\n        },\n        ingest_aliases: {\n          type: 'array',\n          description: 'aliases for this customer that can be used instead of the Metronome customer ID in usage events',\n          items: {\n            type: 'string'\n          }\n        },\n        name: {\n          type: 'string'\n        },\n        archived_at: {\n          type: 'string',\n          description: 'RFC 3339 timestamp indicating when the customer was archived. Null if the customer is active.',\n          format: 'date-time'\n        },\n        current_billable_status: {\n          type: 'object',\n          description: 'This field\\'s availability is dependent on your client\\'s configuration.',\n          properties: {\n            value: {\n              type: 'string',\n              enum: [                'billable',\n                'unbillable'\n              ]\n            },\n            effective_at: {\n              type: 'string',\n              format: 'date-time'\n            }\n          },\n          required: [            'value'\n          ]\n        }\n      },\n      required: [        'id',\n        'created_at',\n        'custom_fields',\n        'customer_config',\n        'external_id',\n        'ingest_aliases',\n        '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\nFetches a list of customers on a specific plan (by default, only currently active plans are included)\n\n# Response Schema\n```json\n{\n  type: 'object',\n  properties: {\n    data: {\n      type: 'array',\n      items: {\n        $ref: '#/$defs/plan_list_customers_response'\n      }\n    },\n    next_page: {\n      type: 'string'\n    }\n  },\n  required: [    'data',\n    'next_page'\n  ],\n  $defs: {\n    plan_list_customers_response: {\n      type: 'object',\n      properties: {\n        customer_details: {\n          $ref: '#/$defs/customer_detail'\n        },\n        plan_details: {\n          type: 'object',\n          properties: {\n            id: {\n              type: 'string'\n            },\n            custom_fields: {\n              type: 'object',\n              description: 'Custom fields to be added eg. { \"key1\": \"value1\", \"key2\": \"value2\" }',\n              additionalProperties: true\n            },\n            customer_plan_id: {\n              type: 'string'\n            },\n            name: {\n              type: 'string'\n            },\n            starting_on: {\n              type: 'string',\n              description: 'The start date of the plan',\n              format: 'date-time'\n            },\n            ending_before: {\n              type: 'string',\n              description: 'The end date of the plan',\n              format: 'date-time'\n            }\n          },\n          required: [            'id',\n            'custom_fields',\n            'customer_plan_id',\n            'name',\n            'starting_on'\n          ]\n        }\n      },\n      required: [        'customer_details',\n        'plan_details'\n      ]\n    },\n    customer_detail: {\n      type: 'object',\n      properties: {\n        id: {\n          type: 'string',\n          description: 'the Metronome ID of the customer'\n        },\n        created_at: {\n          type: 'string',\n          description: 'RFC 3339 timestamp indicating when the customer was created.',\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        customer_config: {\n          type: 'object',\n          properties: {\n            salesforce_account_id: {\n              type: 'string',\n              description: 'The Salesforce account ID for the customer'\n            }\n          },\n          required: [            'salesforce_account_id'\n          ]\n        },\n        external_id: {\n          type: 'string',\n          description: '(deprecated, use ingest_aliases instead) the first ID (Metronome or ingest alias) that can be used in usage events'\n        },\n        ingest_aliases: {\n          type: 'array',\n          description: 'aliases for this customer that can be used instead of the Metronome customer ID in usage events',\n          items: {\n            type: 'string'\n          }\n        },\n        name: {\n          type: 'string'\n        },\n        updated_at: {\n          type: 'string',\n          description: 'RFC 3339 timestamp indicating when the customer was last updated.',\n          format: 'date-time'\n        },\n        archived_at: {\n          type: 'string',\n          description: 'RFC 3339 timestamp indicating when the customer was archived. Null if the customer is active.',\n          format: 'date-time'\n        },\n        current_billable_status: {\n          type: 'object',\n          description: 'This field\\'s availability is dependent on your client\\'s configuration.',\n          properties: {\n            value: {\n              type: 'string',\n              enum: [                'billable',\n                'unbillable'\n              ]\n            },\n            effective_at: {\n              type: 'string',\n              format: 'date-time'\n            }\n          },\n          required: [            'value'\n          ]\n        }\n      },\n      required: [        'id',\n        'created_at',\n        'custom_fields',\n        'customer_config',\n        'external_id',\n        'ingest_aliases',\n        'name',\n        'updated_at'\n      ]\n    }\n  }\n}\n```",
   inputSchema: {
     type: 'object',
     properties: {

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

@@ -18,7 +18,7 @@ export const metadata: Metadata = {
 export const tool: Tool = {
   name: 'list_v1_plans',
   description:
-    "When using this tool, always use the `jq_filter` parameter to reduce the response size and improve performance.\n\nOnly omit if you're sure you don't need the data.\n\nList all available plans.\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          description: {\n            type: 'string'\n          },\n          name: {\n            type: 'string'\n          },\n          custom_fields: {\n            type: 'object',\n            additionalProperties: true\n          }\n        },\n        required: [          'id',\n          'description',\n          'name'\n        ]\n      }\n    },\n    next_page: {\n      type: 'string'\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\nList all available plans.\n\n# Response Schema\n```json\n{\n  type: 'object',\n  properties: {\n    data: {\n      type: 'array',\n      items: {\n        $ref: '#/$defs/plan_list_response'\n      }\n    },\n    next_page: {\n      type: 'string'\n    }\n  },\n  required: [    'data',\n    'next_page'\n  ],\n  $defs: {\n    plan_list_response: {\n      type: 'object',\n      properties: {\n        id: {\n          type: 'string'\n        },\n        description: {\n          type: 'string'\n        },\n        name: {\n          type: 'string'\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        'description',\n        'name'\n      ]\n    }\n  }\n}\n```",
   inputSchema: {
     type: 'object',
     properties: {

package/src/tools/v1/pricing-units/list-v1-pricing-units.ts

@@ -18,7 +18,7 @@ export const metadata: Metadata = {
 export const tool: Tool = {
   name: 'list_v1_pricing_units',
   description:
-    "When using this tool, always use the `jq_filter` parameter to reduce the response size and improve performance.\n\nOnly omit if you're sure you don't need the data.\n\nList all pricing units (known in the API by the legacy term \"credit types\").\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          is_currency: {\n            type: 'boolean'\n          },\n          name: {\n            type: 'string'\n          }\n        }\n      }\n    },\n    next_page: {\n      type: 'string'\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\nList all pricing units. All fiat currency types (for example, USD or GBP) will be included, as well as any custom pricing units that were configured. Custom pricing units can be used to charge for usage in a non-fiat pricing unit, for example AI credits.\n\nNote: The USD (cents) pricing unit is 2714e483-4ff1-48e4-9e25-ac732e8f24f2.\n\n\n# Response Schema\n```json\n{\n  type: 'object',\n  properties: {\n    data: {\n      type: 'array',\n      items: {\n        $ref: '#/$defs/pricing_unit_list_response'\n      }\n    },\n    next_page: {\n      type: 'string'\n    }\n  },\n  required: [    'data',\n    'next_page'\n  ],\n  $defs: {\n    pricing_unit_list_response: {\n      type: 'object',\n      properties: {\n        id: {\n          type: 'string'\n        },\n        is_currency: {\n          type: 'boolean'\n        },\n        name: {\n          type: 'string'\n        }\n      }\n    }\n  }\n}\n```",
   inputSchema: {
     type: 'object',
     properties: {

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

@@ -18,7 +18,7 @@ export const metadata: Metadata = {
 export const tool: Tool = {
   name: 'list_v1_services',
   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\nFetches a list of services used by Metronome and the associated IP addresses. IP addresses are not necessarily unique between services. In most cases, IP addresses will appear in the list at least 30 days before they are used for the first time.\n\n\n# Response Schema\n```json\n{\n  type: 'object',\n  properties: {\n    services: {\n      type: 'array',\n      items: {\n        type: 'object',\n        properties: {\n          ips: {\n            type: 'array',\n            items: {\n              type: 'string'\n            }\n          },\n          name: {\n            type: 'string'\n          },\n          usage: {\n            type: 'string',\n            enum: [              'makes_connections_from',\n              'accepts_connections_at'\n            ]\n          }\n        },\n        required: [          'ips',\n          'name',\n          'usage'\n        ]\n      }\n    }\n  },\n  required: [    'services'\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\nGets Metronome's service registry with associated IP addresses for security allowlisting and firewall configuration. Use this endpoint to maintain an up-to-date list of IPs that your systems should trust for Metronome communications. Returns service names and their current IP ranges, with new IPs typically appearing 30+ days before first use to ensure smooth allowlist updates.\n\n\n# Response Schema\n```json\n{\n  $ref: '#/$defs/service_list_response',\n  $defs: {\n    service_list_response: {\n      type: 'object',\n      properties: {\n        services: {\n          type: 'array',\n          items: {\n            type: 'object',\n            properties: {\n              ips: {\n                type: 'array',\n                items: {\n                  type: 'string'\n                }\n              },\n              name: {\n                type: 'string'\n              },\n              usage: {\n                type: 'string',\n                enum: [                  'makes_connections_from',\n                  'accepts_connections_at'\n                ]\n              }\n            },\n            required: [              'ips',\n              'name',\n              'usage'\n            ]\n          }\n        }\n      },\n      required: [        'services'\n      ]\n    }\n  }\n}\n```",
   inputSchema: {
     type: 'object',
     properties: {