@metronome/mcp 2.2.0 → 3.4.1

package/src/tools/v1/settings/upsert-avalara-credentials-v1-settings.ts

@@ -1,77 +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.settings',
-  operation: 'write',
-  tags: [],
-  httpMethod: 'post',
-  httpPath: '/v1/upsertAvalaraCredentials',
-  operationId: 'upsertAvalaraCredentials-v1',
-};
-
-export const tool: Tool = {
-  name: 'upsert_avalara_credentials_v1_settings',
-  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\nSet the Avalara credentials for some specified `delivery_method_ids`, which can be found in the `/listConfiguredBillingProviders` response. This maps the Avalara credentials to the appropriate billing entity. These credentials are only used for PLG Invoicing today.\n\n\n# Response Schema\n```json\n{\n  $ref: '#/$defs/setting_upsert_avalara_credentials_response',\n  $defs: {\n    setting_upsert_avalara_credentials_response: {\n      type: 'object',\n      properties: {}\n    }\n  }\n}\n```",
-  inputSchema: {
-    type: 'object',
-    properties: {
-      avalara_environment: {
-        type: 'string',
-        description: 'The Avalara environment to use (SANDBOX or PRODUCTION).',
-        enum: ['PRODUCTION', 'SANDBOX'],
-      },
-      avalara_password: {
-        type: 'string',
-        description: 'The password for the Avalara account.',
-      },
-      avalara_username: {
-        type: 'string',
-        description: 'The username for the Avalara account.',
-      },
-      delivery_method_ids: {
-        type: 'array',
-        description:
-          'The delivery method IDs of the billing provider configurations to update, can be found in the response of the `/listConfiguredBillingProviders` endpoint.',
-        items: {
-          type: 'string',
-        },
-      },
-      commit_transactions: {
-        type: 'boolean',
-        description:
-          'Commit transactions if you want Metronome tax calculations used for reporting and tax filings.',
-      },
-      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: ['avalara_environment', 'avalara_password', 'avalara_username', 'delivery_method_ids'],
-  },
-  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.settings.upsertAvalaraCredentials(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/usage/ingest-v1-usage.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.usage',
-  operation: 'write',
-  tags: [],
-  httpMethod: 'post',
-  httpPath: '/v1/ingest',
-  operationId: 'ingest-v1',
-};
-
-export const tool: Tool = {
-  name: 'ingest_v1_usage',
-  description:
-    'The ingest endpoint is the primary method for sending usage events to Metronome, serving as the foundation for all billing calculations in your usage-based pricing model. This high-throughput endpoint is designed for real-time streaming ingestion, supports backdating 34 days, and is built to handle mission-critical usage data with enterprise-grade reliability. Metronome supports 100,000 events per second without requiring pre-aggregation or rollups and can scale up from there. See the [Send usage events](/guides/events/send-usage-events) guide to learn more about usage events.\n\n### Use this endpoint to:\nCreate a customer usage pipeline into Metronome that drives billable metrics, credit drawdown, and invoicing. Track customer behavior, resource consumption, and feature usage\n\n### What happens when you send events:\n- Events are validated and processed in real-time\n- Events are matched to customers using customer IDs or customer ingest aliases\n- Events are matched to billable metrics and are immediately available for usage and spend calculations\n\n### Usage guidelines:\n- Historical events can be backdated up to 34 days and will immediately impact live customer spend\n- Duplicate events are automatically detected and ignored (34-day deduplication window)\n\n#### Event structure:\nUsage events are simple JSON objects designed for flexibility and ease of integration:\n```json\n{\n  "transaction_id": "2021-01-01T00:00:00Z_cluster42",\n  "customer_id": "team@example.com",\n  "event_type": "api_request",\n  "timestamp": "2021-01-01T00:00:00Z",\n  "properties": {\n    "endpoint": "/v1/users",\n    "method": "POST",\n    "response_time_ms": 45,\n    "region": "us-west-2"\n  }\n}\n```\n\nLearn more about [usage event structure definitions](/guides/events/design-usage-events).\n\n#### Transaction ID\n  The transaction_id serves as your idempotency key, ensuring events are processed exactly once. Metronome maintains a 34-day deduplication window - significantly longer than typical 12-hour windows - enabling robust backfill scenarios without duplicate billing.\n  - Best Practices:\n    - Use UUIDs for one-time events: uuid4()\n    - For heartbeat events, use deterministic IDs\n    - Include enough context to avoid collisions across different event sources\n\n#### Customer ID\nIdentifies which customer should be billed for this usage. Supports two identification methods:\n  - Metronome Customer ID: The UUID returned when creating a customer\n  - Ingest Alias: Your system\'s identifier (email, account number, etc.) \n\nIngest aliases enable seamless integration without requiring ID mapping, and customers can have multiple aliases for flexibility.\n\n#### Event Type:\nCategorizes the event type for billable metric matching. Choose descriptive names that aligns with the product surface area.\n\n#### Properties:\nFlexible metadata also used to match billable metrics or to be used to serve as group keys to create multiple pricing dimensions or breakdown costs by novel properties for end customers or internal finance teams measuring underlying COGs.\n',
-  inputSchema: {
-    type: 'object',
-    properties: {
-      usage: {
-        type: 'array',
-        items: {
-          type: 'object',
-          properties: {
-            customer_id: {
-              type: 'string',
-            },
-            event_type: {
-              type: 'string',
-            },
-            timestamp: {
-              type: 'string',
-              description: 'RFC 3339 formatted',
-            },
-            transaction_id: {
-              type: 'string',
-            },
-            properties: {
-              type: 'object',
-              additionalProperties: true,
-            },
-          },
-          required: ['customer_id', 'event_type', 'timestamp', 'transaction_id'],
-        },
-      },
-    },
-    required: [],
-  },
-  annotations: {},
-};
-
-export const handler = async (client: Metronome, args: Record<string, unknown> | undefined) => {
-  const body = args as any;
-  const response = await client.v1.usage.ingest(body).asResponse();
-  return asTextContentResult(await response.text());
-};
-
-export default { metadata, tool, handler };

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

@@ -1,108 +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.usage',
-  operation: 'write',
-  tags: [],
-  httpMethod: 'post',
-  httpPath: '/v1/usage',
-  operationId: 'getUsageBatch-v1',
-};
-
-export const tool: Tool = {
-  name: 'list_v1_usage',
-  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 aggregated usage data across multiple customers and billable metrics in a single query. This batch endpoint enables you to fetch usage patterns at scale, broken down by time windows, making it ideal for building analytics dashboards, generating reports, and monitoring platform-wide usage trends.\n\n### Use this endpoint to:\n- Generate platform-wide usage reports for internal teams\n- Monitor aggregate usage trends across your entire customer base\n- Create comparative usage analyses between customers or time periods\n- Support capacity planning with historical usage patterns\n\n### Key response fields:\nAn array of `UsageBatchAggregate` objects containing:\n\n- `customer_id`: The customer this usage belongs to\n- `billable_metric_id` and `billable_metric_name`: What was measured\n- `start_timestamp` and `end_timestamp`: Time window for this data point\n- `value`: Aggregated usage amount for the period\n- `groups` (optional): Usage broken down by group keys with values\n- `next_page`: Pagination cursor for large result sets\n\n### Usage guidelines:\n- Time windows: Set `window_size` to `hour`, `day`, or `none` (entire period)\n- Required parameters: Must specify `starting_on`, `ending_before`, and `window_size`\n- Filtering options:\n  - `customer_ids`: Limit to specific customers (omit for all customers)\n  - `billable_metrics`: Limit to specific metrics (omit for all metrics)\n- Pagination: Use `next_page` cursor to retrieve large datasets\n- Null values: Group values may be null when no usage matches that group\n\n\n# Response Schema\n```json\n{\n  type: 'object',\n  properties: {\n    data: {\n      type: 'array',\n      items: {\n        $ref: '#/$defs/usage_list_response'\n      }\n    },\n    next_page: {\n      type: 'string'\n    }\n  },\n  required: [    'data',\n    'next_page'\n  ],\n  $defs: {\n    usage_list_response: {\n      type: 'object',\n      properties: {\n        billable_metric_id: {\n          type: 'string'\n        },\n        billable_metric_name: {\n          type: 'string'\n        },\n        customer_id: {\n          type: 'string'\n        },\n        end_timestamp: {\n          type: 'string',\n          format: 'date-time'\n        },\n        start_timestamp: {\n          type: 'string',\n          format: 'date-time'\n        },\n        value: {\n          type: 'number'\n        },\n        groups: {\n          type: 'object',\n          description: 'Values will be either a number or null. Null indicates that there were no matches for the group_by value.',\n          additionalProperties: true\n        }\n      },\n      required: [        'billable_metric_id',\n        'billable_metric_name',\n        'customer_id',\n        'end_timestamp',\n        'start_timestamp',\n        'value'\n      ]\n    }\n  }\n}\n```",
-  inputSchema: {
-    type: 'object',
-    properties: {
-      ending_before: {
-        type: 'string',
-        format: 'date-time',
-      },
-      starting_on: {
-        type: 'string',
-        format: 'date-time',
-      },
-      window_size: {
-        type: 'string',
-        description:
-          'A window_size of "day" or "hour" will return the usage for the specified period segmented into daily or hourly aggregates. A window_size of "none" will return a single usage aggregate for the entirety of the specified period.',
-        enum: ['HOUR', 'DAY', 'NONE'],
-      },
-      next_page: {
-        type: 'string',
-        description: 'Cursor that indicates where the next page of results should start.',
-      },
-      billable_metrics: {
-        type: 'array',
-        description:
-          'A list of billable metrics to fetch usage for. If absent, all billable metrics will be returned.',
-        items: {
-          type: 'object',
-          properties: {
-            id: {
-              type: 'string',
-            },
-            group_by: {
-              type: 'object',
-              properties: {
-                key: {
-                  type: 'string',
-                  description: 'The name of the group_by key to use',
-                },
-                values: {
-                  type: 'array',
-                  description:
-                    'Values of the group_by key to return in the query. If this field is omitted, all available values will be returned, up to a maximum of 200.',
-                  items: {
-                    type: 'string',
-                  },
-                },
-              },
-              required: ['key'],
-            },
-          },
-          required: ['id'],
-        },
-      },
-      customer_ids: {
-        type: 'array',
-        description:
-          'A list of Metronome customer IDs to fetch usage for. If absent, usage for all customers will be returned.',
-        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: ['ending_before', 'starting_on', 'window_size'],
-  },
-  annotations: {},
-};
-
-export const handler = async (client: Metronome, args: Record<string, unknown> | undefined) => {
-  const { jq_filter, ...body } = args as any;
-  const response = await client.v1.usage.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/usage/list-with-groups-v1-usage.ts

@@ -1,101 +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.usage',
-  operation: 'write',
-  tags: [],
-  httpMethod: 'post',
-  httpPath: '/v1/usage/groups',
-  operationId: 'getPagedUsage-v1',
-};
-
-export const tool: Tool = {
-  name: 'list_with_groups_v1_usage',
-  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 granular usage data for a specific customer and billable metric, with the ability to break down usage by custom grouping dimensions. This endpoint enables deep usage analytics by segmenting data across attributes like region, user, model type, or any custom dimension defined in your billable metrics.\n\n### Use this endpoint to:\n- Analyze usage patterns broken down by specific attributes (region, user, department, etc.)\n- Build detailed usage dashboards with dimensional filtering\n- Identify high-usage segments for optimization opportunities\n\n### Key response fields:\nAn array of `PagedUsageAggregate` objects containing:\n- `starting_on` and `ending_before`: Time window boundaries\n- `group_key`: The dimension being grouped by (e.g., \"region\")\n- `group_value`: The specific value for this group (e.g., \"US-East\")\n- `value`: Aggregated usage for this group and time window\n- `next_page`: Pagination cursor for large datasets\n\n### Usage guidelines:\n- Required parameters: Must specify `customer_id`, `billable_metric_id`, and `window_size`\n- Time windows: Set `window_size` to hour, day, or none for different granularities\n- Group filtering: Use `group_by` to specify:\n    - key: The dimension to group by (must be set on the billable metric as a group key)\n    - values: Optional array to filter to specific values only\n- Pagination: Use limit and `next_page` for large result sets\n- Null handling: `group_value` may be null for unmatched data\n\n\n# Response Schema\n```json\n{\n  type: 'object',\n  properties: {\n    data: {\n      type: 'array',\n      items: {\n        $ref: '#/$defs/usage_list_with_groups_response'\n      }\n    },\n    next_page: {\n      type: 'string'\n    }\n  },\n  required: [    'data',\n    'next_page'\n  ],\n  $defs: {\n    usage_list_with_groups_response: {\n      type: 'object',\n      properties: {\n        ending_before: {\n          type: 'string',\n          format: 'date-time'\n        },\n        group_key: {\n          type: 'string'\n        },\n        group_value: {\n          type: 'string'\n        },\n        starting_on: {\n          type: 'string',\n          format: 'date-time'\n        },\n        value: {\n          type: 'number'\n        }\n      },\n      required: [        'ending_before',\n        'group_key',\n        'group_value',\n        'starting_on',\n        'value'\n      ]\n    }\n  }\n}\n```",
-  inputSchema: {
-    type: 'object',
-    properties: {
-      billable_metric_id: {
-        type: 'string',
-      },
-      customer_id: {
-        type: 'string',
-      },
-      window_size: {
-        type: 'string',
-        description:
-          'A window_size of "day" or "hour" will return the usage for the specified period segmented into daily or hourly aggregates. A window_size of "none" will return a single usage aggregate for the entirety of the specified period.',
-        enum: ['HOUR', 'DAY', 'NONE'],
-      },
-      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.',
-      },
-      current_period: {
-        type: 'boolean',
-        description:
-          'If true, will return the usage for the current billing period. Will return an error if the customer is currently uncontracted or starting_on and ending_before are specified when this is true.',
-      },
-      ending_before: {
-        type: 'string',
-        format: 'date-time',
-      },
-      group_by: {
-        type: 'object',
-        properties: {
-          key: {
-            type: 'string',
-            description: 'The name of the group_by key to use',
-          },
-          values: {
-            type: 'array',
-            description:
-              "Values of the group_by key to return in the query. Omit this if you'd like all values for the key returned.",
-            items: {
-              type: 'string',
-            },
-          },
-        },
-        required: ['key'],
-      },
-      starting_on: {
-        type: 'string',
-        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: ['billable_metric_id', 'customer_id', 'window_size'],
-  },
-  annotations: {},
-};
-
-export const handler = async (client: Metronome, args: Record<string, unknown> | undefined) => {
-  const { jq_filter, ...body } = args as any;
-  const response = await client.v1.usage.listWithGroups(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/usage/search-v1-usage.ts

@@ -1,56 +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.usage',
-  operation: 'write',
-  tags: [],
-  httpMethod: 'post',
-  httpPath: '/v1/events/search',
-  operationId: 'searchEvents-v1',
-};
-
-export const tool: Tool = {
-  name: 'search_v1_usage',
-  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\nThis endpoint retrieves events by transaction ID for events that occurred within the last 34 days. It is specifically designed for sampling-based testing workflows to detect revenue leakage. The Event Search API provides a critical observability tool that validates the integrity of your usage pipeline by allowing you to sample raw events and verify their matching against active billable metrics. \n\nWhy event observability matters for revenue leakage:\nSilent revenue loss occurs when events are dropped, delayed, or fail to match billable metrics due to:\n- Upstream system failures\n- Event format changes\n- Misconfigured billable metrics\n\n### Use this endpoint to:\n- Sample raw events and validate they match the expected billable metrics\n- Build custom leakage detection alerts to prevent silent revenue loss\n- Verify event processing accuracy during system changes or metric updates\n- Debug event matching issues in real-time\n\n### Key response fields:\n- Complete event details including transaction ID, customer ID, and properties\n- Matched Metronome customer (if any)\n- Matched billable metric information (if any)\n- Processing status and duplicate detection flags\n\n### Usage guidelines:\n⚠️ Important: This endpoint is heavily rate limited and designed for sampling workflows only. Do not use this endpoint to check every event in your system. Instead, implement a sampling strategy to randomly validate a subset of events for observability purposes.\n\n\n# Response Schema\n```json\n{\n  $ref: '#/$defs/usage_search_response',\n  $defs: {\n    usage_search_response: {\n      type: 'array',\n      items: {\n        type: 'object',\n        properties: {\n          id: {\n            type: 'string'\n          },\n          customer_id: {\n            type: 'string',\n            description: 'The ID of the customer in the ingest event body'\n          },\n          event_type: {\n            type: 'string'\n          },\n          timestamp: {\n            type: 'string',\n            format: 'date-time'\n          },\n          transaction_id: {\n            type: 'string'\n          },\n          is_duplicate: {\n            type: 'boolean'\n          },\n          matched_billable_metrics: {\n            type: 'array',\n            items: {\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. Includes \"custom_sql\" for events search endpoint responses.',\n                  enum: [                    'COUNT',\n                    'LATEST',\n                    'MAX',\n                    'SUM',\n                    'UNIQUE',\n                    'custom_sql'\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          },\n          matched_customer: {\n            type: 'object',\n            description: 'The customer the event was matched to if a match was found',\n            properties: {\n              id: {\n                type: 'string'\n              },\n              name: {\n                type: 'string'\n              }\n            }\n          },\n          processed_at: {\n            type: 'string',\n            format: 'date-time'\n          },\n          properties: {\n            type: 'object',\n            additionalProperties: true\n          }\n        },\n        required: [          'id',\n          'customer_id',\n          'event_type',\n          'timestamp',\n          'transaction_id'\n        ]\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: {
-      transactionIds: {
-        type: 'array',
-        description: 'The transaction IDs of the events to retrieve',
-        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: ['transactionIds'],
-  },
-  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.usage.search(body)));
-  } catch (error) {
-    if (error instanceof Metronome.APIError || isJqError(error)) {
-      return asErrorResult(error.message);
-    }
-    throw error;
-  }
-};
-
-export default { metadata, tool, handler };