@metronome/mcp 2.1.0 → 3.0.0

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

@@ -1,63 +0,0 @@
-// 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.billing_config',
-  operation: 'read',
-  tags: [],
-  httpMethod: 'get',
-  httpPath: '/v1/customers/{customer_id}/billing-config/{billing_provider_type}',
-  operationId: 'getBillingConfig-v1',
-};
-
-export const tool: Tool = {
-  name: 'retrieve_customers_v1_billing_config',
-  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 the billing configuration for the given customer. This is a Plans (deprecated) endpoint. New clients should implement using Contracts.\n\n\n# Response Schema\n```json\n{\n  $ref: '#/$defs/billing_config_retrieve_response',\n  $defs: {\n    billing_config_retrieve_response: {\n      type: 'object',\n      properties: {\n        data: {\n          type: 'object',\n          properties: {\n            aws_expiration_date: {\n              type: 'string',\n              description: 'Contract expiration date for the customer. The expected format is RFC 3339 and can be retrieved from [AWS\\'s GetEntitlements API](https://docs.aws.amazon.com/marketplaceentitlement/latest/APIReference/API_GetEntitlements.html).',\n              format: 'date-time'\n            },\n            aws_is_subscription_product: {\n              type: 'boolean',\n              description: 'True if the aws_product_code is a SAAS subscription product, false otherwise.'\n            },\n            aws_product_code: {\n              type: 'string'\n            },\n            aws_region: {\n              type: 'string',\n              enum: [                'af-south-1',\n                'ap-east-1',\n                'ap-northeast-1',\n                'ap-northeast-2',\n                'ap-northeast-3',\n                'ap-south-1',\n                'ap-southeast-1',\n                'ap-southeast-2',\n                'ca-central-1',\n                'cn-north-1',\n                'cn-northwest-1',\n                'eu-central-1',\n                'eu-north-1',\n                'eu-south-1',\n                'eu-west-1',\n                'eu-west-2',\n                'eu-west-3',\n                'me-south-1',\n                'sa-east-1',\n                'us-east-1',\n                'us-east-2',\n                'us-gov-east-1',\n                'us-gov-west-1',\n                'us-west-1',\n                'us-west-2'\n              ]\n            },\n            azure_expiration_date: {\n              type: 'string',\n              description: 'Subscription term start/end date for the customer. The expected format is RFC 3339 and can be retrieved from [Azure\\'s Get Subscription API](https://learn.microsoft.com/en-us/partner-center/marketplace/partner-center-portal/pc-saas-fulfillment-subscription-api#get-subscription).',\n              format: 'date-time'\n            },\n            azure_plan_id: {\n              type: 'string'\n            },\n            azure_start_date: {\n              type: 'string',\n              description: 'Subscription term start/end date for the customer. The expected format is RFC 3339 and can be retrieved from [Azure\\'s Get Subscription API](https://learn.microsoft.com/en-us/partner-center/marketplace/partner-center-portal/pc-saas-fulfillment-subscription-api#get-subscription).',\n              format: 'date-time'\n            },\n            azure_subscription_status: {\n              type: 'string',\n              enum: [                'Subscribed',\n                'Unsubscribed',\n                'Suspended',\n                'PendingFulfillmentStart'\n              ]\n            },\n            billing_provider_customer_id: {\n              type: 'string'\n            },\n            stripe_collection_method: {\n              type: 'string',\n              description: 'The collection method for the customer\\'s invoices.\\nNOTE: `auto_charge_payment_intent` and `manually_charge_payment_intent` are in beta.',\n              enum: [                'charge_automatically',\n                'send_invoice',\n                'auto_charge_payment_intent',\n                'manually_charge_payment_intent'\n              ]\n            }\n          }\n        }\n      },\n      required: [        'data'\n      ]\n    }\n  }\n}\n```",
-  inputSchema: {
-    type: 'object',
-    properties: {
-      customer_id: {
-        type: 'string',
-      },
-      billing_provider_type: {
-        type: 'string',
-        enum: [
-          'aws_marketplace',
-          'stripe',
-          'netsuite',
-          'custom',
-          'azure_marketplace',
-          'quickbooks_online',
-          'workday',
-          'gcp_marketplace',
-          'metronome',
-        ],
-      },
-      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', 'billing_provider_type'],
-  },
-  annotations: {
-    readOnlyHint: true,
-  },
-};
-
-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.billingConfig.retrieve(body)),
-  );
-};
-
-export default { metadata, tool, handler };

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

@@ -1,267 +0,0 @@
-// File generated from our OpenAPI spec by Stainless. See CONTRIBUTING.md for details.
-
-import { Metadata, asTextContentResult } from '@metronome/mcp/tools/types';
-
-import { Tool } from '@modelcontextprotocol/sdk/types.js';
-import Metronome from '@metronome/sdk';
-
-export const metadata: Metadata = {
-  resource: 'v1.customers.commits',
-  operation: 'write',
-  tags: [],
-  httpMethod: 'post',
-  httpPath: '/v1/contracts/customerCommits/create',
-  operationId: 'createCustomerCommit-v1',
-};
-
-export const tool: Tool = {
-  name: 'create_customers_v1_commits',
-  description:
-    'Creates customer-level commits that establish spending commitments for customers across their Metronome usage. Commits represent contracted spending obligations that can be either prepaid (paid upfront) or postpaid (billed later). \n\nNote: In most cases, you should add commitments 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 establish customer-level spending commitments that can be applied across multiple contracts or scoped to specific contracts. Customer-level commits are ideal for:\n- Enterprise-wide minimum spending agreements that span multiple contracts\n- Multi-contract volume commitments with shared spending pools\n- Cross-contract discount tiers based on aggregate usage\n\n#### Commit type Requirements: \n- You must specify either "prepaid" or "postpaid" as the commit type:\n- Prepaid commits: Customer pays upfront; invoice_schedule is optional (if omitted, creates a commit without an invoice)\n- Postpaid commits: Customer pays when the commitment expires (the end of the access_schedule); invoice_schedule is required and must match access_schedule totals. \n\n#### Billing configuration:\n- invoice_contract_id is required for postpaid commits and for prepaid commits with billing (only optional for free prepaid commits) unless do_not_invoice is set to true\n- For postpaid commits: access_schedule and invoice_schedule must have matching amounts\n- For postpaid commits: only one schedule item is allowed in both schedules.\n\n#### Scoping flexibility:\nCustomer-level commits can be configured in a few ways:\n- Contract-specific: Use the `applicable_contract_ids` field to limit the commit to specific contracts\n- Cross-contract: Leave `applicable_contract_ids` empty to allow the commit to be used across all of the customer\'s contracts\n\n#### Product targeting:\nCommits can be scoped to specific products using applicable_product_ids, applicable_product_tags, or specifiers, or left unrestricted to apply to all products.\n\n#### Priority considerations:\nWhen multiple commits 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 commits are applied in the desired order.\n\n### Usage guidelines:\n⚠️ Preferred Alternative: In most cases, you should add commits directly to contracts using the create contract or edit contract APIs instead of creating customer-level commits. Contract-level commits provide better organization and are the recommended approach for standard use cases.\n',
-  inputSchema: {
-    type: 'object',
-    properties: {
-      access_schedule: {
-        type: 'object',
-        description:
-          'Schedule for distributing the commit to the customer. For "POSTPAID" commits only one schedule item is allowed and amount must match invoice_schedule total.',
-        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',
-        description:
-          'ID of the fixed product associated with the commit. This is required because products are used to invoice the commit amount.',
-      },
-      type: {
-        type: 'string',
-        enum: ['PREPAID', 'POSTPAID'],
-      },
-      applicable_contract_ids: {
-        type: 'array',
-        description:
-          'Which contract the commit applies to. If not provided, the commit applies to all contracts.',
-        items: {
-          type: 'string',
-        },
-      },
-      applicable_product_ids: {
-        type: 'array',
-        description:
-          'Which products the commit applies to. If applicable_product_ids, applicable_product_tags or specifiers are not provided, the commit applies to all products.',
-        items: {
-          type: 'string',
-        },
-      },
-      applicable_product_tags: {
-        type: 'array',
-        description:
-          'Which tags the commit applies to. If applicable_product_ids, applicable_product_tags or specifiers are not provided, the commit 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.',
-      },
-      invoice_contract_id: {
-        type: 'string',
-        description:
-          'The contract that this commit will be billed on. This is required for "POSTPAID" commits and for "PREPAID" commits unless there is no invoice schedule above (i.e., the commit is \'free\'), or if do_not_invoice is set to true.',
-      },
-      invoice_schedule: {
-        type: 'object',
-        description:
-          'Required for "POSTPAID" commits: the true up invoice will be generated at this time and only one schedule item is allowed; the total must match accesss_schedule amount. Optional for "PREPAID" commits: if not provided, this will be a "complimentary" commit with no invoice.',
-        properties: {
-          credit_type_id: {
-            type: 'string',
-            description: 'Defaults to USD (cents) if not passed.',
-          },
-          do_not_invoice: {
-            type: 'boolean',
-            description:
-              'This field is only applicable to commit invoice schedules. If true, this schedule will not generate an invoice.',
-          },
-          recurring_schedule: {
-            type: 'object',
-            description:
-              'Enter the unit price and quantity for the charge or instead only send the amount. If amount is sent, the unit price is assumed to be the amount and quantity is inferred to be 1.',
-            properties: {
-              amount_distribution: {
-                type: 'string',
-                enum: ['DIVIDED', 'DIVIDED_ROUNDED', 'EACH'],
-              },
-              ending_before: {
-                type: 'string',
-                description: 'RFC 3339 timestamp (exclusive).',
-                format: 'date-time',
-              },
-              frequency: {
-                type: 'string',
-                enum: ['MONTHLY', 'QUARTERLY', 'SEMI_ANNUAL', 'ANNUAL'],
-              },
-              starting_at: {
-                type: 'string',
-                description: 'RFC 3339 timestamp (inclusive).',
-                format: 'date-time',
-              },
-              amount: {
-                type: 'number',
-                description:
-                  'Amount for the charge. Can be provided instead of unit_price and quantity. If amount is sent, the unit_price is assumed to be the amount and quantity is inferred to be 1.',
-              },
-              quantity: {
-                type: 'number',
-                description:
-                  'Quantity for the charge. Will be multiplied by unit_price to determine the amount and must be specified with unit_price. If specified amount cannot be provided.',
-              },
-              unit_price: {
-                type: 'number',
-                description:
-                  'Unit price for the charge. Will be multiplied by quantity to determine the amount and must be specified with quantity. If specified amount cannot be provided.',
-              },
-            },
-            required: ['amount_distribution', 'ending_before', 'frequency', 'starting_at'],
-          },
-          schedule_items: {
-            type: 'array',
-            description: 'Either provide amount or provide both unit_price and quantity.',
-            items: {
-              type: 'object',
-              properties: {
-                timestamp: {
-                  type: 'string',
-                  description: 'timestamp of the scheduled event',
-                  format: 'date-time',
-                },
-                amount: {
-                  type: 'number',
-                  description:
-                    'Amount for the charge. Can be provided instead of unit_price and quantity. If amount is sent, the unit_price is assumed to be the amount and quantity is inferred to be 1.',
-                },
-                quantity: {
-                  type: 'number',
-                  description:
-                    'Quantity for the charge. Will be multiplied by unit_price to determine the amount and must be specified with unit_price. If specified amount cannot be provided.',
-                },
-                unit_price: {
-                  type: 'number',
-                  description:
-                    'Unit price for the charge. Will be multiplied by quantity to determine the amount and must be specified with quantity. If specified amount cannot be provided.',
-                },
-              },
-              required: ['timestamp'],
-            },
-          },
-        },
-      },
-      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.',
-      },
-    },
-    required: ['access_schedule', 'customer_id', 'priority', 'product_id', 'type'],
-    $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 body = args as any;
-  return asTextContentResult(await client.v1.customers.commits.create(body));
-};
-
-export default { metadata, tool, handler };

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

@@ -1,83 +0,0 @@
-// File generated from our OpenAPI spec by Stainless. See CONTRIBUTING.md for details.
-
-import { Metadata, asTextContentResult } from '@metronome/mcp/tools/types';
-
-import { Tool } from '@modelcontextprotocol/sdk/types.js';
-import Metronome from '@metronome/sdk';
-
-export const metadata: Metadata = {
-  resource: 'v1.customers.commits',
-  operation: 'write',
-  tags: [],
-  httpMethod: 'post',
-  httpPath: '/v1/contracts/customerCommits/list',
-  operationId: 'listCustomerCommits-v1',
-};
-
-export const tool: Tool = {
-  name: 'list_customers_v1_commits',
-  description:
-    "Retrieve all commit agreements for a customer, including both prepaid and postpaid commitments. This endpoint provides comprehensive visibility into contractual spending obligations, enabling you to track commitment utilization and manage customer contracts effectively.\n\n### Use this endpoint to:\n- Display commitment balances and utilization in customer dashboards\n- Track prepaid commitment drawdown and remaining balances\n- Monitor postpaid commitment progress toward minimum thresholds\n- Build commitment tracking and forecasting tools\n- Show commitment history with optional ledger details\n- Manage rollover balances between contract periods\n\n### Key response fields:\nAn array of Commit objects containing:\n- Commit type: PREPAID (pay upfront) or POSTPAID (pay at true-up)\n- Rate type: COMMIT_RATE (discounted) or LIST_RATE (standard pricing)\n- Access schedule: When commitment funds become available\n- Invoice schedule: When the customer is billed\n- Product targeting: Which product(s) usage is eligible to draw from this commit\n- Optional ledger entries: Transaction history (if `include_ledgers=true`)\n- Balance information: Current available amount (if `include_balance=true`)\n- Rollover settings: Fraction of unused amount that carries forward\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`: Commits active on a specific date\n    - `starting_at`: Commits with access on/after a date\n    - `effective_before`: Commits with access before a date (exclusive)\n- Scope options:\n    - `include_contract_commits`: Include contract-level commits (not just customer-level)\n    - `include_archived`: Include archived commits and commits 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 commit_id to retrieve a specific commit\n",
-  inputSchema: {
-    type: 'object',
-    properties: {
-      customer_id: {
-        type: 'string',
-      },
-      commit_id: {
-        type: 'string',
-      },
-      covering_date: {
-        type: 'string',
-        description: 'Include only commits that have access schedules that "cover" the provided date',
-        format: 'date-time',
-      },
-      effective_before: {
-        type: 'string',
-        description: 'Include only commits that have any access before the provided date (exclusive)',
-        format: 'date-time',
-      },
-      include_archived: {
-        type: 'boolean',
-        description: 'Include archived commits and commits 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_commits: {
-        type: 'boolean',
-        description: 'Include commits on the contract level.',
-      },
-      include_ledgers: {
-        type: 'boolean',
-        description:
-          'Include commit 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 commits 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.commits.list(body).asResponse();
-  return asTextContentResult(await response.json());
-};
-
-export default { metadata, tool, handler };

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

@@ -1,64 +0,0 @@
-// 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.commits',
-  operation: 'write',
-  tags: [],
-  httpMethod: 'post',
-  httpPath: '/v1/contracts/customerCommits/updateEndDate',
-  operationId: 'updateCommitEndDate-v1',
-};
-
-export const tool: Tool = {
-  name: 'update_end_date_customers_v1_commits',
-  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 a prepaid commit to terminate it earlier than originally scheduled. Use this endpoint when you need to cancel or reduce the duration of an existing prepaid commit. Only works with prepaid commit types and can only move the end date forward (earlier), not extend it. \n\n### Usage guidelines:\nTo extend commit end dates or make other comprehensive edits, use the 'edit commit' endpoint instead.\n\n\n# Response Schema\n```json\n{\n  $ref: '#/$defs/commit_update_end_date_response',\n  $defs: {\n    commit_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: {
-      commit_id: {
-        type: 'string',
-        description: 'ID of the commit to update. Only supports "PREPAID" commits.',
-      },
-      customer_id: {
-        type: 'string',
-        description: 'ID of the customer whose commit is to be updated',
-      },
-      access_ending_before: {
-        type: 'string',
-        description:
-          'RFC 3339 timestamp indicating when access to the commit will end and it will no longer be possible to draw it down (exclusive). If not provided, the access will not be updated.',
-        format: 'date-time',
-      },
-      invoices_ending_before: {
-        type: 'string',
-        description:
-          'RFC 3339 timestamp indicating when the commit will stop being invoiced (exclusive). If not provided, the invoice schedule will not be updated.',
-        format: 'date-time',
-      },
-      jq_filter: {
-        type: 'string',
-        title: 'jq Filter',
-        description:
-          'A jq filter to apply to the response to include certain fields. Consult the output schema in the tool description to see the fields that are available.\n\nFor example: to include only the `name` field in every object of a results array, you can provide ".results[].name".\n\nFor more information, see the [jq documentation](https://jqlang.org/manual/).',
-      },
-    },
-    required: ['commit_id', '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.commits.updateEndDate(body)),
-  );
-};
-
-export default { metadata, tool, handler };

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

@@ -1,171 +0,0 @@
-// 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/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_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'],
-        },
-      },
-      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;
-  return asTextContentResult(await maybeFilter(jq_filter, await client.v1.customers.create(body)));
-};
-
-export default { metadata, tool, handler };