@metronome/mcp 2.1.0 → 3.0.0

package/src/tools/v1/customers/list-billable-metrics-v1-customers.ts

@@ -1,65 +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: 'read',
-  tags: [],
-  httpMethod: 'get',
-  httpPath: '/v1/customers/{customer_id}/billable-metrics',
-  operationId: 'listBillableMetrics-v1',
-};
-
-export const tool: Tool = {
-  name: 'list_billable_metrics_v1_customers',
-  description:
-    "When using this tool, always use the `jq_filter` parameter to reduce the response size and improve performance.\n\nOnly omit if you're sure you don't need the data.\n\nGet all billable metrics available for a specific customer. Supports pagination and filtering by current plan status or archived metrics. Use this endpoint to see which metrics are being tracked for billing calculations for a given customer.\n\n\n# Response Schema\n```json\n{\n  type: 'object',\n  properties: {\n    data: {\n      type: 'array',\n      items: {\n        $ref: '#/$defs/customer_list_billable_metrics_response'\n      }\n    },\n    next_page: {\n      type: 'string'\n    }\n  },\n  required: [    'data',\n    'next_page'\n  ],\n  $defs: {\n    customer_list_billable_metrics_response: {\n      type: 'object',\n      properties: {\n        id: {\n          type: 'string'\n        },\n        name: {\n          type: 'string'\n        },\n        aggregate: {\n          type: 'string',\n          description: '(DEPRECATED) use aggregation_type instead'\n        },\n        aggregate_keys: {\n          type: 'array',\n          description: '(DEPRECATED) use aggregation_key instead',\n          items: {\n            type: 'string'\n          }\n        },\n        aggregation_key: {\n          type: 'string',\n          description: 'A key that specifies which property of the event is used to aggregate data. This key must be one of the property filter names and is not applicable when the aggregation type is \\'count\\'.'\n        },\n        aggregation_type: {\n          type: 'string',\n          description: 'Specifies the type of aggregation performed on matching events.',\n          enum: [            'COUNT',\n            'LATEST',\n            'MAX',\n            'SUM',\n            'UNIQUE'\n          ]\n        },\n        archived_at: {\n          type: 'string',\n          description: 'RFC 3339 timestamp indicating when the billable metric was archived. If not provided, the billable metric is not archived.',\n          format: 'date-time'\n        },\n        custom_fields: {\n          type: 'object',\n          description: 'Custom fields to be added eg. { \"key1\": \"value1\", \"key2\": \"value2\" }',\n          additionalProperties: true\n        },\n        event_type_filter: {\n          $ref: '#/$defs/event_type_filter'\n        },\n        filter: {\n          type: 'object',\n          description: '(DEPRECATED) use property_filters & event_type_filter instead',\n          additionalProperties: true\n        },\n        group_by: {\n          type: 'array',\n          description: '(DEPRECATED) use group_keys instead',\n          items: {\n            type: 'string',\n            description: 'A list of keys that can be used to additionally segment the values of the billable metric when making usage queries'\n          }\n        },\n        group_keys: {\n          type: 'array',\n          description: 'Property names that are used to group usage costs on an invoice. Each entry represents a set of properties used to slice events into distinct buckets.',\n          items: {\n            type: 'array',\n            items: {\n              type: 'string'\n            }\n          }\n        },\n        property_filters: {\n          type: 'array',\n          description: 'A list of filters to match events to this billable metric. Each filter defines a rule on an event property. All rules must pass for the event to match the billable metric.',\n          items: {\n            $ref: '#/$defs/property_filter'\n          }\n        },\n        sql: {\n          type: 'string',\n          description: 'The SQL query associated with the billable metric'\n        }\n      },\n      required: [        'id',\n        'name'\n      ]\n    },\n    event_type_filter: {\n      type: 'object',\n      description: 'An optional filtering rule to match the \\'event_type\\' property of an event.',\n      properties: {\n        in_values: {\n          type: 'array',\n          description: 'A list of event types that are explicitly included in the billable metric. If specified, only events of these types will match the billable metric. Must be non-empty if present.',\n          items: {\n            type: 'string'\n          }\n        },\n        not_in_values: {\n          type: 'array',\n          description: 'A list of event types that are explicitly excluded from the billable metric. If specified, events of these types will not match the billable metric. Must be non-empty if present.',\n          items: {\n            type: 'string'\n          }\n        }\n      }\n    },\n    property_filter: {\n      type: 'object',\n      properties: {\n        name: {\n          type: 'string',\n          description: 'The name of the event property.'\n        },\n        exists: {\n          type: 'boolean',\n          description: 'Determines whether the property must exist in the event. If true, only events with this property will pass the filter. If false, only events without this property will pass the filter. If null or omitted, the existence of the property is optional.'\n        },\n        in_values: {\n          type: 'array',\n          description: 'Specifies the allowed values for the property to match an event. An event will pass the filter only if its property value is included in this list. If undefined, all property values will pass the filter. Must be non-empty if present.',\n          items: {\n            type: 'string'\n          }\n        },\n        not_in_values: {\n          type: 'array',\n          description: 'Specifies the values that prevent an event from matching the filter. An event will not pass the filter if its property value is included in this list. If null or empty, all property values will pass the filter. Must be non-empty if present.',\n          items: {\n            type: 'string'\n          }\n        }\n      },\n      required: [        'name'\n      ]\n    }\n  }\n}\n```",
-  inputSchema: {
-    type: 'object',
-    properties: {
-      customer_id: {
-        type: 'string',
-      },
-      include_archived: {
-        type: 'boolean',
-        description: 'If true, the list of returned metrics will include archived metrics',
-      },
-      limit: {
-        type: 'integer',
-        description: 'Max number of results that should be returned',
-      },
-      next_page: {
-        type: 'string',
-        description: 'Cursor that indicates where the next page of results should start.',
-      },
-      on_current_plan: {
-        type: 'boolean',
-        description:
-          "If true, the list of metrics will be filtered to just ones that are on the customer's current plan",
-      },
-      jq_filter: {
-        type: 'string',
-        title: 'jq Filter',
-        description:
-          'A jq filter to apply to the response to include certain fields. Consult the output schema in the tool description to see the fields that are available.\n\nFor example: to include only the `name` field in every object of a results array, you can provide ".results[].name".\n\nFor more information, see the [jq documentation](https://jqlang.org/manual/).',
-      },
-    },
-    required: ['customer_id'],
-  },
-  annotations: {
-    readOnlyHint: true,
-  },
-};
-
-export const handler = async (client: Metronome, args: Record<string, unknown> | undefined) => {
-  const { jq_filter, ...body } = args as any;
-  const response = await client.v1.customers.listBillableMetrics(body).asResponse();
-  return asTextContentResult(await maybeFilter(jq_filter, await response.json()));
-};
-
-export default { metadata, tool, handler };

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

@@ -1,66 +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: 'read',
-  tags: [],
-  httpMethod: 'get',
-  httpPath: '/v1/customers/{customer_id}/costs',
-  operationId: 'getCosts-v1',
-};
-
-export const tool: Tool = {
-  name: 'list_costs_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\nFetch daily pending costs for the specified customer, broken down by credit type and line items. Note: this is not supported for customers whose plan includes a UNIQUE-type billable metric. This is a Plans (deprecated) endpoint. New clients should implement using Contracts.\n\n\n# Response Schema\n```json\n{\n  type: 'object',\n  properties: {\n    data: {\n      type: 'array',\n      items: {\n        $ref: '#/$defs/customer_list_costs_response'\n      }\n    },\n    next_page: {\n      type: 'string'\n    }\n  },\n  required: [    'data',\n    'next_page'\n  ],\n  $defs: {\n    customer_list_costs_response: {\n      type: 'object',\n      properties: {\n        credit_types: {\n          type: 'object',\n          additionalProperties: true\n        },\n        end_timestamp: {\n          type: 'string',\n          format: 'date-time'\n        },\n        start_timestamp: {\n          type: 'string',\n          format: 'date-time'\n        }\n      },\n      required: [        'credit_types',\n        'end_timestamp',\n        'start_timestamp'\n      ]\n    }\n  }\n}\n```",
-  inputSchema: {
-    type: 'object',
-    properties: {
-      customer_id: {
-        type: 'string',
-      },
-      ending_before: {
-        type: 'string',
-        description: 'RFC 3339 timestamp (exclusive)',
-        format: 'date-time',
-      },
-      starting_on: {
-        type: 'string',
-        description: 'RFC 3339 timestamp (inclusive)',
-        format: 'date-time',
-      },
-      limit: {
-        type: 'integer',
-        description: 'Max number of results that should be returned',
-      },
-      next_page: {
-        type: 'string',
-        description: 'Cursor that indicates where the next page of results should start.',
-      },
-      jq_filter: {
-        type: 'string',
-        title: 'jq Filter',
-        description:
-          'A jq filter to apply to the response to include certain fields. Consult the output schema in the tool description to see the fields that are available.\n\nFor example: to include only the `name` field in every object of a results array, you can provide ".results[].name".\n\nFor more information, see the [jq documentation](https://jqlang.org/manual/).',
-      },
-    },
-    required: ['customer_id', 'ending_before', 'starting_on'],
-  },
-  annotations: {
-    readOnlyHint: true,
-  },
-};
-
-export const handler = async (client: Metronome, args: Record<string, unknown> | undefined) => {
-  const { jq_filter, ...body } = args as any;
-  const response = await client.v1.customers.listCosts(body).asResponse();
-  return asTextContentResult(await maybeFilter(jq_filter, await response.json()));
-};
-
-export default { metadata, tool, handler };

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

@@ -1,76 +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: 'read',
-  tags: [],
-  httpMethod: 'get',
-  httpPath: '/v1/customers',
-  operationId: 'listCustomers-v1',
-};
-
-export const tool: Tool = {
-  name: 'list_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\nGets a paginated list of all customers in your Metronome account. Use this endpoint to browse your customer base, implement customer search functionality, or sync customer data with external systems. Returns customer details including IDs, names, and configuration settings. Supports filtering and pagination parameters for efficient data retrieval.\n\n\n# Response Schema\n```json\n{\n  type: 'object',\n  properties: {\n    data: {\n      type: 'array',\n      items: {\n        $ref: '#/$defs/customer_detail'\n      }\n    },\n    next_page: {\n      type: 'string'\n    }\n  },\n  required: [    'data',\n    'next_page'\n  ],\n  $defs: {\n    customer_detail: {\n      type: 'object',\n      properties: {\n        id: {\n          type: 'string',\n          description: 'the Metronome ID of the customer'\n        },\n        created_at: {\n          type: 'string',\n          description: 'RFC 3339 timestamp indicating when the customer was created.',\n          format: 'date-time'\n        },\n        custom_fields: {\n          type: 'object',\n          description: 'Custom fields to be added eg. { \"key1\": \"value1\", \"key2\": \"value2\" }',\n          additionalProperties: true\n        },\n        customer_config: {\n          type: 'object',\n          properties: {\n            salesforce_account_id: {\n              type: 'string',\n              description: 'The Salesforce account ID for the customer'\n            }\n          },\n          required: [            'salesforce_account_id'\n          ]\n        },\n        external_id: {\n          type: 'string',\n          description: '(deprecated, use ingest_aliases instead) the first ID (Metronome or ingest alias) that can be used in usage events'\n        },\n        ingest_aliases: {\n          type: 'array',\n          description: 'aliases for this customer that can be used instead of the Metronome customer ID in usage events',\n          items: {\n            type: 'string'\n          }\n        },\n        name: {\n          type: 'string'\n        },\n        updated_at: {\n          type: 'string',\n          description: 'RFC 3339 timestamp indicating when the customer was last updated.',\n          format: 'date-time'\n        },\n        archived_at: {\n          type: 'string',\n          description: 'RFC 3339 timestamp indicating when the customer was archived. Null if the customer is active.',\n          format: 'date-time'\n        },\n        current_billable_status: {\n          type: 'object',\n          description: 'This field\\'s availability is dependent on your client\\'s configuration.',\n          properties: {\n            value: {\n              type: 'string',\n              enum: [                'billable',\n                'unbillable'\n              ]\n            },\n            effective_at: {\n              type: 'string',\n              format: 'date-time'\n            }\n          },\n          required: [            'value'\n          ]\n        }\n      },\n      required: [        'id',\n        'created_at',\n        'custom_fields',\n        'customer_config',\n        'external_id',\n        'ingest_aliases',\n        'name',\n        'updated_at'\n      ]\n    }\n  }\n}\n```",
-  inputSchema: {
-    type: 'object',
-    properties: {
-      customer_ids: {
-        type: 'array',
-        description: 'Filter the customer list by customer_id.  Up to 100 ids can be provided.',
-        items: {
-          type: 'string',
-        },
-      },
-      ingest_alias: {
-        type: 'string',
-        description: 'Filter the customer list by ingest_alias',
-      },
-      limit: {
-        type: 'integer',
-        description: 'Max number of results that should be returned',
-      },
-      next_page: {
-        type: 'string',
-        description: 'Cursor that indicates where the next page of results should start.',
-      },
-      only_archived: {
-        type: 'boolean',
-        description:
-          'Filter the customer list to only return archived customers. By default, only active customers are returned.',
-      },
-      salesforce_account_ids: {
-        type: 'array',
-        description: 'Filter the customer list by salesforce_account_id.  Up to 100 ids can be provided.',
-        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: [],
-  },
-  annotations: {
-    readOnlyHint: true,
-  },
-};
-
-export const handler = async (client: Metronome, args: Record<string, unknown> | undefined) => {
-  const { jq_filter, ...body } = args as any;
-  const response = await client.v1.customers.list(body).asResponse();
-  return asTextContentResult(await maybeFilter(jq_filter, await response.json()));
-};
-
-export default { metadata, tool, handler };

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

@@ -1,58 +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.named_schedules',
-  operation: 'write',
-  tags: [],
-  httpMethod: 'post',
-  httpPath: '/v1/customers/getNamedSchedule',
-  operationId: 'getCustomerNamedSchedule-v1',
-};
-
-export const tool: Tool = {
-  name: 'retrieve_customers_v1_named_schedules',
-  description:
-    "When using this tool, always use the `jq_filter` parameter to reduce the response size and improve performance.\n\nOnly omit if you're sure you don't need the data.\n\nGet a named schedule for the given customer. This endpoint's availability is dependent on your client's configuration.\n\n# Response Schema\n```json\n{\n  $ref: '#/$defs/named_schedule_retrieve_response',\n  $defs: {\n    named_schedule_retrieve_response: {\n      type: 'object',\n      properties: {\n        data: {\n          type: 'array',\n          items: {\n            type: 'object',\n            properties: {\n              starting_at: {\n                type: 'string',\n                format: 'date-time'\n              },\n              value: {\n                type: 'object',\n                additionalProperties: true\n              },\n              ending_before: {\n                type: 'string',\n                format: 'date-time'\n              }\n            },\n            required: [              'starting_at',\n              'value'\n            ]\n          }\n        }\n      },\n      required: [        'data'\n      ]\n    }\n  }\n}\n```",
-  inputSchema: {
-    type: 'object',
-    properties: {
-      customer_id: {
-        type: 'string',
-        description: 'ID of the customer whose named schedule is to be retrieved',
-      },
-      schedule_name: {
-        type: 'string',
-        description: 'The identifier for the schedule to be retrieved',
-      },
-      covering_date: {
-        type: 'string',
-        description:
-          'If provided, at most one schedule segment will be returned (the one that covers this date). If not provided, all segments will be returned.',
-        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: ['customer_id', 'schedule_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.namedSchedules.retrieve(body)),
-  );
-};
-
-export default { metadata, tool, handler };

package/src/tools/v1/customers/named-schedules/update-customers-v1-named-schedules.ts

@@ -1,58 +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.named_schedules',
-  operation: 'write',
-  tags: [],
-  httpMethod: 'post',
-  httpPath: '/v1/customers/updateNamedSchedule',
-  operationId: 'updateCustomerNamedSchedule-v1',
-};
-
-export const tool: Tool = {
-  name: 'update_customers_v1_named_schedules',
-  description:
-    "Update a named schedule for the given customer. This endpoint's availability is dependent on your client's configuration.",
-  inputSchema: {
-    type: 'object',
-    properties: {
-      customer_id: {
-        type: 'string',
-        description: 'ID of the customer whose named schedule is to be updated',
-      },
-      schedule_name: {
-        type: 'string',
-        description: 'The identifier for the schedule to be updated',
-      },
-      starting_at: {
-        type: 'string',
-        format: 'date-time',
-      },
-      value: {
-        type: 'object',
-        description:
-          'The value to set for the named schedule. The structure of this object is specific to the named schedule.',
-        additionalProperties: true,
-      },
-      ending_before: {
-        type: 'string',
-        format: 'date-time',
-      },
-    },
-    required: ['customer_id', 'schedule_name', 'starting_at', 'value'],
-  },
-  annotations: {},
-};
-
-export const handler = async (client: Metronome, args: Record<string, unknown> | undefined) => {
-  const body = args as any;
-  const response = await client.v1.customers.namedSchedules.update(body).asResponse();
-  return asTextContentResult(await response.text());
-};
-
-export default { metadata, tool, handler };

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

@@ -1,148 +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.plans',
-  operation: 'write',
-  tags: [],
-  httpMethod: 'post',
-  httpPath: '/v1/customers/{customer_id}/plans/add',
-  operationId: 'addPlanToCustomer-v1',
-};
-
-export const tool: Tool = {
-  name: 'add_customers_v1_plans',
-  description:
-    "When using this tool, always use the `jq_filter` parameter to reduce the response size and improve performance.\n\nOnly omit if you're sure you don't need the data.\n\nAssociate an existing customer with a plan for a specified date range.  See the [price adjustments documentation](https://plans-docs.metronome.com/pricing/managing-plans/#price-adjustments) for details on the price adjustments. This is a Plans (deprecated) endpoint. New clients should implement using Contracts.\n\n\n# Response Schema\n```json\n{\n  $ref: '#/$defs/plan_add_response',\n  $defs: {\n    plan_add_response: {\n      type: 'object',\n      properties: {\n        data: {\n          $ref: '#/$defs/id'\n        }\n      },\n      required: [        'data'\n      ]\n    },\n    id: {\n      type: 'object',\n      properties: {\n        id: {\n          type: 'string'\n        }\n      },\n      required: [        'id'\n      ]\n    }\n  }\n}\n```",
-  inputSchema: {
-    type: 'object',
-    properties: {
-      customer_id: {
-        type: 'string',
-      },
-      plan_id: {
-        type: 'string',
-      },
-      starting_on: {
-        type: 'string',
-        description:
-          'RFC 3339 timestamp for when the plan becomes active for this customer. Must be at 0:00 UTC (midnight).',
-        format: 'date-time',
-      },
-      ending_before: {
-        type: 'string',
-        description:
-          'RFC 3339 timestamp for when the plan ends (exclusive) for this customer. Must be at 0:00 UTC (midnight).',
-        format: 'date-time',
-      },
-      net_payment_terms_days: {
-        type: 'number',
-        description: 'Number of days after issuance of invoice after which the invoice is due (e.g. Net 30).',
-      },
-      overage_rate_adjustments: {
-        type: 'array',
-        description:
-          'An optional list of overage rates that override the rates of the original plan configuration. These new rates will apply to all pricing ramps.',
-        items: {
-          type: 'object',
-          properties: {
-            custom_credit_type_id: {
-              type: 'string',
-            },
-            fiat_currency_credit_type_id: {
-              type: 'string',
-            },
-            to_fiat_conversion_factor: {
-              type: 'number',
-              description: 'The overage cost in fiat currency for each credit of the custom credit type.',
-            },
-          },
-          required: ['custom_credit_type_id', 'fiat_currency_credit_type_id', 'to_fiat_conversion_factor'],
-        },
-      },
-      price_adjustments: {
-        type: 'array',
-        description:
-          'A list of price adjustments can be applied on top of the pricing in the plans. See the [price adjustments documentation](https://plans-docs.metronome.com/pricing/managing-plans/#price-adjustments) for details.',
-        items: {
-          type: 'object',
-          properties: {
-            adjustment_type: {
-              type: 'string',
-              enum: ['percentage', 'fixed', 'override', 'quantity'],
-            },
-            charge_id: {
-              type: 'string',
-            },
-            start_period: {
-              type: 'number',
-              description:
-                'Used in price ramps.  Indicates how many billing periods pass before the charge applies.',
-            },
-            quantity: {
-              type: 'number',
-              description: 'the overridden quantity for a fixed charge',
-            },
-            tier: {
-              type: 'number',
-              description: 'Used in pricing tiers.  Indicates at what metric value the price applies.',
-            },
-            value: {
-              type: 'number',
-              description:
-                'The amount of change to a price. Percentage and fixed adjustments can be positive or negative. Percentage-based adjustments should be decimals, e.g. -0.05 for a 5% discount.',
-            },
-          },
-          required: ['adjustment_type', 'charge_id', 'start_period'],
-        },
-      },
-      trial_spec: {
-        type: 'object',
-        description:
-          "A custom trial can be set for the customer's plan. See the [trial configuration documentation](https://docs.metronome.com/provisioning/configure-trials/) for details.",
-        properties: {
-          length_in_days: {
-            type: 'number',
-            description: 'Length of the trial period in days.',
-          },
-          spending_cap: {
-            type: 'object',
-            properties: {
-              amount: {
-                type: 'number',
-                description:
-                  'The credit amount in the given denomination based on the credit type, e.g. US cents.',
-              },
-              credit_type_id: {
-                type: 'string',
-                description: 'The credit type ID for the spending cap.',
-              },
-            },
-            required: ['amount', 'credit_type_id'],
-          },
-        },
-        required: ['length_in_days'],
-      },
-      jq_filter: {
-        type: 'string',
-        title: 'jq Filter',
-        description:
-          'A jq filter to apply to the response to include certain fields. Consult the output schema in the tool description to see the fields that are available.\n\nFor example: to include only the `name` field in every object of a results array, you can provide ".results[].name".\n\nFor more information, see the [jq documentation](https://jqlang.org/manual/).',
-      },
-    },
-    required: ['customer_id', 'plan_id', 'starting_on'],
-  },
-  annotations: {},
-};
-
-export const handler = async (client: Metronome, args: Record<string, unknown> | undefined) => {
-  const { jq_filter, ...body } = args as any;
-  return asTextContentResult(await maybeFilter(jq_filter, await client.v1.customers.plans.add(body)));
-};
-
-export default { metadata, tool, handler };

package/src/tools/v1/customers/plans/end-customers-v1-plans.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.plans',
-  operation: 'write',
-  tags: [],
-  httpMethod: 'post',
-  httpPath: '/v1/customers/{customer_id}/plans/{customer_plan_id}/end',
-  operationId: 'endCustomerPlan-v1',
-};
-
-export const tool: Tool = {
-  name: 'end_customers_v1_plans',
-  description:
-    "When using this tool, always use the `jq_filter` parameter to reduce the response size and improve performance.\n\nOnly omit if you're sure you don't need the data.\n\nChange the end date of a customer's plan. This is a Plans (deprecated) endpoint. New clients should implement using Contracts.\n\n\n# Response Schema\n```json\n{\n  $ref: '#/$defs/plan_end_response',\n  $defs: {\n    plan_end_response: {\n      type: 'object',\n      properties: {}\n    }\n  }\n}\n```",
-  inputSchema: {
-    type: 'object',
-    properties: {
-      customer_id: {
-        type: 'string',
-      },
-      customer_plan_id: {
-        type: 'string',
-      },
-      ending_before: {
-        type: 'string',
-        description:
-          'RFC 3339 timestamp for when the plan ends (exclusive) for this customer. Must be at 0:00 UTC (midnight). If not provided, the plan end date will be cleared.',
-        format: 'date-time',
-      },
-      void_invoices: {
-        type: 'boolean',
-        description:
-          'If true, plan end date can be before the last finalized invoice date. Any invoices generated after the plan end date will be voided.',
-      },
-      void_stripe_invoices: {
-        type: 'boolean',
-        description:
-          'Only applicable when void_invoices is set to true. If true, for every invoice that is voided we will also attempt to void/delete the stripe invoice (if any). Stripe invoices will be voided if finalized or deleted if still in draft state.',
-      },
-      jq_filter: {
-        type: 'string',
-        title: 'jq Filter',
-        description:
-          'A jq filter to apply to the response to include certain fields. Consult the output schema in the tool description to see the fields that are available.\n\nFor example: to include only the `name` field in every object of a results array, you can provide ".results[].name".\n\nFor more information, see the [jq documentation](https://jqlang.org/manual/).',
-      },
-    },
-    required: ['customer_id', 'customer_plan_id'],
-  },
-  annotations: {},
-};
-
-export const handler = async (client: Metronome, args: Record<string, unknown> | undefined) => {
-  const { jq_filter, ...body } = args as any;
-  return asTextContentResult(await maybeFilter(jq_filter, await client.v1.customers.plans.end(body)));
-};
-
-export default { metadata, tool, handler };

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

@@ -1,56 +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.plans',
-  operation: 'read',
-  tags: [],
-  httpMethod: 'get',
-  httpPath: '/v1/customers/{customer_id}/plans',
-  operationId: 'listCustomerPlans-v1',
-};
-
-export const tool: Tool = {
-  name: 'list_customers_v1_plans',
-  description:
-    "When using this tool, always use the `jq_filter` parameter to reduce the response size and improve performance.\n\nOnly omit if you're sure you don't need the data.\n\nList the given customer's plans in reverse-chronological order. This is a Plans (deprecated) endpoint. New clients should implement using Contracts.\n\n\n# Response Schema\n```json\n{\n  type: 'object',\n  properties: {\n    data: {\n      type: 'array',\n      items: {\n        $ref: '#/$defs/plan_list_response'\n      }\n    },\n    next_page: {\n      type: 'string'\n    }\n  },\n  required: [    'data',\n    'next_page'\n  ],\n  $defs: {\n    plan_list_response: {\n      type: 'object',\n      properties: {\n        id: {\n          type: 'string',\n          description: 'the ID of the customer plan'\n        },\n        custom_fields: {\n          type: 'object',\n          description: 'Custom fields to be added eg. { \"key1\": \"value1\", \"key2\": \"value2\" }',\n          additionalProperties: true\n        },\n        plan_description: {\n          type: 'string'\n        },\n        plan_id: {\n          type: 'string',\n          description: 'the ID of the plan'\n        },\n        plan_name: {\n          type: 'string'\n        },\n        starting_on: {\n          type: 'string',\n          format: 'date-time'\n        },\n        ending_before: {\n          type: 'string',\n          format: 'date-time'\n        },\n        net_payment_terms_days: {\n          type: 'number'\n        },\n        trial_info: {\n          type: 'object',\n          properties: {\n            ending_before: {\n              type: 'string',\n              format: 'date-time'\n            },\n            spending_caps: {\n              type: 'array',\n              items: {\n                type: 'object',\n                properties: {\n                  amount: {\n                    type: 'number'\n                  },\n                  amount_remaining: {\n                    type: 'number'\n                  },\n                  credit_type: {\n                    $ref: '#/$defs/credit_type_data'\n                  }\n                },\n                required: [                  'amount',\n                  'amount_remaining',\n                  'credit_type'\n                ]\n              }\n            }\n          },\n          required: [            'ending_before',\n            'spending_caps'\n          ]\n        }\n      },\n      required: [        'id',\n        'custom_fields',\n        'plan_description',\n        'plan_id',\n        'plan_name',\n        'starting_on'\n      ]\n    },\n    credit_type_data: {\n      type: 'object',\n      properties: {\n        id: {\n          type: 'string'\n        },\n        name: {\n          type: 'string'\n        }\n      },\n      required: [        'id',\n        'name'\n      ]\n    }\n  }\n}\n```",
-  inputSchema: {
-    type: 'object',
-    properties: {
-      customer_id: {
-        type: 'string',
-      },
-      limit: {
-        type: 'integer',
-        description: 'Max number of results that should be returned',
-      },
-      next_page: {
-        type: 'string',
-        description: 'Cursor that indicates where the next page of results should start.',
-      },
-      jq_filter: {
-        type: 'string',
-        title: 'jq Filter',
-        description:
-          'A jq filter to apply to the response to include certain fields. Consult the output schema in the tool description to see the fields that are available.\n\nFor example: to include only the `name` field in every object of a results array, you can provide ".results[].name".\n\nFor more information, see the [jq documentation](https://jqlang.org/manual/).',
-      },
-    },
-    required: ['customer_id'],
-  },
-  annotations: {
-    readOnlyHint: true,
-  },
-};
-
-export const handler = async (client: Metronome, args: Record<string, unknown> | undefined) => {
-  const { jq_filter, ...body } = args as any;
-  const response = await client.v1.customers.plans.list(body).asResponse();
-  return asTextContentResult(await maybeFilter(jq_filter, await response.json()));
-};
-
-export default { metadata, tool, handler };