@metronome/mcp 2.2.0 → 3.4.1

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

@@ -1,155 +0,0 @@
-// File generated from our OpenAPI spec by Stainless. See CONTRIBUTING.md for details.
-
-import { isJqError, maybeFilter } from '@metronome/mcp/filtering';
-import { Metadata, asErrorResult, asTextContentResult } from '@metronome/mcp/tools/types';
-
-import { Tool } from '@modelcontextprotocol/sdk/types.js';
-import Metronome from '@metronome/sdk';
-
-export const metadata: Metadata = {
-  resource: 'v1.customers.plans',
-  operation: 'write',
-  tags: [],
-  httpMethod: 'post',
-  httpPath: '/v1/customers/{customer_id}/plans/add',
-  operationId: 'addPlanToCustomer-v1',
-};
-
-export const tool: Tool = {
-  name: 'add_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\nAssociate an existing customer with a plan for a specified date range.  See the [price adjustments documentation](https://plans-docs.metronome.com/pricing/managing-plans/#price-adjustments) for details on the price adjustments. This is a Plans (deprecated) endpoint. New clients should implement using Contracts.\n\n\n# Response Schema\n```json\n{\n  $ref: '#/$defs/plan_add_response',\n  $defs: {\n    plan_add_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: {
-      customer_id: {
-        type: 'string',
-      },
-      plan_id: {
-        type: 'string',
-      },
-      starting_on: {
-        type: 'string',
-        description:
-          'RFC 3339 timestamp for when the plan becomes active for this customer. Must be at 0:00 UTC (midnight).',
-        format: 'date-time',
-      },
-      ending_before: {
-        type: 'string',
-        description:
-          'RFC 3339 timestamp for when the plan ends (exclusive) for this customer. Must be at 0:00 UTC (midnight).',
-        format: 'date-time',
-      },
-      net_payment_terms_days: {
-        type: 'number',
-        description: 'Number of days after issuance of invoice after which the invoice is due (e.g. Net 30).',
-      },
-      overage_rate_adjustments: {
-        type: 'array',
-        description:
-          'An optional list of overage rates that override the rates of the original plan configuration. These new rates will apply to all pricing ramps.',
-        items: {
-          type: 'object',
-          properties: {
-            custom_credit_type_id: {
-              type: 'string',
-            },
-            fiat_currency_credit_type_id: {
-              type: 'string',
-            },
-            to_fiat_conversion_factor: {
-              type: 'number',
-              description: 'The overage cost in fiat currency for each credit of the custom credit type.',
-            },
-          },
-          required: ['custom_credit_type_id', 'fiat_currency_credit_type_id', 'to_fiat_conversion_factor'],
-        },
-      },
-      price_adjustments: {
-        type: 'array',
-        description:
-          'A list of price adjustments can be applied on top of the pricing in the plans. See the [price adjustments documentation](https://plans-docs.metronome.com/pricing/managing-plans/#price-adjustments) for details.',
-        items: {
-          type: 'object',
-          properties: {
-            adjustment_type: {
-              type: 'string',
-              enum: ['percentage', 'fixed', 'override', 'quantity'],
-            },
-            charge_id: {
-              type: 'string',
-            },
-            start_period: {
-              type: 'number',
-              description:
-                'Used in price ramps.  Indicates how many billing periods pass before the charge applies.',
-            },
-            quantity: {
-              type: 'number',
-              description: 'the overridden quantity for a fixed charge',
-            },
-            tier: {
-              type: 'number',
-              description: 'Used in pricing tiers.  Indicates at what metric value the price applies.',
-            },
-            value: {
-              type: 'number',
-              description:
-                'The amount of change to a price. Percentage and fixed adjustments can be positive or negative. Percentage-based adjustments should be decimals, e.g. -0.05 for a 5% discount.',
-            },
-          },
-          required: ['adjustment_type', 'charge_id', 'start_period'],
-        },
-      },
-      trial_spec: {
-        type: 'object',
-        description:
-          "A custom trial can be set for the customer's plan. See the [trial configuration documentation](https://docs.metronome.com/provisioning/configure-trials/) for details.",
-        properties: {
-          length_in_days: {
-            type: 'number',
-            description: 'Length of the trial period in days.',
-          },
-          spending_cap: {
-            type: 'object',
-            properties: {
-              amount: {
-                type: 'number',
-                description:
-                  'The credit amount in the given denomination based on the credit type, e.g. US cents.',
-              },
-              credit_type_id: {
-                type: 'string',
-                description: 'The credit type ID for the spending cap.',
-              },
-            },
-            required: ['amount', 'credit_type_id'],
-          },
-        },
-        required: ['length_in_days'],
-      },
-      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', 'plan_id', 'starting_on'],
-  },
-  annotations: {},
-};
-
-export const handler = async (client: Metronome, args: Record<string, unknown> | undefined) => {
-  const { jq_filter, ...body } = args as any;
-  try {
-    return asTextContentResult(await maybeFilter(jq_filter, await client.v1.customers.plans.add(body)));
-  } catch (error) {
-    if (error instanceof Metronome.APIError || isJqError(error)) {
-      return asErrorResult(error.message);
-    }
-    throw error;
-  }
-};
-
-export default { metadata, tool, handler };

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

@@ -1,71 +0,0 @@
-// File generated from our OpenAPI spec by Stainless. See CONTRIBUTING.md for details.
-
-import { isJqError, maybeFilter } from '@metronome/mcp/filtering';
-import { Metadata, asErrorResult, asTextContentResult } from '@metronome/mcp/tools/types';
-
-import { Tool } from '@modelcontextprotocol/sdk/types.js';
-import Metronome from '@metronome/sdk';
-
-export const metadata: Metadata = {
-  resource: 'v1.customers.plans',
-  operation: 'write',
-  tags: [],
-  httpMethod: 'post',
-  httpPath: '/v1/customers/{customer_id}/plans/{customer_plan_id}/end',
-  operationId: 'endCustomerPlan-v1',
-};
-
-export const tool: Tool = {
-  name: 'end_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\nChange the end date of a customer's plan. This is a Plans (deprecated) endpoint. New clients should implement using Contracts.\n\n\n# Response Schema\n```json\n{\n  $ref: '#/$defs/plan_end_response',\n  $defs: {\n    plan_end_response: {\n      type: 'object',\n      properties: {}\n    }\n  }\n}\n```",
-  inputSchema: {
-    type: 'object',
-    properties: {
-      customer_id: {
-        type: 'string',
-      },
-      customer_plan_id: {
-        type: 'string',
-      },
-      ending_before: {
-        type: 'string',
-        description:
-          'RFC 3339 timestamp for when the plan ends (exclusive) for this customer. Must be at 0:00 UTC (midnight). If not provided, the plan end date will be cleared.',
-        format: 'date-time',
-      },
-      void_invoices: {
-        type: 'boolean',
-        description:
-          'If true, plan end date can be before the last finalized invoice date. Any invoices generated after the plan end date will be voided.',
-      },
-      void_stripe_invoices: {
-        type: 'boolean',
-        description:
-          'Only applicable when void_invoices is set to true. If true, for every invoice that is voided we will also attempt to void/delete the stripe invoice (if any). Stripe invoices will be voided if finalized or deleted if still in draft state.',
-      },
-      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', 'customer_plan_id'],
-  },
-  annotations: {},
-};
-
-export const handler = async (client: Metronome, args: Record<string, unknown> | undefined) => {
-  const { jq_filter, ...body } = args as any;
-  try {
-    return asTextContentResult(await maybeFilter(jq_filter, await client.v1.customers.plans.end(body)));
-  } catch (error) {
-    if (error instanceof Metronome.APIError || isJqError(error)) {
-      return asErrorResult(error.message);
-    }
-    throw error;
-  }
-};
-
-export default { metadata, tool, handler };

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

@@ -1,63 +0,0 @@
-// File generated from our OpenAPI spec by Stainless. See CONTRIBUTING.md for details.
-
-import { isJqError, maybeFilter } from '@metronome/mcp/filtering';
-import { Metadata, asErrorResult, asTextContentResult } from '@metronome/mcp/tools/types';
-
-import { Tool } from '@modelcontextprotocol/sdk/types.js';
-import Metronome from '@metronome/sdk';
-
-export const metadata: Metadata = {
-  resource: 'v1.customers.plans',
-  operation: 'read',
-  tags: [],
-  httpMethod: 'get',
-  httpPath: '/v1/customers/{customer_id}/plans',
-  operationId: 'listCustomerPlans-v1',
-};
-
-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\nList the given customer's plans in reverse-chronological order. This is a Plans (deprecated) endpoint. New clients should implement using Contracts.\n\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          description: 'the ID of the customer plan'\n        },\n        custom_fields: {\n          type: 'object',\n          description: 'Custom fields to be added eg. { \"key1\": \"value1\", \"key2\": \"value2\" }',\n          additionalProperties: true\n        },\n        plan_description: {\n          type: 'string'\n        },\n        plan_id: {\n          type: 'string',\n          description: 'the ID of the plan'\n        },\n        plan_name: {\n          type: 'string'\n        },\n        starting_on: {\n          type: 'string',\n          format: 'date-time'\n        },\n        ending_before: {\n          type: 'string',\n          format: 'date-time'\n        },\n        net_payment_terms_days: {\n          type: 'number'\n        },\n        trial_info: {\n          type: 'object',\n          properties: {\n            ending_before: {\n              type: 'string',\n              format: 'date-time'\n            },\n            spending_caps: {\n              type: 'array',\n              items: {\n                type: 'object',\n                properties: {\n                  amount: {\n                    type: 'number'\n                  },\n                  amount_remaining: {\n                    type: 'number'\n                  },\n                  credit_type: {\n                    $ref: '#/$defs/credit_type_data'\n                  }\n                },\n                required: [                  'amount',\n                  'amount_remaining',\n                  'credit_type'\n                ]\n              }\n            }\n          },\n          required: [            'ending_before',\n            'spending_caps'\n          ]\n        }\n      },\n      required: [        'id',\n        'custom_fields',\n        'plan_description',\n        'plan_id',\n        'plan_name',\n        'starting_on'\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: {
-      customer_id: {
-        type: 'string',
-      },
-      limit: {
-        type: 'integer',
-        description: 'Max number of results that should be returned',
-      },
-      next_page: {
-        type: 'string',
-        description: 'Cursor that indicates where the next page of results should start.',
-      },
-      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: {
-    readOnlyHint: true,
-  },
-};
-
-export const handler = async (client: Metronome, args: Record<string, unknown> | undefined) => {
-  const { jq_filter, ...body } = args as any;
-  const response = await client.v1.customers.plans.list(body).asResponse();
-  try {
-    return asTextContentResult(await maybeFilter(jq_filter, await response.json()));
-  } catch (error) {
-    if (error instanceof Metronome.APIError || isJqError(error)) {
-      return asErrorResult(error.message);
-    }
-    throw error;
-  }
-};
-
-export default { metadata, tool, handler };

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

@@ -1,66 +0,0 @@
-// File generated from our OpenAPI spec by Stainless. See CONTRIBUTING.md for details.
-
-import { isJqError, maybeFilter } from '@metronome/mcp/filtering';
-import { Metadata, asErrorResult, asTextContentResult } from '@metronome/mcp/tools/types';
-
-import { Tool } from '@modelcontextprotocol/sdk/types.js';
-import Metronome from '@metronome/sdk';
-
-export const metadata: Metadata = {
-  resource: 'v1.customers.plans',
-  operation: 'read',
-  tags: [],
-  httpMethod: 'get',
-  httpPath: '/v1/customers/{customer_id}/plans/{customer_plan_id}/priceAdjustments',
-  operationId: 'getPlanPriceAdjustments-v1',
-};
-
-export const tool: Tool = {
-  name: 'list_price_adjustments_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\nLists a customer plans adjustments. See the [price adjustments documentation](https://plans-docs.metronome.com/pricing/managing-plans/#price-adjustments) for details. This is a Plans (deprecated) endpoint. New clients should implement using Contracts.\n\n\n# Response Schema\n```json\n{\n  type: 'object',\n  properties: {\n    data: {\n      type: 'array',\n      items: {\n        $ref: '#/$defs/plan_list_price_adjustments_response'\n      }\n    },\n    next_page: {\n      type: 'string'\n    }\n  },\n  required: [    'data',\n    'next_page'\n  ],\n  $defs: {\n    plan_list_price_adjustments_response: {\n      type: 'object',\n      properties: {\n        charge_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        prices: {\n          type: 'array',\n          items: {\n            type: 'object',\n            properties: {\n              adjustment_type: {\n                type: 'string',\n                description: 'Determines how the value will be applied.',\n                enum: [                  'fixed',\n                  'quantity',\n                  'percentage',\n                  'override'\n                ]\n              },\n              quantity: {\n                type: 'number'\n              },\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            },\n            required: [              'adjustment_type'\n            ]\n          }\n        },\n        start_period: {\n          type: 'number'\n        },\n        quantity: {\n          type: 'number'\n        }\n      },\n      required: [        'charge_id',\n        'charge_type',\n        'prices',\n        'start_period'\n      ]\n    }\n  }\n}\n```",
-  inputSchema: {
-    type: 'object',
-    properties: {
-      customer_id: {
-        type: 'string',
-      },
-      customer_plan_id: {
-        type: 'string',
-      },
-      limit: {
-        type: 'integer',
-        description: 'Max number of results that should be returned',
-      },
-      next_page: {
-        type: 'string',
-        description: 'Cursor that indicates where the next page of results should start.',
-      },
-      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', 'customer_plan_id'],
-  },
-  annotations: {
-    readOnlyHint: true,
-  },
-};
-
-export const handler = async (client: Metronome, args: Record<string, unknown> | undefined) => {
-  const { jq_filter, ...body } = args as any;
-  const response = await client.v1.customers.plans.listPriceAdjustments(body).asResponse();
-  try {
-    return asTextContentResult(await maybeFilter(jq_filter, await response.json()));
-  } catch (error) {
-    if (error instanceof Metronome.APIError || isJqError(error)) {
-      return asErrorResult(error.message);
-    }
-    throw error;
-  }
-};
-
-export default { metadata, tool, handler };

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

@@ -1,82 +0,0 @@
-// File generated from our OpenAPI spec by Stainless. See CONTRIBUTING.md for details.
-
-import { Metadata, asErrorResult, asTextContentResult } from '@metronome/mcp/tools/types';
-
-import { Tool } from '@modelcontextprotocol/sdk/types.js';
-import Metronome from '@metronome/sdk';
-
-export const metadata: Metadata = {
-  resource: 'v1.customers',
-  operation: 'write',
-  tags: [],
-  httpMethod: 'post',
-  httpPath: '/v1/customers/{customer_id}/previewEvents',
-  operationId: 'previewCustomerEvents-v1',
-};
-
-export const tool: Tool = {
-  name: 'preview_events_v1_customers',
-  description:
-    "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. Customers on contracts with SQL billable metrics are not supported.\n",
-  inputSchema: {
-    type: 'object',
-    properties: {
-      customer_id: {
-        type: 'string',
-      },
-      events: {
-        type: 'array',
-        description:
-          'Array of usage events to include in the preview calculation. Must contain at least one event in `merge` mode.\n',
-        items: {
-          type: 'object',
-          properties: {
-            event_type: {
-              type: 'string',
-            },
-            properties: {
-              type: 'object',
-              additionalProperties: true,
-            },
-            timestamp: {
-              type: 'string',
-              description: 'RFC 3339 formatted. If not provided, the current time will be used.',
-            },
-            transaction_id: {
-              type: 'string',
-              description:
-                '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'],
-        },
-      },
-      mode: {
-        type: 'string',
-        description:
-          "Controls how the provided events are combined with existing usage data. Use `replace` to calculate the preview as if these are the only events for the customer, ignoring all historical usage.  Use `merge` to combine these events with the customer's existing usage.  Defaults to `replace`.",
-        enum: ['replace', 'merge'],
-      },
-      skip_zero_qty_line_items: {
-        type: 'boolean',
-        description: 'When `true`, line items with zero quantity are excluded from the response.',
-      },
-    },
-    required: ['customer_id', 'events'],
-  },
-  annotations: {},
-};
-
-export const handler = async (client: Metronome, args: Record<string, unknown> | undefined) => {
-  const body = args as any;
-  try {
-    return asTextContentResult(await client.v1.customers.previewEvents(body));
-  } catch (error) {
-    if (error instanceof Metronome.APIError) {
-      return asErrorResult(error.message);
-    }
-    throw error;
-  }
-};
-
-export default { metadata, tool, handler };

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

@@ -1,57 +0,0 @@
-// File generated from our OpenAPI spec by Stainless. See CONTRIBUTING.md for details.
-
-import { isJqError, maybeFilter } from '@metronome/mcp/filtering';
-import { Metadata, asErrorResult, asTextContentResult } from '@metronome/mcp/tools/types';
-
-import { Tool } from '@modelcontextprotocol/sdk/types.js';
-import Metronome from '@metronome/sdk';
-
-export const metadata: Metadata = {
-  resource: 'v1.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                  'metronome'\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;
-  try {
-    return asTextContentResult(
-      await maybeFilter(jq_filter, await client.v1.customers.retrieveBillingConfigurations(body)),
-    );
-  } catch (error) {
-    if (error instanceof Metronome.APIError || isJqError(error)) {
-      return asErrorResult(error.message);
-    }
-    throw error;
-  }
-};
-
-export default { metadata, tool, handler };

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

@@ -1,54 +0,0 @@
-// File generated from our OpenAPI spec by Stainless. See CONTRIBUTING.md for details.
-
-import { isJqError, maybeFilter } from '@metronome/mcp/filtering';
-import { Metadata, asErrorResult, asTextContentResult } from '@metronome/mcp/tools/types';
-
-import { Tool } from '@modelcontextprotocol/sdk/types.js';
-import Metronome from '@metronome/sdk';
-
-export const metadata: Metadata = {
-  resource: 'v1.customers',
-  operation: 'read',
-  tags: [],
-  httpMethod: 'get',
-  httpPath: '/v1/customers/{customer_id}',
-  operationId: 'getCustomer-v1',
-};
-
-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 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: {
-      customer_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'],
-  },
-  annotations: {
-    readOnlyHint: true,
-  },
-};
-
-export const handler = async (client: Metronome, args: Record<string, unknown> | undefined) => {
-  const { jq_filter, ...body } = args as any;
-  try {
-    return asTextContentResult(await maybeFilter(jq_filter, await client.v1.customers.retrieve(body)));
-  } catch (error) {
-    if (error instanceof Metronome.APIError || isJqError(error)) {
-      return asErrorResult(error.message);
-    }
-    throw error;
-  }
-};
-
-export default { metadata, tool, handler };