@metronome/mcp 2.2.0 → 3.4.1

package/src/tools/v1/custom-fields/delete-values-v1-custom-fields.ts

@@ -1,68 +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.custom_fields',
-  operation: 'write',
-  tags: [],
-  httpMethod: 'post',
-  httpPath: '/v1/customFields/deleteValues',
-  operationId: 'deleteCustomFields-v1',
-};
-
-export const tool: Tool = {
-  name: 'delete_values_v1_custom_fields',
-  description:
-    'Remove specific custom field values from a Metronome entity instance by specifying the field keys to delete. Use this endpoint to clean up unwanted custom field data while preserving other fields on the same entity. Requires the entity type, entity ID, and array of keys to remove.\n',
-  inputSchema: {
-    type: 'object',
-    properties: {
-      entity: {
-        type: 'string',
-        enum: [
-          'alert',
-          'billable_metric',
-          'charge',
-          'commit',
-          'contract_credit',
-          'contract_product',
-          'contract',
-          'credit_grant',
-          'customer_plan',
-          'customer',
-          'discount',
-          'invoice',
-          'plan',
-          'professional_service',
-          'product',
-          'rate_card',
-          'scheduled_charge',
-          'subscription',
-        ],
-      },
-      entity_id: {
-        type: 'string',
-      },
-      keys: {
-        type: 'array',
-        items: {
-          type: 'string',
-        },
-      },
-    },
-    required: ['entity', 'entity_id', 'keys'],
-  },
-  annotations: {},
-};
-
-export const handler = async (client: Metronome, args: Record<string, unknown> | undefined) => {
-  const body = args as any;
-  const response = await client.v1.customFields.deleteValues(body).asResponse();
-  return asTextContentResult(await response.text());
-};
-
-export default { metadata, tool, handler };

package/src/tools/v1/custom-fields/list-keys-v1-custom-fields.ts

@@ -1,81 +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.custom_fields',
-  operation: 'write',
-  tags: [],
-  httpMethod: 'post',
-  httpPath: '/v1/customFields/listKeys',
-  operationId: 'listCustomFieldKeys-v1',
-};
-
-export const tool: Tool = {
-  name: 'list_keys_v1_custom_fields',
-  description:
-    "When using this tool, always use the `jq_filter` parameter to reduce the response size and improve performance.\n\nOnly omit if you're sure you don't need the data.\n\nRetrieve all your active custom field keys, with optional filtering by entity type (customer, contract, product, etc.). Use this endpoint to discover what custom field keys are available before setting values on entities or to audit your custom field configuration across different entity types.\n\n\n# Response Schema\n```json\n{\n  type: 'object',\n  properties: {\n    data: {\n      type: 'array',\n      items: {\n        $ref: '#/$defs/custom_field_list_keys_response'\n      }\n    },\n    next_page: {\n      type: 'string'\n    }\n  },\n  required: [    'data',\n    'next_page'\n  ],\n  $defs: {\n    custom_field_list_keys_response: {\n      type: 'object',\n      properties: {\n        enforce_uniqueness: {\n          type: 'boolean'\n        },\n        entity: {\n          type: 'string',\n          enum: [            'alert',\n            'billable_metric',\n            'charge',\n            'commit',\n            'contract_credit',\n            'contract_product',\n            'contract',\n            'credit_grant',\n            'customer_plan',\n            'customer',\n            'discount',\n            'invoice',\n            'plan',\n            'professional_service',\n            'product',\n            'rate_card',\n            'scheduled_charge',\n            'subscription'\n          ]\n        },\n        key: {\n          type: 'string'\n        }\n      },\n      required: [        'enforce_uniqueness',\n        'entity',\n        'key'\n      ]\n    }\n  }\n}\n```",
-  inputSchema: {
-    type: 'object',
-    properties: {
-      next_page: {
-        type: 'string',
-        description: 'Cursor that indicates where the next page of results should start.',
-      },
-      entities: {
-        type: 'array',
-        description: 'Optional list of entity types to return keys for',
-        items: {
-          type: 'string',
-          enum: [
-            'alert',
-            'billable_metric',
-            'charge',
-            'commit',
-            'contract_credit',
-            'contract_product',
-            'contract',
-            'credit_grant',
-            'customer_plan',
-            'customer',
-            'discount',
-            'invoice',
-            'plan',
-            'professional_service',
-            'product',
-            'rate_card',
-            'scheduled_charge',
-            'subscription',
-          ],
-        },
-      },
-      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: [],
-  },
-  annotations: {},
-};
-
-export const handler = async (client: Metronome, args: Record<string, unknown> | undefined) => {
-  const { jq_filter, ...body } = args as any;
-  const response = await client.v1.customFields.listKeys(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/custom-fields/remove-key-v1-custom-fields.ts

@@ -1,62 +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.custom_fields',
-  operation: 'write',
-  tags: [],
-  httpMethod: 'post',
-  httpPath: '/v1/customFields/removeKey',
-  operationId: 'disableCustomFieldKey-v1',
-};
-
-export const tool: Tool = {
-  name: 'remove_key_v1_custom_fields',
-  description:
-    'Removes a custom field key from the allowlist for a specific entity type, preventing future use of that key across all instances of the entity. Existing values for this key on entity instances will no longer be accessible once the key is removed.\n',
-  inputSchema: {
-    type: 'object',
-    properties: {
-      entity: {
-        type: 'string',
-        enum: [
-          'alert',
-          'billable_metric',
-          'charge',
-          'commit',
-          'contract_credit',
-          'contract_product',
-          'contract',
-          'credit_grant',
-          'customer_plan',
-          'customer',
-          'discount',
-          'invoice',
-          'plan',
-          'professional_service',
-          'product',
-          'rate_card',
-          'scheduled_charge',
-          'subscription',
-        ],
-      },
-      key: {
-        type: 'string',
-      },
-    },
-    required: ['entity', 'key'],
-  },
-  annotations: {},
-};
-
-export const handler = async (client: Metronome, args: Record<string, unknown> | undefined) => {
-  const body = args as any;
-  const response = await client.v1.customFields.removeKey(body).asResponse();
-  return asTextContentResult(await response.text());
-};
-
-export default { metadata, tool, handler };

package/src/tools/v1/custom-fields/set-values-v1-custom-fields.ts

@@ -1,67 +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.custom_fields',
-  operation: 'write',
-  tags: [],
-  httpMethod: 'post',
-  httpPath: '/v1/customFields/setValues',
-  operationId: 'setCustomFields-v1',
-};
-
-export const tool: Tool = {
-  name: 'set_values_v1_custom_fields',
-  description:
-    'Sets custom field values on a specific Metronome entity instance. Overwrites existing values for matching keys while preserving other fields. All updates are transactional—either all values are set or none are. Custom field values are limited to 200 characters each.\n',
-  inputSchema: {
-    type: 'object',
-    properties: {
-      custom_fields: {
-        type: 'object',
-        description: 'Custom fields to be added eg. { "key1": "value1", "key2": "value2" }',
-        additionalProperties: true,
-      },
-      entity: {
-        type: 'string',
-        enum: [
-          'alert',
-          'billable_metric',
-          'charge',
-          'commit',
-          'contract_credit',
-          'contract_product',
-          'contract',
-          'credit_grant',
-          'customer_plan',
-          'customer',
-          'discount',
-          'invoice',
-          'plan',
-          'professional_service',
-          'product',
-          'rate_card',
-          'scheduled_charge',
-          'subscription',
-        ],
-      },
-      entity_id: {
-        type: 'string',
-      },
-    },
-    required: ['custom_fields', 'entity', 'entity_id'],
-  },
-  annotations: {},
-};
-
-export const handler = async (client: Metronome, args: Record<string, unknown> | undefined) => {
-  const body = args as any;
-  const response = await client.v1.customFields.setValues(body).asResponse();
-  return asTextContentResult(await response.text());
-};
-
-export default { metadata, tool, handler };

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

@@ -1,67 +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.alerts',
-  operation: 'write',
-  tags: [],
-  httpMethod: 'post',
-  httpPath: '/v1/customer-alerts/list',
-  operationId: 'listCustomerAlerts-v1',
-};
-
-export const tool: Tool = {
-  name: 'list_customers_v1_alerts',
-  description:
-    "When using this tool, always use the `jq_filter` parameter to reduce the response size and improve performance.\n\nOnly omit if you're sure you don't need the data.\n\nRetrieve all threshold notification configurations and their current statuses for a specific customer in a single API call. This endpoint provides a comprehensive view of all threshold notification monitoring a customer account.\n\n### Use this endpoint to:\n- Display all active threshold notifications for a customer in dashboards or admin panels\n- Quickly identify which threshold notifications a customer is currently triggering\n- Audit threshold notification coverage for specific accounts\n- Filter threshold notifications by status (enabled, disabled, or archived)\n\n### Key response fields:\n- data: Array of CustomerAlert objects, each containing:\n  - Current evaluation status (`ok`, `in_alarm`, `evaluating`, or `null`)\n  - Complete threshold notification configuration and threshold details\n  - Threshold notification metadata including type, name, and last update time\n- next_page: Pagination cursor for retrieving additional results\n\n### Usage guidelines:\n- Default behavior: Returns only enabled threshold notifications unless `alert_statuses` filter is specified\n- Pagination: Use the `next_page` cursor to retrieve all results for customers with many notifications\n- Performance: Efficiently retrieves multiple threshold notification statuses in a single request instead of making individual calls\n- Filtering: Pass the `alert_statuses` array to include disabled or archived threshold notifications in results\n\n\n# Response Schema\n```json\n{\n  type: 'object',\n  properties: {\n    data: {\n      type: 'array',\n      items: {\n        $ref: '#/$defs/customer_alert'\n      }\n    },\n    next_page: {\n      type: 'string'\n    }\n  },\n  required: [    'data',\n    'next_page'\n  ],\n  $defs: {\n    customer_alert: {\n      type: 'object',\n      properties: {\n        alert: {\n          type: 'object',\n          properties: {\n            id: {\n              type: 'string',\n              description: 'the Metronome ID of the threshold notification'\n            },\n            name: {\n              type: 'string',\n              description: 'Name of the threshold notification'\n            },\n            status: {\n              type: 'string',\n              description: 'Status of the threshold notification',\n              enum: [                'enabled',\n                'archived',\n                'disabled'\n              ]\n            },\n            threshold: {\n              type: 'number',\n              description: 'Threshold value of the notification policy'\n            },\n            type: {\n              type: 'string',\n              description: 'Type of the threshold notification',\n              enum: [                'low_credit_balance_reached',\n                'spend_threshold_reached',\n                'monthly_invoice_total_spend_threshold_reached',\n                'low_remaining_days_in_plan_reached',\n                'low_remaining_credit_percentage_reached',\n                'usage_threshold_reached',\n                'low_remaining_days_for_commit_segment_reached',\n                'low_remaining_commit_balance_reached',\n                'low_remaining_commit_percentage_reached',\n                'low_remaining_days_for_contract_credit_segment_reached',\n                'low_remaining_contract_credit_balance_reached',\n                'low_remaining_contract_credit_percentage_reached',\n                'low_remaining_contract_credit_and_commit_balance_reached',\n                'low_remaining_seat_balance_reached',\n                'invoice_total_reached'\n              ]\n            },\n            updated_at: {\n              type: 'string',\n              description: 'Timestamp for when the threshold notification was last updated',\n              format: 'date-time'\n            },\n            credit_grant_type_filters: {\n              type: 'array',\n              description: 'An array of strings, representing a way to filter the credit grant this threshold notification applies to, by looking at the credit_grant_type field on the credit grant. This field is only defined for CreditPercentage and CreditBalance notifications',\n              items: {\n                type: 'string'\n              }\n            },\n            credit_type: {\n              $ref: '#/$defs/credit_type_data'\n            },\n            custom_field_filters: {\n              type: 'array',\n              description: 'A list of custom field filters for notification types that support advanced filtering',\n              items: {\n                type: 'object',\n                properties: {\n                  entity: {\n                    type: 'string',\n                    enum: [                      'Contract',\n                      'Commit',\n                      'ContractCredit'\n                    ]\n                  },\n                  key: {\n                    type: 'string'\n                  },\n                  value: {\n                    type: 'string'\n                  }\n                },\n                required: [                  'entity',\n                  'key',\n                  'value'\n                ]\n              }\n            },\n            group_key_filter: {\n              type: 'object',\n              description: 'Scopes threshold notification evaluation to a specific presentation group key on individual line items. Only present for spend notifications.',\n              properties: {\n                key: {\n                  type: 'string'\n                },\n                value: {\n                  type: 'string'\n                }\n              },\n              required: [                'key',\n                'value'\n              ]\n            },\n            group_values: {\n              type: 'array',\n              description: 'Only present for `spend_threshold_reached` notifications. Scope notification to a specific group key on individual line items.',\n              items: {\n                type: 'object',\n                properties: {\n                  key: {\n                    type: 'string'\n                  },\n                  value: {\n                    type: 'string'\n                  }\n                },\n                required: [                  'key'\n                ]\n              }\n            },\n            invoice_types_filter: {\n              type: 'array',\n              description: 'Only supported for invoice_total_reached threshold notifications. A list of invoice types to evaluate.',\n              items: {\n                type: 'string'\n              }\n            },\n            seat_filter: {\n              type: 'object',\n              description: 'Only present for low_remaining_seat_balance_reached notifications. The seat group key or seat group key-value pair the alert is scoped to.',\n              properties: {\n                seat_group_key: {\n                  type: 'string',\n                  description: 'The seat group key (e.g., \"seat_id\", \"user_id\") that the alert is scoped to.'\n                },\n                seat_group_value: {\n                  type: 'string',\n                  description: 'The seat group value that the alert is scoped to.'\n                }\n              },\n              required: [                'seat_group_key'\n              ]\n            },\n            uniqueness_key: {\n              type: 'string',\n              description: 'Prevents the creation of duplicates. If a request to create a record is made with a previously used uniqueness key, a new record will not be created and the request will fail with a 409 error.'\n            }\n          },\n          required: [            'id',\n            'name',\n            'status',\n            'threshold',\n            'type',\n            'updated_at'\n          ]\n        },\n        customer_status: {\n          type: 'string',\n          description: 'The status of the threshold notification. If the notification is archived, null will be returned.',\n          enum: [            'ok',\n            'in_alarm',\n            'evaluating'\n          ]\n        },\n        triggered_by: {\n          type: 'string',\n          description: 'If present, indicates the reason the threshold notification was triggered.'\n        }\n      },\n      required: [        'alert',\n        'customer_status'\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',
-        description: 'The Metronome ID of the customer',
-      },
-      next_page: {
-        type: 'string',
-        description: 'Cursor that indicates where the next page of results should start.',
-      },
-      alert_statuses: {
-        type: 'array',
-        description:
-          'Optionally filter by threshold notification status. If absent, only enabled notifications will be returned.',
-        items: {
-          type: 'string',
-          enum: ['ENABLED', 'DISABLED', 'ARCHIVED'],
-        },
-      },
-      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;
-  const response = await client.v1.customers.alerts.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/alerts/reset-customers-v1-alerts.ts

@@ -1,44 +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.alerts',
-  operation: 'write',
-  tags: [],
-  httpMethod: 'post',
-  httpPath: '/v1/customer-alerts/reset',
-  operationId: 'resetCustomerAlerts-v1',
-};
-
-export const tool: Tool = {
-  name: 'reset_customers_v1_alerts',
-  description:
-    'Force an immediate re-evaluation of a specific threshold notification for a customer, clearing any previous state and triggering a fresh assessment against current thresholds. This endpoint ensures threshold notification accuracy after configuration changes or data corrections.\n\n### Use this endpoint to:\n- Clear false positive threshold notifications after fixing data issues\n- Re-evaluate threshold notifications after adjusting customer balances or credits\n- Test threshold notification behavior during development and debugging\n- Resolve stuck threshold notification that may be in an incorrect state\n- Trigger immediate evaluation after threshold modifications\n\n### Key response fields: \n- 200 Success: Confirmation that the threshold notification has been reset and re-evaluation initiated\n- No response body is returned - the operation completes asynchronously\n\n### Usage guidelines:\n- Immediate effect: Triggers re-evaluation instantly, which may result in new webhook notifications if thresholds are breached\n- State clearing: Removes any cached evaluation state, ensuring a fresh assessment\n- Use sparingly: Intended for exceptional cases, not routine operations\n- Asynchronous processing: The reset completes immediately, but re-evaluation happens in the background\n',
-  inputSchema: {
-    type: 'object',
-    properties: {
-      alert_id: {
-        type: 'string',
-        description: 'The Metronome ID of the threshold notification',
-      },
-      customer_id: {
-        type: 'string',
-        description: 'The Metronome ID of the customer',
-      },
-    },
-    required: ['alert_id', '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.alerts.reset(body).asResponse();
-  return asTextContentResult(await response.text());
-};
-
-export default { metadata, tool, handler };

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

@@ -1,91 +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.alerts',
-  operation: 'write',
-  tags: [],
-  httpMethod: 'post',
-  httpPath: '/v1/customer-alerts/get',
-  operationId: 'getCustomerAlert-v1',
-};
-
-export const tool: Tool = {
-  name: 'retrieve_customers_v1_alerts',
-  description:
-    "Retrieve the real-time evaluation status for a specific threshold notification-customer pair. This endpoint provides instant visibility into whether a customer has triggered a threshold notification condition, enabling you to monitor account health and take proactive action based on current threshold notification states.\n\n### Use this endpoint to:\n- Check if a specific customer is currently violating an threshold notification (`in_alarm` status)\n- Verify threshold notification configuration details and threshold values for a customer\n- Monitor the evaluation state of newly created or recently modified threshold notification\n- Build dashboards or automated workflows that respond to specific threshold notification conditions\n- Validate threshold notification behavior before deploying to production customers\n- Integrate threshold notification status checks into customer support tools or admin interfaces\n\n### Key response fields: \nA CustomerAlert object containing:\n\n- `customer_status`: The current evaluation state\n\n- `ok` - Customer is within acceptable thresholds\n- `in_alarm` - Customer has breached the threshold for the notification\n- `evaluating` - Notification is currently being evaluated (typically during initial setup)\n- `null` - Notification has been archived\n- `triggered_by`: Additional context about what caused the notification to trigger (when applicable)\n- alert: Complete threshold notification configuration including:\n  - Notification ID, name, and type\n  - Current threshold values and credit type information\n  - Notification status (enabled, disabled, or archived)\n  - Last update timestamp\n  - Any applied filters (credit grant types, custom fields, group values)\n\n### Usage guidelines:\n- Customer status: Returns the current evaluation state, not historical data. For threshold notification history, use webhook notifications or event logs\n- Required parameters: Both customer_id and alert_id must be valid UUIDs that exist in your organization\n- Archived notifications: Returns null for customer_status if the notification has been archived, but still includes the notification configuration details\n- Performance considerations: This endpoint queries live evaluation state, making it ideal for real-time monitoring but not for bulk status checks\n- Integration patterns: Best used for on-demand status checks in response to user actions or as part of targeted monitoring workflows\n- Error handling: Returns 404 if either the customer or alert_id doesn't exist or isn't accessible to your organization\n",
-  inputSchema: {
-    type: 'object',
-    properties: {
-      alert_id: {
-        type: 'string',
-        description: 'The Metronome ID of the threshold notification',
-      },
-      customer_id: {
-        type: 'string',
-        description: 'The Metronome ID of the customer',
-      },
-      group_values: {
-        type: 'array',
-        description:
-          'Only present for `spend_threshold_reached` notifications. Retrieve the notification for a specific group key-value pair.',
-        items: {
-          type: 'object',
-          description:
-            'Scopes threshold notification evaluation to a specific presentation group key on individual line items. Only present for spend notifications.',
-          properties: {
-            key: {
-              type: 'string',
-            },
-            value: {
-              type: 'string',
-            },
-          },
-          required: ['key', 'value'],
-        },
-      },
-      plans_or_contracts: {
-        type: 'string',
-        description:
-          'When parallel threshold notifications are enabled during migration, this flag denotes whether to fetch notifications for plans or contracts.',
-        enum: ['PLANS', 'CONTRACTS'],
-      },
-      seat_filter: {
-        type: 'object',
-        description:
-          'Only allowed for `low_remaining_seat_balance_reached` notifications. This filters alerts by the seat group key-value pair.',
-        properties: {
-          seat_group_key: {
-            type: 'string',
-            description: 'The seat group key (e.g., "seat_id", "user_id")',
-          },
-          seat_group_value: {
-            type: 'string',
-            description: 'The specific seat identifier to filter by',
-          },
-        },
-        required: ['seat_group_key', 'seat_group_value'],
-      },
-    },
-    required: ['alert_id', 'customer_id'],
-  },
-  annotations: {},
-};
-
-export const handler = async (client: Metronome, args: Record<string, unknown> | undefined) => {
-  const body = args as any;
-  try {
-    return asTextContentResult(await client.v1.customers.alerts.retrieve(body));
-  } catch (error) {
-    if (error instanceof Metronome.APIError) {
-      return asErrorResult(error.message);
-    }
-    throw error;
-  }
-};
-
-export default { metadata, tool, handler };

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

@@ -1,52 +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/archive',
-  operationId: 'archiveCustomer-v1',
-};
-
-export const tool: Tool = {
-  name: 'archive_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\nUse this endpoint to archive a customer while preserving auditability. Archiving a customer will automatically archive all contracts as of the current date and void all corresponding invoices. Use this endpoint if a customer is onboarded by mistake.\n\n### Usage guidelines:\n- Once a customer is archived, it cannot be unarchived.\n- Archived customers can still be viewed through the API or the UI for audit purposes. \n- Ingest aliases remain idempotent for archived customers. In order to reuse an ingest alias, first remove the ingest alias from the customer prior to archiving.\n- Any notifications associated with the customer will no longer be triggered.\n\n\n# Response Schema\n```json\n{\n  $ref: '#/$defs/customer_archive_response',\n  $defs: {\n    customer_archive_response: {\n      type: 'object',\n      properties: {\n        data: {\n          $ref: '#/$defs/id'\n        }\n      },\n      required: [        'data'\n      ]\n    },\n    id: {\n      type: 'object',\n      properties: {\n        id: {\n          type: 'string'\n        }\n      },\n      required: [        'id'\n      ]\n    }\n  }\n}\n```",
-  inputSchema: {
-    type: 'object',
-    properties: {
-      id: {
-        type: 'string',
-      },
-      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: ['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.archive(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/billing-config/create-customers-v1-billing-config.ts

@@ -1,108 +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.billing_config',
-  operation: 'write',
-  tags: [],
-  httpMethod: 'post',
-  httpPath: '/v1/customers/{customer_id}/billing-config/{billing_provider_type}',
-  operationId: 'setBillingConfigForCustomer-v1',
-};
-
-export const tool: Tool = {
-  name: 'create_customers_v1_billing_config',
-  description:
-    'Set the billing configuration for a given customer. This is a Plans (deprecated) endpoint. New clients should implement using Contracts.\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',
-        ],
-      },
-      billing_provider_customer_id: {
-        type: 'string',
-        description:
-          "The customer ID in the billing provider's system. For Azure, this is the subscription ID.",
-      },
-      aws_customer_account_id: {
-        type: 'string',
-      },
-      aws_customer_id: {
-        type: 'string',
-      },
-      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: ['customer_id', 'billing_provider_type', 'billing_provider_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.billingConfig.create(body).asResponse();
-  return asTextContentResult(await response.text());
-};
-
-export default { metadata, tool, handler };