@metronome/mcp 2.0.0 → 2.2.0

package/src/tools/v1/pricing-units/list-v1-pricing-units.ts

@@ -1,7 +1,7 @@
 // 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 { 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';
@@ -47,7 +47,14 @@ export const tool: Tool = {
 export const handler = async (client: Metronome, args: Record<string, unknown> | undefined) => {
   const { jq_filter, ...body } = args as any;
   const response = await client.v1.pricingUnits.list(body).asResponse();
-  return asTextContentResult(await maybeFilter(jq_filter, await response.json()));
+  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/services/list-v1-services.ts

@@ -1,7 +1,7 @@
 // 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 { 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';
@@ -38,7 +38,14 @@ export const tool: Tool = {
 
 export const handler = async (client: Metronome, args: Record<string, unknown> | undefined) => {
   const { jq_filter } = args as any;
-  return asTextContentResult(await maybeFilter(jq_filter, await client.v1.services.list()));
+  try {
+    return asTextContentResult(await maybeFilter(jq_filter, await client.v1.services.list()));
+  } catch (error) {
+    if (error instanceof Metronome.APIError || isJqError(error)) {
+      return asErrorResult(error.message);
+    }
+    throw error;
+  }
 };
 
 export default { metadata, tool, handler };

package/src/tools/v1/settings/billing-providers/create-settings-v1-billing-providers.ts

@@ -0,0 +1,67 @@
+// 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.billing_providers',
+  operation: 'write',
+  tags: [],
+  httpMethod: 'post',
+  httpPath: '/v1/setUpBillingProvider',
+  operationId: 'setUpBillingProvider-v1',
+};
+
+export const tool: Tool = {
+  name: 'create_settings_v1_billing_providers',
+  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 up account-level configuration for a billing provider. Once configured, individual contracts across customers can be mapped to this configuration using the returned delivery_method_id.\n\n\n# Response Schema\n```json\n{\n  $ref: '#/$defs/billing_provider_create_response',\n  $defs: {\n    billing_provider_create_response: {\n      type: 'object',\n      properties: {\n        data: {\n          type: 'object',\n          properties: {\n            delivery_method_id: {\n              type: 'string'\n            }\n          },\n          required: [            'delivery_method_id'\n          ]\n        }\n      },\n      required: [        'data'\n      ]\n    }\n  }\n}\n```",
+  inputSchema: {
+    type: 'object',
+    properties: {
+      billing_provider: {
+        type: 'string',
+        description: 'The billing provider set for this configuration.',
+        enum: ['aws_marketplace', 'azure_marketplace', 'gcp_marketplace'],
+      },
+      configuration: {
+        type: 'object',
+        description:
+          'Account-level configuration for the billing provider. The structure of this object is specific to the billing provider and delivery provider combination. See examples below.',
+        additionalProperties: true,
+      },
+      delivery_method: {
+        type: 'string',
+        description: 'The method to use for delivering invoices for this configuration.',
+        enum: ['direct_to_billing_provider', 'aws_sqs', 'aws_sns'],
+      },
+      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: ['billing_provider', 'configuration', 'delivery_method'],
+  },
+  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.billingProviders.create(body)),
+    );
+  } catch (error) {
+    if (error instanceof Metronome.APIError || isJqError(error)) {
+      return asErrorResult(error.message);
+    }
+    throw error;
+  }
+};
+
+export default { metadata, tool, handler };

package/src/tools/v1/settings/billing-providers/list-settings-v1-billing-providers.ts

@@ -0,0 +1,55 @@
+// 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.billing_providers',
+  operation: 'write',
+  tags: [],
+  httpMethod: 'post',
+  httpPath: '/v1/listConfiguredBillingProviders',
+  operationId: 'listConfiguredBillingProviders-v1',
+};
+
+export const tool: Tool = {
+  name: 'list_settings_v1_billing_providers',
+  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\nLists all configured billing providers and their delivery method configurations for your account. Returns provider details, delivery method IDs, and configuration settings needed for mapping individual customer contracts to billing integrations.\n\n\n# Response Schema\n```json\n{\n  $ref: '#/$defs/billing_provider_list_response',\n  $defs: {\n    billing_provider_list_response: {\n      type: 'object',\n      properties: {\n        data: {\n          type: 'array',\n          items: {\n            type: 'object',\n            properties: {\n              billing_provider: {\n                type: 'string',\n                description: 'The billing provider set for this configuration.',\n                enum: [                  'aws_marketplace',\n                  'stripe',\n                  'netsuite',\n                  'custom',\n                  'azure_marketplace',\n                  'quickbooks_online',\n                  'workday',\n                  'gcp_marketplace',\n                  'metronome'\n                ]\n              },\n              delivery_method: {\n                type: 'string',\n                description: 'The method to use for delivering invoices to this customer.',\n                enum: [                  'direct_to_billing_provider',\n                  'aws_sqs',\n                  'tackle',\n                  'aws_sns'\n                ]\n              },\n              delivery_method_configuration: {\n                type: 'object',\n                description: 'Configuration for the delivery method. The structure of this object is specific to the delivery method. Some configuration may be omitted for security reasons.',\n                additionalProperties: true\n              },\n              delivery_method_id: {\n                type: 'string',\n                description: 'ID of the delivery method to use for this customer.'\n              }\n            },\n            required: [              'billing_provider',\n              'delivery_method',\n              'delivery_method_configuration',\n              'delivery_method_id'\n            ]\n          }\n        },\n        next_page: {\n          type: 'string'\n        }\n      },\n      required: [        'data'\n      ]\n    }\n  }\n}\n```",
+  inputSchema: {
+    type: 'object',
+    properties: {
+      next_page: {
+        type: 'string',
+        description: 'The cursor to the next page of results',
+      },
+      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;
+  try {
+    return asTextContentResult(
+      await maybeFilter(jq_filter, await client.v1.settings.billingProviders.list(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/settings/upsert-avalara-credentials-v1-settings.ts

@@ -0,0 +1,77 @@
+// 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/list-v1-usage.ts

@@ -1,7 +1,7 @@
 // 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 { 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';
@@ -95,7 +95,14 @@ export const tool: Tool = {
 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();
-  return asTextContentResult(await maybeFilter(jq_filter, await response.json()));
+  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,7 +1,7 @@
 // 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 { 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';
@@ -88,7 +88,14 @@ export const tool: Tool = {
 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();
-  return asTextContentResult(await maybeFilter(jq_filter, await response.json()));
+  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,7 +1,7 @@
 // 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 { 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';
@@ -18,7 +18,7 @@ export const metadata: Metadata = {
 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.',\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          },\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```",
+    "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: {
@@ -43,7 +43,14 @@ export const tool: Tool = {
 
 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.usage.search(body)));
+  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 };

package/src/tools/v2/contracts/edit-commit-v2-contracts.ts

@@ -1,7 +1,7 @@
 // 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 { 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';
@@ -106,6 +106,10 @@ export const tool: Tool = {
           type: 'string',
         },
       },
+      description: {
+        type: 'string',
+        description: 'Updated description for the commit',
+      },
       hierarchy_configuration: {
         $ref: '#/$defs/commit_hierarchy_configuration',
       },
@@ -177,6 +181,10 @@ export const tool: Tool = {
           },
         },
       },
+      name: {
+        type: 'string',
+        description: 'Updated name for the commit',
+      },
       priority: {
         type: 'number',
         description: 'If multiple commits are applicable, the one with the lower priority will apply first.',
@@ -285,7 +293,14 @@ export const tool: Tool = {
 
 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.v2.contracts.editCommit(body)));
+  try {
+    return asTextContentResult(await maybeFilter(jq_filter, await client.v2.contracts.editCommit(body)));
+  } catch (error) {
+    if (error instanceof Metronome.APIError || isJqError(error)) {
+      return asErrorResult(error.message);
+    }
+    throw error;
+  }
 };
 
 export default { metadata, tool, handler };

package/src/tools/v2/contracts/edit-credit-v2-contracts.ts

@@ -1,7 +1,7 @@
 // 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 { 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';
@@ -106,9 +106,17 @@ export const tool: Tool = {
           type: 'string',
         },
       },
+      description: {
+        type: 'string',
+        description: 'Updated description for the credit',
+      },
       hierarchy_configuration: {
         $ref: '#/$defs/commit_hierarchy_configuration',
       },
+      name: {
+        type: 'string',
+        description: 'Updated name for the credit',
+      },
       priority: {
         type: 'number',
         description: 'If multiple commits are applicable, the one with the lower priority will apply first.',
@@ -217,7 +225,14 @@ export const tool: Tool = {
 
 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.v2.contracts.editCredit(body)));
+  try {
+    return asTextContentResult(await maybeFilter(jq_filter, await client.v2.contracts.editCredit(body)));
+  } catch (error) {
+    if (error instanceof Metronome.APIError || isJqError(error)) {
+      return asErrorResult(error.message);
+    }
+    throw error;
+  }
 };
 
 export default { metadata, tool, handler };