@metronome/mcp 2.0.0 → 2.2.0

package/src/tools/v1/credit-grants/list-entries-v1-credit-grants.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: 'list_entries_v1_credit_grants',
   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\nFetches a list of credit ledger entries. Returns lists of ledgers per customer. Ledger entries are returned in chronological order. Ledger entries associated with voided credit grants are not included.\n\n# Response Schema\n```json\n{\n  type: 'object',\n  properties: {\n    data: {\n      type: 'array',\n      items: {\n        $ref: '#/$defs/credit_grant_list_entries_response'\n      }\n    },\n    next_page: {\n      type: 'string'\n    }\n  },\n  required: [    'data',\n    'next_page'\n  ],\n  $defs: {\n    credit_grant_list_entries_response: {\n      type: 'object',\n      properties: {\n        customer_id: {\n          type: 'string'\n        },\n        ledgers: {\n          type: 'array',\n          items: {\n            type: 'object',\n            properties: {\n              credit_type: {\n                $ref: '#/$defs/credit_type_data'\n              },\n              ending_balance: {\n                type: 'object',\n                description: 'the effective balances at the end of the specified time window',\n                properties: {\n                  effective_at: {\n                    type: 'string',\n                    description: 'the ending_before request parameter (if supplied) or the current billing period\\'s end date',\n                    format: 'date-time'\n                  },\n                  excluding_pending: {\n                    type: 'number',\n                    description: 'the ending balance, including the balance of all grants that have not expired before the effective_at date and deductions that happened before the effective_at date'\n                  },\n                  including_pending: {\n                    type: 'number',\n                    description: 'the excluding_pending balance plus any pending invoice deductions and expirations that will happen by the effective_at date'\n                  }\n                },\n                required: [                  'effective_at',\n                  'excluding_pending',\n                  'including_pending'\n                ]\n              },\n              entries: {\n                type: 'array',\n                items: {\n                  $ref: '#/$defs/credit_ledger_entry'\n                }\n              },\n              pending_entries: {\n                type: 'array',\n                items: {\n                  $ref: '#/$defs/credit_ledger_entry'\n                }\n              },\n              starting_balance: {\n                type: 'object',\n                properties: {\n                  effective_at: {\n                    type: 'string',\n                    description: 'the starting_on request parameter (if supplied) or the first credit grant\\'s effective_at date',\n                    format: 'date-time'\n                  },\n                  excluding_pending: {\n                    type: 'number',\n                    description: 'the starting balance, including all posted grants, deductions, and expirations that happened at or before the effective_at timestamp'\n                  },\n                  including_pending: {\n                    type: 'number',\n                    description: 'the excluding_pending balance plus any pending activity that has not been posted at the time of the query'\n                  }\n                },\n                required: [                  'effective_at',\n                  'excluding_pending',\n                  'including_pending'\n                ]\n              }\n            },\n            required: [              'credit_type',\n              'ending_balance',\n              'entries',\n              'pending_entries',\n              'starting_balance'\n            ]\n          }\n        }\n      },\n      required: [        'customer_id',\n        'ledgers'\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    credit_ledger_entry: {\n      type: 'object',\n      properties: {\n        amount: {\n          type: 'number',\n          description: 'an amount representing the change to the customer\\'s credit balance'\n        },\n        created_by: {\n          type: 'string'\n        },\n        credit_grant_id: {\n          type: 'string',\n          description: 'the credit grant this entry is related to'\n        },\n        effective_at: {\n          type: 'string',\n          format: 'date-time'\n        },\n        reason: {\n          type: 'string'\n        },\n        running_balance: {\n          type: 'number',\n          description: 'the running balance for this credit type at the time of the ledger entry, including all preceding charges'\n        },\n        invoice_id: {\n          type: 'string',\n          description: 'if this entry is a deduction, the Metronome ID of the invoice where the credit deduction was consumed; if this entry is a grant, the Metronome ID of the invoice where the grant\\'s paid_amount was charged'\n        }\n      },\n      required: [        'amount',\n        'created_by',\n        'credit_grant_id',\n        'effective_at',\n        'reason',\n        'running_balance'\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\nFetches a list of credit ledger entries. Returns lists of ledgers per customer. Ledger entries are returned in chronological order. Ledger entries associated with voided credit grants are not included. 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/credit_grant_list_entries_response'\n      }\n    },\n    next_page: {\n      type: 'string'\n    }\n  },\n  required: [    'data',\n    'next_page'\n  ],\n  $defs: {\n    credit_grant_list_entries_response: {\n      type: 'object',\n      properties: {\n        customer_id: {\n          type: 'string'\n        },\n        ledgers: {\n          type: 'array',\n          items: {\n            type: 'object',\n            properties: {\n              credit_type: {\n                $ref: '#/$defs/credit_type_data'\n              },\n              ending_balance: {\n                type: 'object',\n                description: 'the effective balances at the end of the specified time window',\n                properties: {\n                  effective_at: {\n                    type: 'string',\n                    description: 'the ending_before request parameter (if supplied) or the current billing period\\'s end date',\n                    format: 'date-time'\n                  },\n                  excluding_pending: {\n                    type: 'number',\n                    description: 'the ending balance, including the balance of all grants that have not expired before the effective_at date and deductions that happened before the effective_at date'\n                  },\n                  including_pending: {\n                    type: 'number',\n                    description: 'the excluding_pending balance plus any pending invoice deductions and expirations that will happen by the effective_at date'\n                  }\n                },\n                required: [                  'effective_at',\n                  'excluding_pending',\n                  'including_pending'\n                ]\n              },\n              entries: {\n                type: 'array',\n                items: {\n                  $ref: '#/$defs/credit_ledger_entry'\n                }\n              },\n              pending_entries: {\n                type: 'array',\n                items: {\n                  $ref: '#/$defs/credit_ledger_entry'\n                }\n              },\n              starting_balance: {\n                type: 'object',\n                properties: {\n                  effective_at: {\n                    type: 'string',\n                    description: 'the starting_on request parameter (if supplied) or the first credit grant\\'s effective_at date',\n                    format: 'date-time'\n                  },\n                  excluding_pending: {\n                    type: 'number',\n                    description: 'the starting balance, including all posted grants, deductions, and expirations that happened at or before the effective_at timestamp'\n                  },\n                  including_pending: {\n                    type: 'number',\n                    description: 'the excluding_pending balance plus any pending activity that has not been posted at the time of the query'\n                  }\n                },\n                required: [                  'effective_at',\n                  'excluding_pending',\n                  'including_pending'\n                ]\n              }\n            },\n            required: [              'credit_type',\n              'ending_balance',\n              'entries',\n              'pending_entries',\n              'starting_balance'\n            ]\n          }\n        }\n      },\n      required: [        'customer_id',\n        'ledgers'\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    credit_ledger_entry: {\n      type: 'object',\n      properties: {\n        amount: {\n          type: 'number',\n          description: 'an amount representing the change to the customer\\'s credit balance'\n        },\n        created_by: {\n          type: 'string'\n        },\n        credit_grant_id: {\n          type: 'string',\n          description: 'the credit grant this entry is related to'\n        },\n        effective_at: {\n          type: 'string',\n          format: 'date-time'\n        },\n        reason: {\n          type: 'string'\n        },\n        running_balance: {\n          type: 'number',\n          description: 'the running balance for this credit type at the time of the ledger entry, including all preceding charges'\n        },\n        invoice_id: {\n          type: 'string',\n          description: 'if this entry is a deduction, the Metronome ID of the invoice where the credit deduction was consumed; if this entry is a grant, the Metronome ID of the invoice where the grant\\'s paid_amount was charged'\n        }\n      },\n      required: [        'amount',\n        'created_by',\n        'credit_grant_id',\n        'effective_at',\n        'reason',\n        'running_balance'\n      ]\n    }\n  }\n}\n```",
   inputSchema: {
     type: 'object',
     properties: {
@@ -73,7 +73,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.creditGrants.listEntries(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/credit-grants/list-v1-credit-grants.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: 'list_v1_credit_grants',
   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 credit grants. This list does not included voided grants.\n\n# Response Schema\n```json\n{\n  type: 'object',\n  properties: {\n    data: {\n      type: 'array',\n      items: {\n        $ref: '#/$defs/credit_grant_list_response'\n      }\n    },\n    next_page: {\n      type: 'string'\n    }\n  },\n  required: [    'data',\n    'next_page'\n  ],\n  $defs: {\n    credit_grant_list_response: {\n      type: 'object',\n      properties: {\n        id: {\n          type: 'string',\n          description: 'the Metronome ID of the credit grant'\n        },\n        balance: {\n          type: 'object',\n          description: 'The effective balance of the grant as of the end of the customer\\'s current billing period. Expiration deductions will be included only if the grant expires before the end of the current billing period.',\n          properties: {\n            effective_at: {\n              type: 'string',\n              description: 'The end_date of the customer\\'s current billing period.',\n              format: 'date-time'\n            },\n            excluding_pending: {\n              type: 'number',\n              description: 'The grant\\'s current balance including all posted deductions. If the grant has expired, this amount will be 0.'\n            },\n            including_pending: {\n              type: 'number',\n              description: 'The grant\\'s current balance including all posted and pending deductions. If the grant expires before the end of the customer\\'s current billing period, this amount will be 0.'\n            }\n          },\n          required: [            'effective_at',\n            'excluding_pending',\n            'including_pending'\n          ]\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_id: {\n          type: 'string',\n          description: 'the Metronome ID of the customer'\n        },\n        deductions: {\n          type: 'array',\n          items: {\n            $ref: '#/$defs/credit_ledger_entry'\n          }\n        },\n        effective_at: {\n          type: 'string',\n          format: 'date-time'\n        },\n        expires_at: {\n          type: 'string',\n          format: 'date-time'\n        },\n        grant_amount: {\n          type: 'object',\n          description: 'the amount of credits initially granted',\n          properties: {\n            amount: {\n              type: 'number'\n            },\n            credit_type: {\n              $ref: '#/$defs/credit_type_data'\n            }\n          },\n          required: [            'amount',\n            'credit_type'\n          ]\n        },\n        name: {\n          type: 'string'\n        },\n        paid_amount: {\n          type: 'object',\n          description: 'the amount paid for this credit grant',\n          properties: {\n            amount: {\n              type: 'number'\n            },\n            credit_type: {\n              $ref: '#/$defs/credit_type_data'\n            }\n          },\n          required: [            'amount',\n            'credit_type'\n          ]\n        },\n        pending_deductions: {\n          type: 'array',\n          items: {\n            $ref: '#/$defs/credit_ledger_entry'\n          }\n        },\n        priority: {\n          type: 'number'\n        },\n        credit_grant_type: {\n          type: 'string'\n        },\n        invoice_id: {\n          type: 'string',\n          description: 'the Metronome ID of the invoice with the purchase charge for this credit grant, if applicable'\n        },\n        products: {\n          type: 'array',\n          description: 'The products which these credits will be applied to. (If unspecified, the credits will be applied to charges for all products.)',\n          items: {\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        reason: {\n          type: 'string'\n        },\n        uniqueness_key: {\n          type: 'string',\n          description: 'Prevents the creation of duplicates. If a request to create a record is made with a previously used uniqueness key, a new record will not be created and the request will fail with a 409 error.'\n        }\n      },\n      required: [        'id',\n        'balance',\n        'custom_fields',\n        'customer_id',\n        'deductions',\n        'effective_at',\n        'expires_at',\n        'grant_amount',\n        'name',\n        'paid_amount',\n        'pending_deductions',\n        'priority'\n      ]\n    },\n    credit_ledger_entry: {\n      type: 'object',\n      properties: {\n        amount: {\n          type: 'number',\n          description: 'an amount representing the change to the customer\\'s credit balance'\n        },\n        created_by: {\n          type: 'string'\n        },\n        credit_grant_id: {\n          type: 'string',\n          description: 'the credit grant this entry is related to'\n        },\n        effective_at: {\n          type: 'string',\n          format: 'date-time'\n        },\n        reason: {\n          type: 'string'\n        },\n        running_balance: {\n          type: 'number',\n          description: 'the running balance for this credit type at the time of the ledger entry, including all preceding charges'\n        },\n        invoice_id: {\n          type: 'string',\n          description: 'if this entry is a deduction, the Metronome ID of the invoice where the credit deduction was consumed; if this entry is a grant, the Metronome ID of the invoice where the grant\\'s paid_amount was charged'\n        }\n      },\n      required: [        'amount',\n        'created_by',\n        'credit_grant_id',\n        'effective_at',\n        'reason',\n        'running_balance'\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```",
+    "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 credit grants. This list does not included voided grants. 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/credit_grant_list_response'\n      }\n    },\n    next_page: {\n      type: 'string'\n    }\n  },\n  required: [    'data',\n    'next_page'\n  ],\n  $defs: {\n    credit_grant_list_response: {\n      type: 'object',\n      properties: {\n        id: {\n          type: 'string',\n          description: 'the Metronome ID of the credit grant'\n        },\n        balance: {\n          type: 'object',\n          description: 'The effective balance of the grant as of the end of the customer\\'s current billing period. Expiration deductions will be included only if the grant expires before the end of the current billing period.',\n          properties: {\n            effective_at: {\n              type: 'string',\n              description: 'The end_date of the customer\\'s current billing period.',\n              format: 'date-time'\n            },\n            excluding_pending: {\n              type: 'number',\n              description: 'The grant\\'s current balance including all posted deductions. If the grant has expired, this amount will be 0.'\n            },\n            including_pending: {\n              type: 'number',\n              description: 'The grant\\'s current balance including all posted and pending deductions. If the grant expires before the end of the customer\\'s current billing period, this amount will be 0.'\n            }\n          },\n          required: [            'effective_at',\n            'excluding_pending',\n            'including_pending'\n          ]\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_id: {\n          type: 'string',\n          description: 'the Metronome ID of the customer'\n        },\n        deductions: {\n          type: 'array',\n          items: {\n            $ref: '#/$defs/credit_ledger_entry'\n          }\n        },\n        effective_at: {\n          type: 'string',\n          format: 'date-time'\n        },\n        expires_at: {\n          type: 'string',\n          format: 'date-time'\n        },\n        grant_amount: {\n          type: 'object',\n          description: 'the amount of credits initially granted',\n          properties: {\n            amount: {\n              type: 'number'\n            },\n            credit_type: {\n              $ref: '#/$defs/credit_type_data'\n            }\n          },\n          required: [            'amount',\n            'credit_type'\n          ]\n        },\n        name: {\n          type: 'string'\n        },\n        paid_amount: {\n          type: 'object',\n          description: 'the amount paid for this credit grant',\n          properties: {\n            amount: {\n              type: 'number'\n            },\n            credit_type: {\n              $ref: '#/$defs/credit_type_data'\n            }\n          },\n          required: [            'amount',\n            'credit_type'\n          ]\n        },\n        pending_deductions: {\n          type: 'array',\n          items: {\n            $ref: '#/$defs/credit_ledger_entry'\n          }\n        },\n        priority: {\n          type: 'number'\n        },\n        credit_grant_type: {\n          type: 'string'\n        },\n        invoice_id: {\n          type: 'string',\n          description: 'the Metronome ID of the invoice with the purchase charge for this credit grant, if applicable'\n        },\n        products: {\n          type: 'array',\n          description: 'The products which these credits will be applied to. (If unspecified, the credits will be applied to charges for all products.)',\n          items: {\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        reason: {\n          type: 'string'\n        },\n        uniqueness_key: {\n          type: 'string',\n          description: 'Prevents the creation of duplicates. If a request to create a record is made with a previously used uniqueness key, a new record will not be created and the request will fail with a 409 error.'\n        }\n      },\n      required: [        'id',\n        'balance',\n        'custom_fields',\n        'customer_id',\n        'deductions',\n        'effective_at',\n        'expires_at',\n        'grant_amount',\n        'name',\n        'paid_amount',\n        'pending_deductions',\n        'priority'\n      ]\n    },\n    credit_ledger_entry: {\n      type: 'object',\n      properties: {\n        amount: {\n          type: 'number',\n          description: 'an amount representing the change to the customer\\'s credit balance'\n        },\n        created_by: {\n          type: 'string'\n        },\n        credit_grant_id: {\n          type: 'string',\n          description: 'the credit grant this entry is related to'\n        },\n        effective_at: {\n          type: 'string',\n          format: 'date-time'\n        },\n        reason: {\n          type: 'string'\n        },\n        running_balance: {\n          type: 'number',\n          description: 'the running balance for this credit type at the time of the ledger entry, including all preceding charges'\n        },\n        invoice_id: {\n          type: 'string',\n          description: 'if this entry is a deduction, the Metronome ID of the invoice where the credit deduction was consumed; if this entry is a grant, the Metronome ID of the invoice where the grant\\'s paid_amount was charged'\n        }\n      },\n      required: [        'amount',\n        'created_by',\n        'credit_grant_id',\n        'effective_at',\n        'reason',\n        'running_balance'\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: {
@@ -79,7 +79,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.creditGrants.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/credit-grants/void-v1-credit-grants.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: 'void_v1_credit_grants',
   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\nVoid a credit grant\n\n# Response Schema\n```json\n{\n  $ref: '#/$defs/credit_grant_void_response',\n  $defs: {\n    credit_grant_void_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```",
+    "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\nVoid a credit grant. This is a Plans (deprecated) endpoint. New clients should implement using Contracts.\n\n\n# Response Schema\n```json\n{\n  $ref: '#/$defs/credit_grant_void_response',\n  $defs: {\n    credit_grant_void_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: {
@@ -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;
-  return asTextContentResult(await maybeFilter(jq_filter, await client.v1.creditGrants.void(body)));
+  try {
+    return asTextContentResult(await maybeFilter(jq_filter, await client.v1.creditGrants.void(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/custom-fields/list-keys-v1-custom-fields.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';
@@ -68,7 +68,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.customFields.listKeys(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/customers/alerts/list-customers-v1-alerts.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: 'list_customers_v1_alerts',
   description:
-    "When using this tool, always use the `jq_filter` parameter to reduce the response size and improve performance.\n\nOnly omit if you're sure you don't need the data.\n\nRetrieve all threshold notification configurations and their current statuses for a specific customer in a single API call. This endpoint provides a comprehensive view of all threshold notification monitoring a customer account.\n\n### Use this endpoint to:\n- Display all active threshold notifications for a customer in dashboards or admin panels\n- Quickly identify which threshold notifications a customer is currently triggering\n- Audit threshold notification coverage for specific accounts\n- Filter threshold notifications by status (enabled, disabled, or archived)\n\n### Key response fields:\n- data: Array of CustomerAlert objects, each containing:\n  - Current evaluation status (`ok`, `in_alarm`, `evaluating`, or `null`)\n  - Complete threshold notification configuration and threshold details\n  - Threshold notification metadata including type, name, and last update time\n- next_page: Pagination cursor for retrieving additional results\n\n### Usage guidelines:\n- Default behavior: Returns only enabled threshold notifications unless `alert_statuses` filter is specified\n- Pagination: Use the `next_page` cursor to retrieve all results for customers with many notifications\n- Performance: Efficiently retrieves multiple threshold notification statuses in a single request instead of making individual calls\n- Filtering: Pass the `alert_statuses` array to include disabled or archived threshold notifications in results\n\n\n# Response Schema\n```json\n{\n  type: 'object',\n  properties: {\n    data: {\n      type: 'array',\n      items: {\n        $ref: '#/$defs/customer_alert'\n      }\n    },\n    next_page: {\n      type: 'string'\n    }\n  },\n  required: [    'data',\n    'next_page'\n  ],\n  $defs: {\n    customer_alert: {\n      type: 'object',\n      properties: {\n        alert: {\n          type: 'object',\n          properties: {\n            id: {\n              type: 'string',\n              description: 'the Metronome ID of the threshold notification'\n            },\n            name: {\n              type: 'string',\n              description: 'Name of the threshold notification'\n            },\n            status: {\n              type: 'string',\n              description: 'Status of the threshold notification',\n              enum: [                'enabled',\n                'archived',\n                'disabled'\n              ]\n            },\n            threshold: {\n              type: 'number',\n              description: 'Threshold value of the notification policy'\n            },\n            type: {\n              type: 'string',\n              description: 'Type of the threshold notification',\n              enum: [                'low_credit_balance_reached',\n                'spend_threshold_reached',\n                'monthly_invoice_total_spend_threshold_reached',\n                'low_remaining_days_in_plan_reached',\n                'low_remaining_credit_percentage_reached',\n                'usage_threshold_reached',\n                'low_remaining_days_for_commit_segment_reached',\n                'low_remaining_commit_balance_reached',\n                'low_remaining_commit_percentage_reached',\n                'low_remaining_days_for_contract_credit_segment_reached',\n                'low_remaining_contract_credit_balance_reached',\n                'low_remaining_contract_credit_percentage_reached',\n                'low_remaining_contract_credit_and_commit_balance_reached',\n                'invoice_total_reached'\n              ]\n            },\n            updated_at: {\n              type: 'string',\n              description: 'Timestamp for when the threshold notification was last updated',\n              format: 'date-time'\n            },\n            credit_grant_type_filters: {\n              type: 'array',\n              description: 'An array of strings, representing a way to filter the credit grant this threshold notification applies to, by looking at the credit_grant_type field on the credit grant. This field is only defined for CreditPercentage and CreditBalance notifications',\n              items: {\n                type: 'string'\n              }\n            },\n            credit_type: {\n              $ref: '#/$defs/credit_type_data'\n            },\n            custom_field_filters: {\n              type: 'array',\n              description: 'A list of custom field filters for notification types that support advanced filtering',\n              items: {\n                type: 'object',\n                properties: {\n                  entity: {\n                    type: 'string',\n                    enum: [                      'Contract',\n                      'Commit',\n                      'ContractCredit'\n                    ]\n                  },\n                  key: {\n                    type: 'string'\n                  },\n                  value: {\n                    type: 'string'\n                  }\n                },\n                required: [                  'entity',\n                  'key',\n                  'value'\n                ]\n              }\n            },\n            group_key_filter: {\n              type: 'object',\n              description: 'Scopes threshold notification evaluation to a specific presentation group key on individual line items. Only present for spend notifications.',\n              properties: {\n                key: {\n                  type: 'string'\n                },\n                value: {\n                  type: 'string'\n                }\n              },\n              required: [                'key',\n                'value'\n              ]\n            },\n            group_values: {\n              type: 'array',\n              description: 'Only present for `spend_threshold_reached` notifications. Scope notification to a specific group key on individual line items.',\n              items: {\n                type: 'object',\n                properties: {\n                  key: {\n                    type: 'string'\n                  },\n                  value: {\n                    type: 'string'\n                  }\n                },\n                required: [                  'key'\n                ]\n              }\n            },\n            invoice_types_filter: {\n              type: 'array',\n              description: 'Only supported for invoice_total_reached threshold notifications. A list of invoice types to evaluate.',\n              items: {\n                type: 'string'\n              }\n            },\n            uniqueness_key: {\n              type: 'string',\n              description: 'Prevents the creation of duplicates. If a request to create a record is made with a previously used uniqueness key, a new record will not be created and the request will fail with a 409 error.'\n            }\n          },\n          required: [            'id',\n            'name',\n            'status',\n            'threshold',\n            'type',\n            'updated_at'\n          ]\n        },\n        customer_status: {\n          type: 'string',\n          description: 'The status of the threshold notification. If the notification is archived, null will be returned.',\n          enum: [            'ok',\n            'in_alarm',\n            'evaluating'\n          ]\n        },\n        triggered_by: {\n          type: 'string',\n          description: 'If present, indicates the reason the threshold notification was triggered.'\n        }\n      },\n      required: [        'alert',\n        'customer_status'\n      ]\n    },\n    credit_type_data: {\n      type: 'object',\n      properties: {\n        id: {\n          type: 'string'\n        },\n        name: {\n          type: 'string'\n        }\n      },\n      required: [        'id',\n        'name'\n      ]\n    }\n  }\n}\n```",
+    "When using this tool, always use the `jq_filter` parameter to reduce the response size and improve performance.\n\nOnly omit if you're sure you don't need the data.\n\nRetrieve all threshold notification configurations and their current statuses for a specific customer in a single API call. This endpoint provides a comprehensive view of all threshold notification monitoring a customer account.\n\n### Use this endpoint to:\n- Display all active threshold notifications for a customer in dashboards or admin panels\n- Quickly identify which threshold notifications a customer is currently triggering\n- Audit threshold notification coverage for specific accounts\n- Filter threshold notifications by status (enabled, disabled, or archived)\n\n### Key response fields:\n- data: Array of CustomerAlert objects, each containing:\n  - Current evaluation status (`ok`, `in_alarm`, `evaluating`, or `null`)\n  - Complete threshold notification configuration and threshold details\n  - Threshold notification metadata including type, name, and last update time\n- next_page: Pagination cursor for retrieving additional results\n\n### Usage guidelines:\n- Default behavior: Returns only enabled threshold notifications unless `alert_statuses` filter is specified\n- Pagination: Use the `next_page` cursor to retrieve all results for customers with many notifications\n- Performance: Efficiently retrieves multiple threshold notification statuses in a single request instead of making individual calls\n- Filtering: Pass the `alert_statuses` array to include disabled or archived threshold notifications in results\n\n\n# Response Schema\n```json\n{\n  type: 'object',\n  properties: {\n    data: {\n      type: 'array',\n      items: {\n        $ref: '#/$defs/customer_alert'\n      }\n    },\n    next_page: {\n      type: 'string'\n    }\n  },\n  required: [    'data',\n    'next_page'\n  ],\n  $defs: {\n    customer_alert: {\n      type: 'object',\n      properties: {\n        alert: {\n          type: 'object',\n          properties: {\n            id: {\n              type: 'string',\n              description: 'the Metronome ID of the threshold notification'\n            },\n            name: {\n              type: 'string',\n              description: 'Name of the threshold notification'\n            },\n            status: {\n              type: 'string',\n              description: 'Status of the threshold notification',\n              enum: [                'enabled',\n                'archived',\n                'disabled'\n              ]\n            },\n            threshold: {\n              type: 'number',\n              description: 'Threshold value of the notification policy'\n            },\n            type: {\n              type: 'string',\n              description: 'Type of the threshold notification',\n              enum: [                'low_credit_balance_reached',\n                'spend_threshold_reached',\n                'monthly_invoice_total_spend_threshold_reached',\n                'low_remaining_days_in_plan_reached',\n                'low_remaining_credit_percentage_reached',\n                'usage_threshold_reached',\n                'low_remaining_days_for_commit_segment_reached',\n                'low_remaining_commit_balance_reached',\n                'low_remaining_commit_percentage_reached',\n                'low_remaining_days_for_contract_credit_segment_reached',\n                'low_remaining_contract_credit_balance_reached',\n                'low_remaining_contract_credit_percentage_reached',\n                'low_remaining_contract_credit_and_commit_balance_reached',\n                'low_remaining_seat_balance_reached',\n                'invoice_total_reached'\n              ]\n            },\n            updated_at: {\n              type: 'string',\n              description: 'Timestamp for when the threshold notification was last updated',\n              format: 'date-time'\n            },\n            credit_grant_type_filters: {\n              type: 'array',\n              description: 'An array of strings, representing a way to filter the credit grant this threshold notification applies to, by looking at the credit_grant_type field on the credit grant. This field is only defined for CreditPercentage and CreditBalance notifications',\n              items: {\n                type: 'string'\n              }\n            },\n            credit_type: {\n              $ref: '#/$defs/credit_type_data'\n            },\n            custom_field_filters: {\n              type: 'array',\n              description: 'A list of custom field filters for notification types that support advanced filtering',\n              items: {\n                type: 'object',\n                properties: {\n                  entity: {\n                    type: 'string',\n                    enum: [                      'Contract',\n                      'Commit',\n                      'ContractCredit'\n                    ]\n                  },\n                  key: {\n                    type: 'string'\n                  },\n                  value: {\n                    type: 'string'\n                  }\n                },\n                required: [                  'entity',\n                  'key',\n                  'value'\n                ]\n              }\n            },\n            group_key_filter: {\n              type: 'object',\n              description: 'Scopes threshold notification evaluation to a specific presentation group key on individual line items. Only present for spend notifications.',\n              properties: {\n                key: {\n                  type: 'string'\n                },\n                value: {\n                  type: 'string'\n                }\n              },\n              required: [                'key',\n                'value'\n              ]\n            },\n            group_values: {\n              type: 'array',\n              description: 'Only present for `spend_threshold_reached` notifications. Scope notification to a specific group key on individual line items.',\n              items: {\n                type: 'object',\n                properties: {\n                  key: {\n                    type: 'string'\n                  },\n                  value: {\n                    type: 'string'\n                  }\n                },\n                required: [                  'key'\n                ]\n              }\n            },\n            invoice_types_filter: {\n              type: 'array',\n              description: 'Only supported for invoice_total_reached threshold notifications. A list of invoice types to evaluate.',\n              items: {\n                type: 'string'\n              }\n            },\n            seat_filter: {\n              type: 'object',\n              description: 'Only present for low_remaining_seat_balance_reached notifications. The seat group key or seat group key-value pair the alert is scoped to.',\n              properties: {\n                seat_group_key: {\n                  type: 'string',\n                  description: 'The seat group key (e.g., \"seat_id\", \"user_id\") that the alert is scoped to.'\n                },\n                seat_group_value: {\n                  type: 'string',\n                  description: 'The seat group value that the alert is scoped to.'\n                }\n              },\n              required: [                'seat_group_key'\n              ]\n            },\n            uniqueness_key: {\n              type: 'string',\n              description: 'Prevents the creation of duplicates. If a request to create a record is made with a previously used uniqueness key, a new record will not be created and the request will fail with a 409 error.'\n            }\n          },\n          required: [            'id',\n            'name',\n            'status',\n            'threshold',\n            'type',\n            'updated_at'\n          ]\n        },\n        customer_status: {\n          type: 'string',\n          description: 'The status of the threshold notification. If the notification is archived, null will be returned.',\n          enum: [            'ok',\n            'in_alarm',\n            'evaluating'\n          ]\n        },\n        triggered_by: {\n          type: 'string',\n          description: 'If present, indicates the reason the threshold notification was triggered.'\n        }\n      },\n      required: [        'alert',\n        'customer_status'\n      ]\n    },\n    credit_type_data: {\n      type: 'object',\n      properties: {\n        id: {\n          type: 'string'\n        },\n        name: {\n          type: 'string'\n        }\n      },\n      required: [        'id',\n        'name'\n      ]\n    }\n  }\n}\n```",
   inputSchema: {
     type: 'object',
     properties: {
@@ -54,7 +54,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.customers.alerts.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/customers/alerts/retrieve-customers-v1-alerts.ts

@@ -1,6 +1,6 @@
 // File generated from our OpenAPI spec by Stainless. See CONTRIBUTING.md for details.
 
-import { Metadata, asTextContentResult } from '@metronome/mcp/tools/types';
+import { Metadata, asErrorResult, asTextContentResult } from '@metronome/mcp/tools/types';
 
 import { Tool } from '@modelcontextprotocol/sdk/types.js';
 import Metronome from '@metronome/sdk';
@@ -54,6 +54,22 @@ export const tool: Tool = {
           'When parallel threshold notifications are enabled during migration, this flag denotes whether to fetch notifications for plans or contracts.',
         enum: ['PLANS', 'CONTRACTS'],
       },
+      seat_filter: {
+        type: 'object',
+        description:
+          'Only allowed for `low_remaining_seat_balance_reached` notifications. This filters alerts by the seat group key-value pair.',
+        properties: {
+          seat_group_key: {
+            type: 'string',
+            description: 'The seat group key (e.g., "seat_id", "user_id")',
+          },
+          seat_group_value: {
+            type: 'string',
+            description: 'The specific seat identifier to filter by',
+          },
+        },
+        required: ['seat_group_key', 'seat_group_value'],
+      },
     },
     required: ['alert_id', 'customer_id'],
   },
@@ -62,7 +78,14 @@ export const tool: Tool = {
 
 export const handler = async (client: Metronome, args: Record<string, unknown> | undefined) => {
   const body = args as any;
-  return asTextContentResult(await client.v1.customers.alerts.retrieve(body));
+  try {
+    return asTextContentResult(await client.v1.customers.alerts.retrieve(body));
+  } catch (error) {
+    if (error instanceof Metronome.APIError) {
+      return asErrorResult(error.message);
+    }
+    throw error;
+  }
 };
 
 export default { metadata, tool, handler };

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

@@ -1,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';
@@ -39,7 +39,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.customers.archive(body)));
+  try {
+    return asTextContentResult(await maybeFilter(jq_filter, await client.v1.customers.archive(body)));
+  } catch (error) {
+    if (error instanceof Metronome.APIError || isJqError(error)) {
+      return asErrorResult(error.message);
+    }
+    throw error;
+  }
 };
 
 export default { metadata, tool, handler };

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

@@ -16,7 +16,8 @@ export const metadata: Metadata = {
 
 export const tool: Tool = {
   name: 'create_customers_v1_billing_config',
-  description: 'Set the billing configuration for a given customer.',
+  description:
+    'Set the billing configuration for a given customer. This is a Plans (deprecated) endpoint. New clients should implement using Contracts.\n',
   inputSchema: {
     type: 'object',
     properties: {
@@ -34,6 +35,7 @@ export const tool: Tool = {
           'quickbooks_online',
           'workday',
           'gcp_marketplace',
+          'metronome',
         ],
       },
       billing_provider_customer_id: {
@@ -41,6 +43,12 @@ export const tool: Tool = {
         description:
           "The customer ID in the billing provider's system. For Azure, this is the subscription ID.",
       },
+      aws_customer_account_id: {
+        type: 'string',
+      },
+      aws_customer_id: {
+        type: 'string',
+      },
       aws_product_code: {
         type: 'string',
       },
@@ -76,6 +84,8 @@ export const tool: Tool = {
       },
       stripe_collection_method: {
         type: 'string',
+        description:
+          "The collection method for the customer's invoices.\nNOTE: `auto_charge_payment_intent` and `manually_charge_payment_intent` are in beta.",
         enum: [
           'charge_automatically',
           'send_invoice',

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

@@ -17,7 +17,7 @@ export const metadata: Metadata = {
 export const tool: Tool = {
   name: 'delete_customers_v1_billing_config',
   description:
-    'Delete the billing configuration for a given customer. Note: this is unsupported for Azure and AWS Marketplace customers.\n',
+    'Delete the billing configuration for a given customer.\nNote: this is unsupported for Azure and AWS Marketplace customers. This is a Plans (deprecated) endpoint. New clients should implement using Contracts.\n',
   inputSchema: {
     type: 'object',
     properties: {
@@ -35,6 +35,7 @@ export const tool: Tool = {
           'quickbooks_online',
           'workday',
           'gcp_marketplace',
+          'metronome',
         ],
       },
     },

package/src/tools/v1/customers/billing-config/retrieve-customers-v1-billing-config.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: 'retrieve_customers_v1_billing_config',
   description:
-    "When using this tool, always use the `jq_filter` parameter to reduce the response size and improve performance.\n\nOnly omit if you're sure you don't need the data.\n\nFetch the billing configuration for the given customer.\n\n# Response Schema\n```json\n{\n  $ref: '#/$defs/billing_config_retrieve_response',\n  $defs: {\n    billing_config_retrieve_response: {\n      type: 'object',\n      properties: {\n        data: {\n          type: 'object',\n          properties: {\n            aws_expiration_date: {\n              type: 'string',\n              description: 'Contract expiration date for the customer. The expected format is RFC 3339 and can be retrieved from [AWS\\'s GetEntitlements API](https://docs.aws.amazon.com/marketplaceentitlement/latest/APIReference/API_GetEntitlements.html).',\n              format: 'date-time'\n            },\n            aws_is_subscription_product: {\n              type: 'boolean',\n              description: 'True if the aws_product_code is a SAAS subscription product, false otherwise.'\n            },\n            aws_product_code: {\n              type: 'string'\n            },\n            aws_region: {\n              type: 'string',\n              enum: [                'af-south-1',\n                'ap-east-1',\n                'ap-northeast-1',\n                'ap-northeast-2',\n                'ap-northeast-3',\n                'ap-south-1',\n                'ap-southeast-1',\n                'ap-southeast-2',\n                'ca-central-1',\n                'cn-north-1',\n                'cn-northwest-1',\n                'eu-central-1',\n                'eu-north-1',\n                'eu-south-1',\n                'eu-west-1',\n                'eu-west-2',\n                'eu-west-3',\n                'me-south-1',\n                'sa-east-1',\n                'us-east-1',\n                'us-east-2',\n                'us-gov-east-1',\n                'us-gov-west-1',\n                'us-west-1',\n                'us-west-2'\n              ]\n            },\n            azure_expiration_date: {\n              type: 'string',\n              description: 'Subscription term start/end date for the customer. The expected format is RFC 3339 and can be retrieved from [Azure\\'s Get Subscription API](https://learn.microsoft.com/en-us/partner-center/marketplace/partner-center-portal/pc-saas-fulfillment-subscription-api#get-subscription).',\n              format: 'date-time'\n            },\n            azure_plan_id: {\n              type: 'string'\n            },\n            azure_start_date: {\n              type: 'string',\n              description: 'Subscription term start/end date for the customer. The expected format is RFC 3339 and can be retrieved from [Azure\\'s Get Subscription API](https://learn.microsoft.com/en-us/partner-center/marketplace/partner-center-portal/pc-saas-fulfillment-subscription-api#get-subscription).',\n              format: 'date-time'\n            },\n            azure_subscription_status: {\n              type: 'string',\n              enum: [                'Subscribed',\n                'Unsubscribed',\n                'Suspended',\n                'PendingFulfillmentStart'\n              ]\n            },\n            billing_provider_customer_id: {\n              type: 'string'\n            },\n            stripe_collection_method: {\n              type: 'string',\n              enum: [                'charge_automatically',\n                'send_invoice',\n                'auto_charge_payment_intent',\n                'manually_charge_payment_intent'\n              ]\n            }\n          }\n        }\n      },\n      required: [        'data'\n      ]\n    }\n  }\n}\n```",
+    "When using this tool, always use the `jq_filter` parameter to reduce the response size and improve performance.\n\nOnly omit if you're sure you don't need the data.\n\nFetch the billing configuration for the given customer. This is a Plans (deprecated) endpoint. New clients should implement using Contracts.\n\n\n# Response Schema\n```json\n{\n  $ref: '#/$defs/billing_config_retrieve_response',\n  $defs: {\n    billing_config_retrieve_response: {\n      type: 'object',\n      properties: {\n        data: {\n          type: 'object',\n          properties: {\n            aws_customer_account_id: {\n              type: 'string'\n            },\n            aws_customer_id: {\n              type: 'string'\n            },\n            aws_expiration_date: {\n              type: 'string',\n              description: 'Contract expiration date for the customer. The expected format is RFC 3339 and can be retrieved from [AWS\\'s GetEntitlements API](https://docs.aws.amazon.com/marketplaceentitlement/latest/APIReference/API_GetEntitlements.html).',\n              format: 'date-time'\n            },\n            aws_is_subscription_product: {\n              type: 'boolean',\n              description: 'True if the aws_product_code is a SAAS subscription product, false otherwise.'\n            },\n            aws_product_code: {\n              type: 'string'\n            },\n            aws_region: {\n              type: 'string',\n              enum: [                'af-south-1',\n                'ap-east-1',\n                'ap-northeast-1',\n                'ap-northeast-2',\n                'ap-northeast-3',\n                'ap-south-1',\n                'ap-southeast-1',\n                'ap-southeast-2',\n                'ca-central-1',\n                'cn-north-1',\n                'cn-northwest-1',\n                'eu-central-1',\n                'eu-north-1',\n                'eu-south-1',\n                'eu-west-1',\n                'eu-west-2',\n                'eu-west-3',\n                'me-south-1',\n                'sa-east-1',\n                'us-east-1',\n                'us-east-2',\n                'us-gov-east-1',\n                'us-gov-west-1',\n                'us-west-1',\n                'us-west-2'\n              ]\n            },\n            azure_expiration_date: {\n              type: 'string',\n              description: 'Subscription term start/end date for the customer. The expected format is RFC 3339 and can be retrieved from [Azure\\'s Get Subscription API](https://learn.microsoft.com/en-us/partner-center/marketplace/partner-center-portal/pc-saas-fulfillment-subscription-api#get-subscription).',\n              format: 'date-time'\n            },\n            azure_plan_id: {\n              type: 'string'\n            },\n            azure_start_date: {\n              type: 'string',\n              description: 'Subscription term start/end date for the customer. The expected format is RFC 3339 and can be retrieved from [Azure\\'s Get Subscription API](https://learn.microsoft.com/en-us/partner-center/marketplace/partner-center-portal/pc-saas-fulfillment-subscription-api#get-subscription).',\n              format: 'date-time'\n            },\n            azure_subscription_status: {\n              type: 'string',\n              enum: [                'Subscribed',\n                'Unsubscribed',\n                'Suspended',\n                'PendingFulfillmentStart'\n              ]\n            },\n            billing_provider_customer_id: {\n              type: 'string'\n            },\n            stripe_collection_method: {\n              type: 'string',\n              description: 'The collection method for the customer\\'s invoices.\\nNOTE: `auto_charge_payment_intent` and `manually_charge_payment_intent` are in beta.',\n              enum: [                'charge_automatically',\n                'send_invoice',\n                'auto_charge_payment_intent',\n                'manually_charge_payment_intent'\n              ]\n            }\n          }\n        }\n      },\n      required: [        'data'\n      ]\n    }\n  }\n}\n```",
   inputSchema: {
     type: 'object',
     properties: {
@@ -36,6 +36,7 @@ export const tool: Tool = {
           'quickbooks_online',
           'workday',
           'gcp_marketplace',
+          'metronome',
         ],
       },
       jq_filter: {
@@ -54,9 +55,16 @@ 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.customers.billingConfig.retrieve(body)),
-  );
+  try {
+    return asTextContentResult(
+      await maybeFilter(jq_filter, await client.v1.customers.billingConfig.retrieve(body)),
+    );
+  } catch (error) {
+    if (error instanceof Metronome.APIError || isJqError(error)) {
+      return asErrorResult(error.message);
+    }
+    throw error;
+  }
 };
 
 export default { metadata, tool, handler };

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

@@ -1,6 +1,6 @@
 // File generated from our OpenAPI spec by Stainless. See CONTRIBUTING.md for details.
 
-import { Metadata, asTextContentResult } from '@metronome/mcp/tools/types';
+import { Metadata, asErrorResult, asTextContentResult } from '@metronome/mcp/tools/types';
 
 import { Tool } from '@modelcontextprotocol/sdk/types.js';
 import Metronome from '@metronome/sdk';
@@ -17,7 +17,7 @@ export const metadata: Metadata = {
 export const tool: Tool = {
   name: 'create_customers_v1_commits',
   description:
-    'Creates customer-level commits that establish spending commitments for customers across their Metronome usage. Commits represent contracted spending obligations that can be either prepaid (paid upfront) or postpaid (billed later). \n\nNote: In most cases, you should add commitments directly to customer contracts using the contract/create or contract/edit APIs.\n\n### Use this endpoint to:\nUse this endpoint when you need to establish customer-level spending commitments that can be applied across multiple contracts or scoped to specific contracts. Customer-level commits are ideal for:\n- Enterprise-wide minimum spending agreements that span multiple contracts\n- Multi-contract volume commitments with shared spending pools\n- Cross-contract discount tiers based on aggregate usage\n\n#### Commit type Requirements: \n- You must specify either "prepaid" or "postpaid" as the commit type:\n- Prepaid commits: Customer pays upfront; invoice_schedule is optional (if omitted, creates a commit without an invoice)\n- Postpaid commits: Customer pays when the commitment expires (the end of the access_schedule); invoice_schedule is required and must match access_schedule totals. \n\n#### Billing configuration:\n- invoice_contract_id is required for postpaid commits and for prepaid commits with billing (only optional for free prepaid commits)\n- For postpaid commits: access_schedule and invoice_schedule must have matching amounts\n- For postpaid commits: only one schedule item is allowed in both schedules.\n\n#### Scoping flexibility:\nCustomer-level commits can be configured in a few ways:\n- Contract-specific: Use the `applicable_contract_ids` field to limit the commit to specific contracts\n- Cross-contract: Leave `applicable_contract_ids` empty to allow the commit to be used across all of the customer\'s contracts\n\n#### Product targeting:\nCommits can be scoped to specific products using applicable_product_ids, applicable_product_tags, or specifiers, or left unrestricted to apply to all products.\n\n#### Priority considerations:\nWhen multiple commits are applicable, the one with the lower priority value will be consumed first. If there is a tie, contract level commits and credits will be applied before customer level commits and credits. Plan your priority scheme carefully to ensure commits are applied in the desired order.\n\n### Usage guidelines:\n⚠️ Preferred Alternative: In most cases, you should add commits directly to contracts using the create contract or edit contract APIs instead of creating customer-level commits. Contract-level commits provide better organization and are the recommended approach for standard use cases.\n',
+    'Creates customer-level commits that establish spending commitments for customers across their Metronome usage. Commits represent contracted spending obligations that can be either prepaid (paid upfront) or postpaid (billed later). \n\nNote: In most cases, you should add commitments directly to customer contracts using the contract/create or contract/edit APIs.\n\n### Use this endpoint to:\nUse this endpoint when you need to establish customer-level spending commitments that can be applied across multiple contracts or scoped to specific contracts. Customer-level commits are ideal for:\n- Enterprise-wide minimum spending agreements that span multiple contracts\n- Multi-contract volume commitments with shared spending pools\n- Cross-contract discount tiers based on aggregate usage\n\n#### Commit type Requirements: \n- You must specify either "prepaid" or "postpaid" as the commit type:\n- Prepaid commits: Customer pays upfront; invoice_schedule is optional (if omitted, creates a commit without an invoice)\n- Postpaid commits: Customer pays when the commitment expires (the end of the access_schedule); invoice_schedule is required and must match access_schedule totals. \n\n#### Billing configuration:\n- invoice_contract_id is required for postpaid commits and for prepaid commits with billing (only optional for free prepaid commits) unless do_not_invoice is set to true\n- For postpaid commits: access_schedule and invoice_schedule must have matching amounts\n- For postpaid commits: only one schedule item is allowed in both schedules.\n\n#### Scoping flexibility:\nCustomer-level commits can be configured in a few ways:\n- Contract-specific: Use the `applicable_contract_ids` field to limit the commit to specific contracts\n- Cross-contract: Leave `applicable_contract_ids` empty to allow the commit to be used across all of the customer\'s contracts\n\n#### Product targeting:\nCommits can be scoped to specific products using applicable_product_ids, applicable_product_tags, or specifiers, or left unrestricted to apply to all products.\n\n#### Priority considerations:\nWhen multiple commits are applicable, the one with the lower priority value will be consumed first. If there is a tie, contract level commits and credits will be applied before customer level commits and credits. Plan your priority scheme carefully to ensure commits are applied in the desired order.\n\n### Usage guidelines:\n⚠️ Preferred Alternative: In most cases, you should add commits directly to contracts using the create contract or edit contract APIs instead of creating customer-level commits. Contract-level commits provide better organization and are the recommended approach for standard use cases.\n',
   inputSchema: {
     type: 'object',
     properties: {
@@ -108,7 +108,7 @@ export const tool: Tool = {
       invoice_contract_id: {
         type: 'string',
         description:
-          'The contract that this commit will be billed on. This is required for "POSTPAID" commits and for "PREPAID" commits unless there is no invoice schedule above (i.e., the commit is \'free\').',
+          'The contract that this commit will be billed on. This is required for "POSTPAID" commits and for "PREPAID" commits unless there is no invoice schedule above (i.e., the commit is \'free\'), or if do_not_invoice is set to true.',
       },
       invoice_schedule: {
         type: 'object',
@@ -261,7 +261,14 @@ export const tool: Tool = {
 
 export const handler = async (client: Metronome, args: Record<string, unknown> | undefined) => {
   const body = args as any;
-  return asTextContentResult(await client.v1.customers.commits.create(body));
+  try {
+    return asTextContentResult(await client.v1.customers.commits.create(body));
+  } catch (error) {
+    if (error instanceof Metronome.APIError) {
+      return asErrorResult(error.message);
+    }
+    throw error;
+  }
 };
 
 export default { metadata, tool, handler };

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

@@ -1,6 +1,6 @@
 // File generated from our OpenAPI spec by Stainless. See CONTRIBUTING.md for details.
 
-import { Metadata, asTextContentResult } from '@metronome/mcp/tools/types';
+import { Metadata, asErrorResult, asTextContentResult } from '@metronome/mcp/tools/types';
 
 import { Tool } from '@modelcontextprotocol/sdk/types.js';
 import Metronome from '@metronome/sdk';
@@ -77,7 +77,14 @@ export const tool: Tool = {
 export const handler = async (client: Metronome, args: Record<string, unknown> | undefined) => {
   const body = args as any;
   const response = await client.v1.customers.commits.list(body).asResponse();
-  return asTextContentResult(await response.json());
+  try {
+    return asTextContentResult(await response.json());
+  } catch (error) {
+    if (error instanceof Metronome.APIError) {
+      return asErrorResult(error.message);
+    }
+    throw error;
+  }
 };
 
 export default { metadata, tool, handler };

package/src/tools/v1/customers/commits/update-end-date-customers-v1-commits.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';
@@ -56,9 +56,16 @@ 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.customers.commits.updateEndDate(body)),
-  );
+  try {
+    return asTextContentResult(
+      await maybeFilter(jq_filter, await client.v1.customers.commits.updateEndDate(body)),
+    );
+  } catch (error) {
+    if (error instanceof Metronome.APIError || isJqError(error)) {
+      return asErrorResult(error.message);
+    }
+    throw error;
+  }
 };
 
 export default { metadata, tool, handler };