@metronome/mcp 2.2.0 → 3.4.1

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

@@ -1,215 +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/customers',
-  operationId: 'createCustomer-v1',
-};
-
-export const tool: Tool = {
-  name: 'create_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\nCreate a new customer in Metronome and optionally the billing configuration (recommended) which dictates where invoices for the customer will be sent or where payment will be collected. \n\n### Use this endpoint to:\nExecute your customer provisioning workflows for either PLG motions, where customers originate in your platform, or SLG motions, where customers originate in your sales system.\n\n### Key response fields: \nThis end-point returns the `customer_id` created by the request. This id can be used to fetch relevant billing configurations and create contracts.\n\n### Example workflow:\n- Generally, Metronome recommends first creating the customer in the downstream payment / ERP system when payment method is collected and then creating the customer in Metronome using the response (i.e. `customer_id`) from the downstream system. If you do not create a billing configuration on customer creation, you can add it later.        \n- Once a customer is created, you can then create a contract for the customer. In the contract creation process, you will need to add the customer billing configuration to the contract to ensure Metronome invoices the customer correctly. This is because a customer can have multiple configurations.\n- As part of the customer creation process, set the ingest alias for the customer which will ensure usage is accurately mapped to the customer. Ingest aliases can be added or changed after the creation process as well.\n\n### Usage guidelines:\nFor details on different billing configurations for different systems, review the `/setCustomerBillingConfiguration` end-point.\n\n\n# Response Schema\n```json\n{\n  $ref: '#/$defs/customer_create_response',\n  $defs: {\n    customer_create_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: {
-      name: {
-        type: 'string',
-        description: 'This will be truncated to 160 characters if the provided name is longer.',
-      },
-      billing_config: {
-        type: 'object',
-        properties: {
-          billing_provider_customer_id: {
-            type: 'string',
-          },
-          billing_provider_type: {
-            type: 'string',
-            enum: [
-              'aws_marketplace',
-              'stripe',
-              'netsuite',
-              'custom',
-              'azure_marketplace',
-              'quickbooks_online',
-              'workday',
-              'gcp_marketplace',
-              'metronome',
-            ],
-          },
-          aws_customer_account_id: {
-            type: 'string',
-          },
-          aws_customer_id: {
-            type: 'string',
-          },
-          aws_is_subscription_product: {
-            type: 'boolean',
-            description: 'True if the aws_product_code is a SAAS subscription product, false otherwise.',
-          },
-          aws_product_code: {
-            type: 'string',
-          },
-          aws_region: {
-            type: 'string',
-            enum: [
-              'af-south-1',
-              'ap-east-1',
-              'ap-northeast-1',
-              'ap-northeast-2',
-              'ap-northeast-3',
-              'ap-south-1',
-              'ap-southeast-1',
-              'ap-southeast-2',
-              'ca-central-1',
-              'cn-north-1',
-              'cn-northwest-1',
-              'eu-central-1',
-              'eu-north-1',
-              'eu-south-1',
-              'eu-west-1',
-              'eu-west-2',
-              'eu-west-3',
-              'me-south-1',
-              'sa-east-1',
-              'us-east-1',
-              'us-east-2',
-              'us-gov-east-1',
-              'us-gov-west-1',
-              'us-west-1',
-              'us-west-2',
-            ],
-          },
-          stripe_collection_method: {
-            type: 'string',
-            description:
-              "The collection method for the customer's invoices.\nNOTE: `auto_charge_payment_intent` and `manually_charge_payment_intent` are in beta.",
-            enum: [
-              'charge_automatically',
-              'send_invoice',
-              'auto_charge_payment_intent',
-              'manually_charge_payment_intent',
-            ],
-          },
-        },
-        required: ['billing_provider_customer_id', 'billing_provider_type'],
-      },
-      custom_fields: {
-        type: 'object',
-        description: 'Custom fields to be added eg. { "key1": "value1", "key2": "value2" }',
-        additionalProperties: true,
-      },
-      customer_billing_provider_configurations: {
-        type: 'array',
-        items: {
-          type: 'object',
-          properties: {
-            billing_provider: {
-              type: 'string',
-              description: 'The billing provider set for this configuration.',
-              enum: ['aws_marketplace', 'azure_marketplace', 'gcp_marketplace', 'stripe', 'netsuite'],
-            },
-            configuration: {
-              type: 'object',
-              description:
-                'Configuration for the billing provider. The structure of this object is specific to the billing provider and delivery provider combination. Defaults to an empty object, however, for most billing provider + delivery method combinations, it will not be a valid configuration.',
-              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_revenue_system_configurations: {
-        type: 'array',
-        items: {
-          type: 'object',
-          properties: {
-            provider: {
-              type: 'string',
-              description: 'The revenue system provider set for this configuration.',
-              enum: ['netsuite'],
-            },
-            configuration: {
-              type: 'object',
-              description:
-                'Configuration for the revenue system provider. The structure of this object is specific to the revenue system provider. For NetSuite, this should contain `netsuite_customer_id`.',
-              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'],
-            },
-            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.',
-            },
-          },
-          required: ['provider'],
-        },
-      },
-      external_id: {
-        type: 'string',
-        description:
-          '(deprecated, use ingest_aliases instead) an alias that can be used to refer to this customer in usage events',
-      },
-      ingest_aliases: {
-        type: 'array',
-        description: 'Aliases that can be used to refer to this customer in usage events',
-        items: {
-          type: 'string',
-        },
-      },
-      jq_filter: {
-        type: 'string',
-        title: 'jq Filter',
-        description:
-          'A jq filter to apply to the response to include certain fields. Consult the output schema in the tool description to see the fields that are available.\n\nFor example: to include only the `name` field in every object of a results array, you can provide ".results[].name".\n\nFor more information, see the [jq documentation](https://jqlang.org/manual/).',
-      },
-    },
-    required: ['name'],
-  },
-  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.create(body)));
-  } catch (error) {
-    if (error instanceof Metronome.APIError || isJqError(error)) {
-      return asErrorResult(error.message);
-    }
-    throw error;
-  }
-};
-
-export default { metadata, tool, handler };

package/src/tools/v1/customers/credits/create-customers-v1-credits.ts

@@ -1,182 +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.credits',
-  operation: 'write',
-  tags: [],
-  httpMethod: 'post',
-  httpPath: '/v1/contracts/customerCredits/create',
-  operationId: 'createCustomerCredit-v1',
-};
-
-export const tool: Tool = {
-  name: 'create_customers_v1_credits',
-  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\nCreates customer-level credits that provide spending allowances or free credit balances for customers across their Metronome usage. Note: In most cases, you should add credits directly to customer contracts using the contract/create or contract/edit APIs.\n\n### Use this endpoint to:\nUse this endpoint when you need to provision credits directly at the customer level that can be applied across multiple contracts or scoped to specific contracts. Customer-level credits are ideal for:\n- Customer onboarding incentives that apply globally\n- Flexible spending allowances that aren't tied to a single contract\n- Migration scenarios where you need to preserve existing customer balances\n\n#### Scoping flexibility: \nCustomer-level credits can be configured in two ways:\n- Contract-specific: Use the applicable_contract_ids field to limit the credit to specific contracts\n- Cross-contract: Leave applicable_contract_ids empty to allow the credit to be used across all of the customer's contracts\n\n#### Product Targeting: \nCredits can be scoped to specific products using `applicable_product_ids` or `applicable_product_tags`, or left unrestricted to apply to all products.\n\n#### Priority considerations: \nWhen multiple credits are applicable, the one with the lower priority value will be consumed first. If there is a tie, contract level commits and credits will be applied before customer level commits and credits. Plan your priority scheme carefully to ensure credits are applied in the desired order.\n\n#### Access Schedule Required: \nYou must provide an `access_schedule` that defines when and how much credit becomes available to the customer over time. This usually is aligned to the contract schedule or starts immediately and is set to expire in the future.\n\n### Usage Guidelines:\n⚠️ Preferred Alternative: In most cases, you should add credits directly to contracts using the contract/create or contract/edit APIs instead of creating customer-level credits. Contract-level credits provide better organization, and are easier for finance teams to recognize revenue, and are the recommended approach for most use cases.\n\n\n# Response Schema\n```json\n{\n  $ref: '#/$defs/credit_create_response',\n  $defs: {\n    credit_create_response: {\n      type: 'object',\n      properties: {\n        data: {\n          $ref: '#/$defs/id'\n        }\n      },\n      required: [        'data'\n      ]\n    },\n    id: {\n      type: 'object',\n      properties: {\n        id: {\n          type: 'string'\n        }\n      },\n      required: [        'id'\n      ]\n    }\n  }\n}\n```",
-  inputSchema: {
-    type: 'object',
-    properties: {
-      access_schedule: {
-        type: 'object',
-        description: 'Schedule for distributing the credit to the customer.',
-        properties: {
-          schedule_items: {
-            type: 'array',
-            items: {
-              type: 'object',
-              properties: {
-                amount: {
-                  type: 'number',
-                },
-                ending_before: {
-                  type: 'string',
-                  description: 'RFC 3339 timestamp (exclusive)',
-                  format: 'date-time',
-                },
-                starting_at: {
-                  type: 'string',
-                  description: 'RFC 3339 timestamp (inclusive)',
-                  format: 'date-time',
-                },
-              },
-              required: ['amount', 'ending_before', 'starting_at'],
-            },
-          },
-          credit_type_id: {
-            type: 'string',
-            description: 'Defaults to USD (cents) if not passed',
-          },
-        },
-        required: ['schedule_items'],
-      },
-      customer_id: {
-        type: 'string',
-      },
-      priority: {
-        type: 'number',
-        description:
-          'If multiple credits or commits are applicable, the one with the lower priority will apply first.',
-      },
-      product_id: {
-        type: 'string',
-      },
-      applicable_contract_ids: {
-        type: 'array',
-        description:
-          'Which contract the credit applies to. If not provided, the credit applies to all contracts.',
-        items: {
-          type: 'string',
-        },
-      },
-      applicable_product_ids: {
-        type: 'array',
-        description:
-          'Which products the credit applies to. If both applicable_product_ids and applicable_product_tags are not provided, the credit applies to all products.',
-        items: {
-          type: 'string',
-        },
-      },
-      applicable_product_tags: {
-        type: 'array',
-        description:
-          'Which tags the credit applies to. If both applicable_product_ids and applicable_product_tags are not provided, the credit applies to all products.',
-        items: {
-          type: 'string',
-        },
-      },
-      custom_fields: {
-        type: 'object',
-        description: 'Custom fields to be added eg. { "key1": "value1", "key2": "value2" }',
-        additionalProperties: true,
-      },
-      description: {
-        type: 'string',
-        description: 'Used only in UI/API. It is not exposed to end customers.',
-      },
-      name: {
-        type: 'string',
-        description: 'displayed on invoices',
-      },
-      netsuite_sales_order_id: {
-        type: 'string',
-        description: "This field's availability is dependent on your client's configuration.",
-      },
-      rate_type: {
-        type: 'string',
-        enum: ['COMMIT_RATE', 'LIST_RATE'],
-      },
-      salesforce_opportunity_id: {
-        type: 'string',
-        description: "This field's availability is dependent on your client's configuration.",
-      },
-      specifiers: {
-        type: 'array',
-        description:
-          "List of filters that determine what kind of customer usage draws down a commit or credit. A customer's usage needs to meet the condition of at least one of the specifiers to contribute to a commit's or credit's drawdown. This field cannot be used together with `applicable_product_ids` or `applicable_product_tags`.",
-        items: {
-          $ref: '#/$defs/commit_specifier_input',
-        },
-      },
-      uniqueness_key: {
-        type: 'string',
-        description:
-          'Prevents the creation of duplicates. If a request to create a commit or credit is made with a uniqueness key that was previously used to create a commit or credit, a new record will not be created and the request will fail with a 409 error.',
-      },
-      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: ['access_schedule', 'customer_id', 'priority', 'product_id'],
-    $defs: {
-      commit_specifier_input: {
-        type: 'object',
-        properties: {
-          presentation_group_values: {
-            type: 'object',
-            additionalProperties: true,
-          },
-          pricing_group_values: {
-            type: 'object',
-            additionalProperties: true,
-          },
-          product_id: {
-            type: 'string',
-            description: 'If provided, the specifier will only apply to the product with the specified ID.',
-          },
-          product_tags: {
-            type: 'array',
-            description:
-              'If provided, the specifier will only apply to products with all the specified tags.',
-            items: {
-              type: 'string',
-            },
-          },
-        },
-      },
-    },
-  },
-  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.credits.create(body)));
-  } catch (error) {
-    if (error instanceof Metronome.APIError || isJqError(error)) {
-      return asErrorResult(error.message);
-    }
-    throw error;
-  }
-};
-
-export default { metadata, tool, handler };

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

@@ -1,90 +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.credits',
-  operation: 'write',
-  tags: [],
-  httpMethod: 'post',
-  httpPath: '/v1/contracts/customerCredits/list',
-  operationId: 'listCustomerCredits-v1',
-};
-
-export const tool: Tool = {
-  name: 'list_customers_v1_credits',
-  description:
-    'Retrieve a detailed list of all credits available to a customer, including promotional credits and contract-specific credits. This endpoint provides comprehensive visibility into credit balances, access schedules, and usage rules, enabling you to build credit management interfaces and track available funding.\n\n### Use this endpoint to:\n- Display all available credits in customer billing dashboards\n- Show credit balances and expiration dates\n- Track credit usage history with optional ledger details\n- Build credit management and reporting tools\n- Monitor promotional credit utilization\n• Support customer inquiries about available credits\n\n### Key response fields:\nAn array of Credit objects containing:\n- Credit details: Name, priority, and which applicable products/tags it applies to\n- Product ID: The `product_id` of the credit. This is for external mapping into your quote-to-cash stack, not the product it applies to. \n- Access schedule: When credits become available and expire\n- Optional ledger entries: Transaction history (if `include_ledgers=true`)\n- Balance information: Current available amount (if `include_balance=true`)\n- Metadata: Custom fields and usage specifiers\n\n### Usage guidelines:\n- Pagination: Results limited to 25 commits per page; use next_page for more\n- Date filtering options:\n    - `covering_date`: Credits active on a specific date\n    - `starting_at`: Credits with access on/after a date\n    - `effective_before`: Credits with access before a date (exclusive)\n- Scope options:\n    - `include_contract_credits`: Include contract-level credits (not just customer-level)\n    - `include_archived`: Include archived credits and credits from archived contracts\n- Performance considerations:\n    - `include_ledgers`: Adds detailed transaction history (slower)\n    - `include_balance`: Adds current balance calculation (slower)\n- Optional filtering: Use credit_id to retrieve a specific commit\n',
-  inputSchema: {
-    type: 'object',
-    properties: {
-      customer_id: {
-        type: 'string',
-      },
-      covering_date: {
-        type: 'string',
-        description: 'Return only credits that have access schedules that "cover" the provided date',
-        format: 'date-time',
-      },
-      credit_id: {
-        type: 'string',
-      },
-      effective_before: {
-        type: 'string',
-        description: 'Include only credits that have any access before the provided date (exclusive)',
-        format: 'date-time',
-      },
-      include_archived: {
-        type: 'boolean',
-        description: 'Include archived credits and credits from archived contracts.',
-      },
-      include_balance: {
-        type: 'boolean',
-        description:
-          'Include the balance in the response. Setting this flag may cause the query to be slower.',
-      },
-      include_contract_credits: {
-        type: 'boolean',
-        description: 'Include credits on the contract level.',
-      },
-      include_ledgers: {
-        type: 'boolean',
-        description:
-          'Include credit ledgers in the response. Setting this flag may cause the query to be slower.',
-      },
-      limit: {
-        type: 'integer',
-        description: 'The maximum number of commits to return. Defaults to 25.',
-      },
-      next_page: {
-        type: 'string',
-        description: 'The next page token from a previous response.',
-      },
-      starting_at: {
-        type: 'string',
-        description: 'Include only credits that have any access on or after the provided date',
-        format: 'date-time',
-      },
-    },
-    required: ['customer_id'],
-  },
-  annotations: {},
-};
-
-export const handler = async (client: Metronome, args: Record<string, unknown> | undefined) => {
-  const body = args as any;
-  const response = await client.v1.customers.credits.list(body).asResponse();
-  try {
-    return asTextContentResult(await response.json());
-  } catch (error) {
-    if (error instanceof Metronome.APIError) {
-      return asErrorResult(error.message);
-    }
-    throw error;
-  }
-};
-
-export default { metadata, tool, handler };

package/src/tools/v1/customers/credits/update-end-date-customers-v1-credits.ts

@@ -1,65 +0,0 @@
-// File generated from our OpenAPI spec by Stainless. See CONTRIBUTING.md for details.
-
-import { isJqError, maybeFilter } from '@metronome/mcp/filtering';
-import { Metadata, asErrorResult, asTextContentResult } from '@metronome/mcp/tools/types';
-
-import { Tool } from '@modelcontextprotocol/sdk/types.js';
-import Metronome from '@metronome/sdk';
-
-export const metadata: Metadata = {
-  resource: 'v1.customers.credits',
-  operation: 'write',
-  tags: [],
-  httpMethod: 'post',
-  httpPath: '/v1/contracts/customerCredits/updateEndDate',
-  operationId: 'updateCreditEndDate-v1',
-};
-
-export const tool: Tool = {
-  name: 'update_end_date_customers_v1_credits',
-  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\nShortens the end date of an existing customer credit to terminate it earlier than originally scheduled. Only allows moving end dates forward (earlier), not extending them. \n\nNote: To extend credit end dates or make comprehensive edits, use the 'edit credit' endpoint instead.\n\n\n# Response Schema\n```json\n{\n  $ref: '#/$defs/credit_update_end_date_response',\n  $defs: {\n    credit_update_end_date_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: {
-      access_ending_before: {
-        type: 'string',
-        description:
-          'RFC 3339 timestamp indicating when access to the credit will end and it will no longer be possible to draw it down (exclusive).',
-        format: 'date-time',
-      },
-      credit_id: {
-        type: 'string',
-        description: 'ID of the commit to update',
-      },
-      customer_id: {
-        type: 'string',
-        description: 'ID of the customer whose credit is to be updated',
-      },
-      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: ['access_ending_before', 'credit_id', '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.credits.updateEndDate(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/invoices/add-charge-customers-v1-invoices.ts

@@ -1,87 +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.invoices',
-  operation: 'write',
-  tags: [],
-  httpMethod: 'post',
-  httpPath: '/v1/customers/{customer_id}/addCharge',
-  operationId: 'addOneTimeCharge-v1',
-};
-
-export const tool: Tool = {
-  name: 'add_charge_customers_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\nAdd a one time charge to the specified invoice. This is a Plans (deprecated) endpoint. New clients should implement using Contracts.\n\n\n# Response Schema\n```json\n{\n  $ref: '#/$defs/invoice_add_charge_response',\n  $defs: {\n    invoice_add_charge_response: {\n      type: 'object',\n      properties: {}\n    }\n  }\n}\n```",
-  inputSchema: {
-    type: 'object',
-    properties: {
-      customer_id: {
-        type: 'string',
-      },
-      charge_id: {
-        type: 'string',
-        description:
-          'The Metronome ID of the charge to add to the invoice. Note that the charge must be on a product that is not on the current plan, and the product must have only fixed charges.',
-      },
-      customer_plan_id: {
-        type: 'string',
-        description: 'The Metronome ID of the customer plan to add the charge to.',
-      },
-      description: {
-        type: 'string',
-      },
-      invoice_start_timestamp: {
-        type: 'string',
-        description: 'The start_timestamp of the invoice to add the charge to.',
-        format: 'date-time',
-      },
-      price: {
-        type: 'number',
-        description:
-          'The price of the charge. This price will match the currency on the invoice, e.g. USD cents.',
-      },
-      quantity: {
-        type: 'number',
-      },
-      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',
-      'charge_id',
-      'customer_plan_id',
-      'description',
-      'invoice_start_timestamp',
-      'price',
-      'quantity',
-    ],
-  },
-  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.invoices.addCharge(body)),
-    );
-  } catch (error) {
-    if (error instanceof Metronome.APIError || isJqError(error)) {
-      return asErrorResult(error.message);
-    }
-    throw error;
-  }
-};
-
-export default { metadata, tool, handler };