@metronome/mcp 2.2.0 → 3.4.1

package/src/tools/v1/billable-metrics/archive-v1-billable-metrics.ts

@@ -1,52 +0,0 @@
-// File generated from our OpenAPI spec by Stainless. See CONTRIBUTING.md for details.
-
-import { isJqError, maybeFilter } from '@metronome/mcp/filtering';
-import { Metadata, asErrorResult, asTextContentResult } from '@metronome/mcp/tools/types';
-
-import { Tool } from '@modelcontextprotocol/sdk/types.js';
-import Metronome from '@metronome/sdk';
-
-export const metadata: Metadata = {
-  resource: 'v1.billable_metrics',
-  operation: 'write',
-  tags: [],
-  httpMethod: 'post',
-  httpPath: '/v1/billable-metrics/archive',
-  operationId: 'archiveBillableMetric-v1',
-};
-
-export const tool: Tool = {
-  name: 'archive_v1_billable_metrics',
-  description:
-    "When using this tool, always use the `jq_filter` parameter to reduce the response size and improve performance.\n\nOnly omit if you're sure you don't need the data.\n\nUse this endpoint to retire billable metrics that are no longer used. After a billable metric is archived, that billable metric can no longer be used in any new Products to define how that product should be metered. If you archive a billable metric that is already associated with a Product, the Product will continue to function as usual, metering based on the definition of the archived billable metric. \n\nArchived billable metrics will be returned on the `getBillableMetric` and `listBillableMetrics` endpoints with a populated `archived_at` field.\n\n\n# Response Schema\n```json\n{\n  $ref: '#/$defs/billable_metric_archive_response',\n  $defs: {\n    billable_metric_archive_response: {\n      type: 'object',\n      properties: {\n        data: {\n          $ref: '#/$defs/id'\n        }\n      },\n      required: [        'data'\n      ]\n    },\n    id: {\n      type: 'object',\n      properties: {\n        id: {\n          type: 'string'\n        }\n      },\n      required: [        'id'\n      ]\n    }\n  }\n}\n```",
-  inputSchema: {
-    type: 'object',
-    properties: {
-      id: {
-        type: 'string',
-      },
-      jq_filter: {
-        type: 'string',
-        title: 'jq Filter',
-        description:
-          'A jq filter to apply to the response to include certain fields. Consult the output schema in the tool description to see the fields that are available.\n\nFor example: to include only the `name` field in every object of a results array, you can provide ".results[].name".\n\nFor more information, see the [jq documentation](https://jqlang.org/manual/).',
-      },
-    },
-    required: ['id'],
-  },
-  annotations: {},
-};
-
-export const handler = async (client: Metronome, args: Record<string, unknown> | undefined) => {
-  const { jq_filter, ...body } = args as any;
-  try {
-    return asTextContentResult(await maybeFilter(jq_filter, await client.v1.billableMetrics.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/billable-metrics/create-v1-billable-metrics.ts

@@ -1,150 +0,0 @@
-// File generated from our OpenAPI spec by Stainless. See CONTRIBUTING.md for details.
-
-import { isJqError, maybeFilter } from '@metronome/mcp/filtering';
-import { Metadata, asErrorResult, asTextContentResult } from '@metronome/mcp/tools/types';
-
-import { Tool } from '@modelcontextprotocol/sdk/types.js';
-import Metronome from '@metronome/sdk';
-
-export const metadata: Metadata = {
-  resource: 'v1.billable_metrics',
-  operation: 'write',
-  tags: [],
-  httpMethod: 'post',
-  httpPath: '/v1/billable-metrics/create',
-  operationId: 'createBillableMetricV1-v1',
-};
-
-export const tool: Tool = {
-  name: 'create_v1_billable_metrics',
-  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\nCreate billable metrics programmatically with this endpoint—an essential step in configuring your pricing and packaging in Metronome.\n\nA billable metric is a customizable query that filters and aggregates events from your event stream. These metrics are continuously tracked as usage data enters Metronome through the ingestion pipeline. The ingestion process transforms raw usage data into actionable pricing metrics, enabling accurate metering and billing for your products.\n\n### Use this endpoint to: \n- Create individual or multiple billable metrics as part of a setup workflow.\n- Automate the entire pricing configuration process, from metric creation to customer contract setup.\n- Define metrics using either standard filtering/aggregation or a custom SQL query.\n\n### Key response fields: \n- The ID of the billable metric that was created\n- The created billable metric will be available to be used in Products, usage endpoints, and alerts. \n\n### Usage guidelines: \n- Metrics defined using standard filtering and aggregation are Streaming billable metrics, which have been optimized for ultra low latency and high throughput workflows. \n- Use SQL billable metrics if you require more flexible aggregation options.\n\n\n# Response Schema\n```json\n{\n  $ref: '#/$defs/billable_metric_create_response',\n  $defs: {\n    billable_metric_create_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: {
-      name: {
-        type: 'string',
-        description: 'The display name of the billable metric.',
-      },
-      aggregation_key: {
-        type: 'string',
-        description:
-          'Specifies the type of aggregation performed on matching events. Required if `sql` is not provided.',
-      },
-      aggregation_type: {
-        type: 'string',
-        description: 'Specifies the type of aggregation performed on matching events.',
-        enum: ['COUNT', 'LATEST', 'MAX', 'SUM', 'UNIQUE'],
-      },
-      custom_fields: {
-        type: 'object',
-        description: 'Custom fields to attach to the billable metric.',
-        additionalProperties: true,
-      },
-      event_type_filter: {
-        $ref: '#/$defs/event_type_filter',
-      },
-      group_keys: {
-        type: 'array',
-        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.',
-        items: {
-          type: 'array',
-          items: {
-            type: 'string',
-          },
-        },
-      },
-      property_filters: {
-        type: 'array',
-        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.',
-        items: {
-          $ref: '#/$defs/property_filter',
-        },
-      },
-      sql: {
-        type: 'string',
-        description:
-          'The SQL query associated with the billable metric. This field is mutually exclusive with aggregation_type, event_type_filter, property_filters, aggregation_key, and group_keys. If provided, these other fields must be omitted.',
-      },
-      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: ['name'],
-    $defs: {
-      event_type_filter: {
-        type: 'object',
-        description: "An optional filtering rule to match the 'event_type' property of an event.",
-        properties: {
-          in_values: {
-            type: 'array',
-            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.',
-            items: {
-              type: 'string',
-            },
-          },
-          not_in_values: {
-            type: 'array',
-            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.',
-            items: {
-              type: 'string',
-            },
-          },
-        },
-      },
-      property_filter: {
-        type: 'object',
-        properties: {
-          name: {
-            type: 'string',
-            description: 'The name of the event property.',
-          },
-          exists: {
-            type: 'boolean',
-            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.',
-          },
-          in_values: {
-            type: 'array',
-            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.',
-            items: {
-              type: 'string',
-            },
-          },
-          not_in_values: {
-            type: 'array',
-            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.',
-            items: {
-              type: 'string',
-            },
-          },
-        },
-        required: ['name'],
-      },
-    },
-  },
-  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.billableMetrics.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/billable-metrics/list-v1-billable-metrics.ts

@@ -1,64 +0,0 @@
-// File generated from our OpenAPI spec by Stainless. See CONTRIBUTING.md for details.
-
-import { isJqError, maybeFilter } from '@metronome/mcp/filtering';
-import { Metadata, asErrorResult, asTextContentResult } from '@metronome/mcp/tools/types';
-
-import { Tool } from '@modelcontextprotocol/sdk/types.js';
-import Metronome from '@metronome/sdk';
-
-export const metadata: Metadata = {
-  resource: 'v1.billable_metrics',
-  operation: 'read',
-  tags: [],
-  httpMethod: 'get',
-  httpPath: '/v1/billable-metrics',
-  operationId: 'listAllBillableMetrics-v1',
-};
-
-export const tool: Tool = {
-  name: 'list_v1_billable_metrics',
-  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\nRetrieves all billable metrics with their complete configurations. Use this for programmatic discovery and management of billable metrics, such as associating metrics to products and auditing for orphaned or archived metrics. \nImportant: Archived metrics are excluded by default; use `include_archived`=`true` parameter to include them.\n\n\n# Response Schema\n```json\n{\n  type: 'object',\n  properties: {\n    data: {\n      type: 'array',\n      items: {\n        $ref: '#/$defs/billable_metric_list_response'\n      }\n    },\n    next_page: {\n      type: 'string'\n    }\n  },\n  required: [    'data',\n    'next_page'\n  ],\n  $defs: {\n    billable_metric_list_response: {\n      type: 'object',\n      properties: {\n        id: {\n          type: 'string',\n          description: 'ID of the billable metric'\n        },\n        name: {\n          type: 'string',\n          description: 'The display name of the billable metric.'\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        group_keys: {\n          type: 'array',\n          description: 'Property names that are used to group usage costs on an invoice. Each entry represents a set of properties used to slice events into distinct buckets.',\n          items: {\n            type: 'array',\n            items: {\n              type: 'string'\n            }\n          }\n        },\n        property_filters: {\n          type: 'array',\n          description: 'A list of filters to match events to this billable metric. Each filter defines a rule on an event property. All rules must pass for the event to match the billable metric.',\n          items: {\n            $ref: '#/$defs/property_filter'\n          }\n        },\n        sql: {\n          type: 'string',\n          description: 'The SQL query associated with the billable metric'\n        }\n      },\n      required: [        'id',\n        'name'\n      ]\n    },\n    event_type_filter: {\n      type: 'object',\n      description: 'An optional filtering rule to match the \\'event_type\\' property of an event.',\n      properties: {\n        in_values: {\n          type: 'array',\n          description: 'A list of event types that are explicitly included in the billable metric. If specified, only events of these types will match the billable metric. Must be non-empty if present.',\n          items: {\n            type: 'string'\n          }\n        },\n        not_in_values: {\n          type: 'array',\n          description: 'A list of event types that are explicitly excluded from the billable metric. If specified, events of these types will not match the billable metric. Must be non-empty if present.',\n          items: {\n            type: 'string'\n          }\n        }\n      }\n    },\n    property_filter: {\n      type: 'object',\n      properties: {\n        name: {\n          type: 'string',\n          description: 'The name of the event property.'\n        },\n        exists: {\n          type: 'boolean',\n          description: 'Determines whether the property must exist in the event. If true, only events with this property will pass the filter. If false, only events without this property will pass the filter. If null or omitted, the existence of the property is optional.'\n        },\n        in_values: {\n          type: 'array',\n          description: 'Specifies the allowed values for the property to match an event. An event will pass the filter only if its property value is included in this list. If undefined, all property values will pass the filter. Must be non-empty if present.',\n          items: {\n            type: 'string'\n          }\n        },\n        not_in_values: {\n          type: 'array',\n          description: 'Specifies the values that prevent an event from matching the filter. An event will not pass the filter if its property value is included in this list. If null or empty, all property values will pass the filter. Must be non-empty if present.',\n          items: {\n            type: 'string'\n          }\n        }\n      },\n      required: [        'name'\n      ]\n    }\n  }\n}\n```",
-  inputSchema: {
-    type: 'object',
-    properties: {
-      include_archived: {
-        type: 'boolean',
-        description: 'If true, the list of returned metrics will include archived metrics',
-      },
-      limit: {
-        type: 'integer',
-        description: 'Max number of results that should be returned',
-      },
-      next_page: {
-        type: 'string',
-        description: 'Cursor that indicates where the next page of results should start.',
-      },
-      jq_filter: {
-        type: 'string',
-        title: 'jq Filter',
-        description:
-          'A jq filter to apply to the response to include certain fields. Consult the output schema in the tool description to see the fields that are available.\n\nFor example: to include only the `name` field in every object of a results array, you can provide ".results[].name".\n\nFor more information, see the [jq documentation](https://jqlang.org/manual/).',
-      },
-    },
-    required: [],
-  },
-  annotations: {
-    readOnlyHint: true,
-  },
-};
-
-export const handler = async (client: Metronome, args: Record<string, unknown> | undefined) => {
-  const { jq_filter, ...body } = args as any;
-  const response = await client.v1.billableMetrics.list(body).asResponse();
-  try {
-    return asTextContentResult(await maybeFilter(jq_filter, await response.json()));
-  } catch (error) {
-    if (error instanceof Metronome.APIError || isJqError(error)) {
-      return asErrorResult(error.message);
-    }
-    throw error;
-  }
-};
-
-export default { metadata, tool, handler };

package/src/tools/v1/billable-metrics/retrieve-v1-billable-metrics.ts

@@ -1,54 +0,0 @@
-// File generated from our OpenAPI spec by Stainless. See CONTRIBUTING.md for details.
-
-import { isJqError, maybeFilter } from '@metronome/mcp/filtering';
-import { Metadata, asErrorResult, asTextContentResult } from '@metronome/mcp/tools/types';
-
-import { Tool } from '@modelcontextprotocol/sdk/types.js';
-import Metronome from '@metronome/sdk';
-
-export const metadata: Metadata = {
-  resource: 'v1.billable_metrics',
-  operation: 'read',
-  tags: [],
-  httpMethod: 'get',
-  httpPath: '/v1/billable-metrics/{billable_metric_id}',
-  operationId: 'getBillableMetric-v1',
-};
-
-export const tool: Tool = {
-  name: 'retrieve_v1_billable_metrics',
-  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\nRetrieves the complete configuration for a specific billable metric by its ID. Use this to review billable metric setup before associating it with products. Returns the metric's `name`, `event_type_filter`, `property_filters`, `aggregation_type`, `aggregation_key`, `group_keys`, `custom fields`, and `SQL query` (if it's a SQL billable metric). \n\nImportant: \n- Archived billable metrics will include an `archived_at` timestamp; they no longer process new usage events but remain accessible for historical reference.\n\n\n# Response Schema\n```json\n{\n  $ref: '#/$defs/billable_metric_retrieve_response',\n  $defs: {\n    billable_metric_retrieve_response: {\n      type: 'object',\n      properties: {\n        data: {\n          type: 'object',\n          properties: {\n            id: {\n              type: 'string',\n              description: 'ID of the billable metric'\n            },\n            name: {\n              type: 'string',\n              description: 'The display name of the billable metric.'\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            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      required: [        'data'\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: {
-      billable_metric_id: {
-        type: 'string',
-      },
-      jq_filter: {
-        type: 'string',
-        title: 'jq Filter',
-        description:
-          'A jq filter to apply to the response to include certain fields. Consult the output schema in the tool description to see the fields that are available.\n\nFor example: to include only the `name` field in every object of a results array, you can provide ".results[].name".\n\nFor more information, see the [jq documentation](https://jqlang.org/manual/).',
-      },
-    },
-    required: ['billable_metric_id'],
-  },
-  annotations: {
-    readOnlyHint: true,
-  },
-};
-
-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.billableMetrics.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/contracts/add-manual-balance-entry-v1-contracts.ts

@@ -1,72 +0,0 @@
-// File generated from our OpenAPI spec by Stainless. See CONTRIBUTING.md for details.
-
-import { Metadata, asTextContentResult } from '@metronome/mcp/tools/types';
-
-import { Tool } from '@modelcontextprotocol/sdk/types.js';
-import Metronome from '@metronome/sdk';
-
-export const metadata: Metadata = {
-  resource: 'v1.contracts',
-  operation: 'write',
-  tags: [],
-  httpMethod: 'post',
-  httpPath: '/v1/contracts/addManualBalanceLedgerEntry',
-  operationId: 'addManualBalanceLedgerEntry-v1',
-};
-
-export const tool: Tool = {
-  name: 'add_manual_balance_entry_v1_contracts',
-  description:
-    'Manually adjust the available balance on a commit or credit. This entry is appended to the commit ledger as a new event. Optionally include a description that provides the reasoning for the entry.\n\n### Use this endpoint to:\n- Address incorrect usage burn-down caused by malformed usage or invalid config\n- Decrease available balance to account for outages where usage may have not been tracked or sent to Metronome\n- Issue credits to customers in the form of increased balance on existing commit or credit\n\n### Usage guidelines:\nManual ledger entries can be extremely useful for resolving discrepancies in Metronome. However, most corrections to inaccurate billings can be modified upstream of the commit, whether that is via contract editing, rate editing, or other actions that cause an invoice to be recalculated.\n',
-  inputSchema: {
-    type: 'object',
-    properties: {
-      id: {
-        type: 'string',
-        description: 'ID of the balance (commit or credit) to update.',
-      },
-      amount: {
-        type: 'number',
-        description: 'Amount to add to the segment. A negative number will draw down from the balance.',
-      },
-      customer_id: {
-        type: 'string',
-        description: 'ID of the customer whose balance is to be updated.',
-      },
-      reason: {
-        type: 'string',
-        description: 'Reason for the manual adjustment. This will be displayed in the ledger.',
-      },
-      segment_id: {
-        type: 'string',
-        description: 'ID of the segment to update.',
-      },
-      contract_id: {
-        type: 'string',
-        description: 'ID of the contract to update. Leave blank to update a customer level balance.',
-      },
-      per_group_amounts: {
-        type: 'object',
-        description:
-          'If using individually configured commits/credits attached to seat managed subscriptions, the amount to add for each seat. Must sum to total amount.',
-        additionalProperties: true,
-      },
-      timestamp: {
-        type: 'string',
-        description:
-          'RFC 3339 timestamp indicating when the manual adjustment takes place. If not provided, it will default to the start of the segment.',
-        format: 'date-time',
-      },
-    },
-    required: ['id', 'amount', 'customer_id', 'reason', 'segment_id'],
-  },
-  annotations: {},
-};
-
-export const handler = async (client: Metronome, args: Record<string, unknown> | undefined) => {
-  const body = args as any;
-  const response = await client.v1.contracts.addManualBalanceEntry(body).asResponse();
-  return asTextContentResult(await response.text());
-};
-
-export default { metadata, tool, handler };