@tryfinch/finch-api-mcp 7.0.0 → 8.1.0

package/src/tools/hris/benefits/retrieve-hris-benefits.ts

@@ -1,63 +0,0 @@
-// File generated from our OpenAPI spec by Stainless. See CONTRIBUTING.md for details.
-
-import { isJqError, maybeFilter } from '@tryfinch/finch-api-mcp/filtering';
-import { Metadata, asErrorResult, asTextContentResult } from '@tryfinch/finch-api-mcp/tools/types';
-
-import { Tool } from '@modelcontextprotocol/sdk/types.js';
-import Finch from '@tryfinch/finch-api';
-
-export const metadata: Metadata = {
-  resource: 'hris.benefits',
-  operation: 'read',
-  tags: [],
-  httpMethod: 'get',
-  httpPath: '/employer/benefits/{benefit_id}',
-  operationId: 'get-company-benefit',
-};
-
-export const tool: Tool = {
-  name: 'retrieve_hris_benefits',
-  description:
-    "When using this tool, always use the `jq_filter` parameter to reduce the response size and improve performance.\n\nOnly omit if you're sure you don't need the data.\n\nLists deductions and contributions information for a given item\n\n# Response Schema\n```json\n{\n  $ref: '#/$defs/company_benefit',\n  $defs: {\n    company_benefit: {\n      type: 'object',\n      title: 'CompanyBenefit',\n      properties: {\n        benefit_id: {\n          type: 'string',\n          description: 'The id of the benefit.'\n        },\n        description: {\n          type: 'string'\n        },\n        frequency: {\n          $ref: '#/$defs/benefit_frequency'\n        },\n        type: {\n          $ref: '#/$defs/benefit_type'\n        },\n        company_contribution: {\n          type: 'object',\n          title: 'BenefitCompanyMatchContribution',\n          description: 'The company match for this benefit.',\n          properties: {\n            tiers: {\n              type: 'array',\n              items: {\n                type: 'object',\n                properties: {\n                  match: {\n                    type: 'integer'\n                  },\n                  threshold: {\n                    type: 'integer'\n                  }\n                },\n                required: [                  'match',\n                  'threshold'\n                ]\n              }\n            },\n            type: {\n              type: 'string',\n              enum: [                'match'\n              ]\n            }\n          },\n          required: [            'tiers',\n            'type'\n          ]\n        }\n      },\n      required: [        'benefit_id',\n        'description',\n        'frequency',\n        'type'\n      ]\n    },\n    benefit_frequency: {\n      type: 'string',\n      title: 'BenefitFrequency',\n      description: 'The frequency of the benefit deduction/contribution.',\n      enum: [        'every_paycheck',\n        'monthly',\n        'one_time'\n      ]\n    },\n    benefit_type: {\n      type: 'string',\n      title: 'BenefitType',\n      description: 'Type of benefit.',\n      enum: [        '457',\n        '401k',\n        '401k_roth',\n        '401k_loan',\n        '403b',\n        '403b_roth',\n        '457_roth',\n        'commuter',\n        'custom_post_tax',\n        'custom_pre_tax',\n        'fsa_dependent_care',\n        'fsa_medical',\n        'hsa_post',\n        'hsa_pre',\n        's125_dental',\n        's125_medical',\n        's125_vision',\n        'simple',\n        'simple_ira'\n      ]\n    }\n  }\n}\n```",
-  inputSchema: {
-    type: 'object',
-    properties: {
-      benefit_id: {
-        type: 'string',
-      },
-      entity_ids: {
-        type: 'array',
-        description: "The entity IDs to specify which entities' data to access.",
-        items: {
-          type: 'string',
-        },
-      },
-      jq_filter: {
-        type: 'string',
-        title: 'jq Filter',
-        description:
-          'A jq filter to apply to the response to include certain fields. Consult the output schema in the tool description to see the fields that are available.\n\nFor example: to include only the `name` field in every object of a results array, you can provide ".results[].name".\n\nFor more information, see the [jq documentation](https://jqlang.org/manual/).',
-      },
-    },
-    required: ['benefit_id'],
-  },
-  annotations: {
-    readOnlyHint: true,
-  },
-};
-
-export const handler = async (client: Finch, args: Record<string, unknown> | undefined) => {
-  const { benefit_id, jq_filter, ...body } = args as any;
-  try {
-    return asTextContentResult(
-      await maybeFilter(jq_filter, await client.hris.benefits.retrieve(benefit_id, body)),
-    );
-  } catch (error) {
-    if (error instanceof Finch.APIError || isJqError(error)) {
-      return asErrorResult(error.message);
-    }
-    throw error;
-  }
-};
-
-export default { metadata, tool, handler };

package/src/tools/hris/benefits/update-hris-benefits.ts

@@ -1,65 +0,0 @@
-// File generated from our OpenAPI spec by Stainless. See CONTRIBUTING.md for details.
-
-import { isJqError, maybeFilter } from '@tryfinch/finch-api-mcp/filtering';
-import { Metadata, asErrorResult, asTextContentResult } from '@tryfinch/finch-api-mcp/tools/types';
-
-import { Tool } from '@modelcontextprotocol/sdk/types.js';
-import Finch from '@tryfinch/finch-api';
-
-export const metadata: Metadata = {
-  resource: 'hris.benefits',
-  operation: 'write',
-  tags: [],
-  httpMethod: 'post',
-  httpPath: '/employer/benefits/{benefit_id}',
-  operationId: 'update-company-benefits',
-};
-
-export const tool: Tool = {
-  name: 'update_hris_benefits',
-  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\nUpdates an existing company-wide deduction or contribution\n\n# Response Schema\n```json\n{\n  $ref: '#/$defs/update_company_benefit_response',\n  $defs: {\n    update_company_benefit_response: {\n      type: 'object',\n      properties: {\n        benefit_id: {\n          type: 'string',\n          description: 'The id of the benefit.'\n        },\n        job_id: {\n          type: 'string'\n        }\n      },\n      required: [        'benefit_id',\n        'job_id'\n      ]\n    }\n  }\n}\n```",
-  inputSchema: {
-    type: 'object',
-    properties: {
-      benefit_id: {
-        type: 'string',
-      },
-      entity_ids: {
-        type: 'array',
-        description: "The entity IDs to specify which entities' data to access.",
-        items: {
-          type: 'string',
-        },
-      },
-      description: {
-        type: 'string',
-        description: 'Updated name or description.',
-      },
-      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: ['benefit_id'],
-  },
-  annotations: {},
-};
-
-export const handler = async (client: Finch, args: Record<string, unknown> | undefined) => {
-  const { benefit_id, jq_filter, ...body } = args as any;
-  try {
-    return asTextContentResult(
-      await maybeFilter(jq_filter, await client.hris.benefits.update(benefit_id, body)),
-    );
-  } catch (error) {
-    if (error instanceof Finch.APIError || isJqError(error)) {
-      return asErrorResult(error.message);
-    }
-    throw error;
-  }
-};
-
-export default { metadata, tool, handler };

package/src/tools/hris/company/pay-statement-item/list-company-hris-pay-statement-item.ts

@@ -1,88 +0,0 @@
-// File generated from our OpenAPI spec by Stainless. See CONTRIBUTING.md for details.
-
-import { isJqError, maybeFilter } from '@tryfinch/finch-api-mcp/filtering';
-import { Metadata, asErrorResult, asTextContentResult } from '@tryfinch/finch-api-mcp/tools/types';
-
-import { Tool } from '@modelcontextprotocol/sdk/types.js';
-import Finch from '@tryfinch/finch-api';
-
-export const metadata: Metadata = {
-  resource: 'hris.company.pay_statement_item',
-  operation: 'read',
-  tags: [],
-  httpMethod: 'get',
-  httpPath: '/employer/pay-statement-item',
-  operationId: 'get-pay-statement-item',
-};
-
-export const tool: Tool = {
-  name: 'list_company_hris_pay_statement_item',
-  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\n**Beta:** this endpoint currently serves employers onboarded after March 4th and historical support will be added soon\n Retrieve a list of detailed pay statement items for the access token's connection account.\n\n\n# Response Schema\n```json\n{\n  type: 'object',\n  properties: {\n    responses: {\n      type: 'array',\n      items: {\n        $ref: '#/$defs/pay_statement_item_list_response'\n      }\n    }\n  },\n  required: [    'responses'\n  ],\n  $defs: {\n    pay_statement_item_list_response: {\n      type: 'object',\n      properties: {\n        attributes: {\n          type: 'object',\n          description: 'The attributes of the pay statement item.',\n          properties: {\n            metadata: {\n              type: 'object',\n              description: 'The metadata of the pay statement item derived by the rules engine if available. Each attribute will be a key-value pair defined by a rule.',\n              additionalProperties: true\n            },\n            employer: {\n              type: 'boolean',\n              description: '`true` if the amount is paid by the employers. This field is only available for taxes.'\n            },\n            pre_tax: {\n              type: 'boolean',\n              description: '`true` if the pay statement item is pre-tax. This field is only available for employee deductions.'\n            },\n            type: {\n              type: 'string',\n              description: 'The type of the pay statement item.'\n            }\n          },\n          required: [            'metadata'\n          ]\n        },\n        category: {\n          type: 'string',\n          description: 'The category of the pay statement item.',\n          enum: [            'earnings',\n            'taxes',\n            'employee_deductions',\n            'employer_contributions'\n          ]\n        },\n        name: {\n          type: 'string',\n          description: 'The name of the pay statement item.'\n        }\n      },\n      required: [        'attributes',\n        'category',\n        'name'\n      ]\n    }\n  }\n}\n```",
-  inputSchema: {
-    type: 'object',
-    properties: {
-      categories: {
-        type: 'array',
-        description:
-          'Comma-delimited list of pay statement item categories to filter on. If empty, defaults to all categories.',
-        items: {
-          type: 'string',
-          enum: ['earnings', 'taxes', 'employee_deductions', 'employer_contributions'],
-        },
-      },
-      end_date: {
-        type: 'string',
-        description:
-          'The end date to retrieve pay statement items by via their last seen pay date in `YYYY-MM-DD` format.',
-        format: 'date',
-      },
-      entity_ids: {
-        type: 'array',
-        description: "The entity IDs to specify which entities' data to access.",
-        items: {
-          type: 'string',
-        },
-      },
-      name: {
-        type: 'string',
-        description: 'Case-insensitive partial match search by pay statement item name.',
-      },
-      start_date: {
-        type: 'string',
-        description:
-          'The start date to retrieve pay statement items by via their last seen pay date (inclusive) in `YYYY-MM-DD` format.',
-        format: 'date',
-      },
-      type: {
-        type: 'string',
-        description: 'String search by pay statement item type.',
-      },
-      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: Finch, args: Record<string, unknown> | undefined) => {
-  const { jq_filter, ...body } = args as any;
-  const response = await client.hris.company.payStatementItem.list(body).asResponse();
-  try {
-    return asTextContentResult(await maybeFilter(jq_filter, await response.json()));
-  } catch (error) {
-    if (error instanceof Finch.APIError || isJqError(error)) {
-      return asErrorResult(error.message);
-    }
-    throw error;
-  }
-};
-
-export default { metadata, tool, handler };

package/src/tools/hris/company/pay-statement-item/rules/create-pay-statement-item-company-hris-rules.ts

@@ -1,106 +0,0 @@
-// File generated from our OpenAPI spec by Stainless. See CONTRIBUTING.md for details.
-
-import { isJqError, maybeFilter } from '@tryfinch/finch-api-mcp/filtering';
-import { Metadata, asErrorResult, asTextContentResult } from '@tryfinch/finch-api-mcp/tools/types';
-
-import { Tool } from '@modelcontextprotocol/sdk/types.js';
-import Finch from '@tryfinch/finch-api';
-
-export const metadata: Metadata = {
-  resource: 'hris.company.pay_statement_item.rules',
-  operation: 'write',
-  tags: [],
-  httpMethod: 'post',
-  httpPath: '/employer/pay-statement-item/rule',
-  operationId: 'create-rule',
-};
-
-export const tool: Tool = {
-  name: 'create_pay_statement_item_company_hris_rules',
-  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\n**Beta:** this endpoint currently serves employers onboarded after March 4th and historical support will be added soon\nCustom rules can be created to associate specific attributes to pay statement items depending on the use case. For example, pay statement items that meet certain conditions can be labeled as a pre-tax 401k. This metadata can be retrieved where pay statement item information is available.\n\n\n# Response Schema\n```json\n{\n  $ref: '#/$defs/rule_create_response',\n  $defs: {\n    rule_create_response: {\n      type: 'object',\n      properties: {\n        id: {\n          type: 'string',\n          description: 'Finch id (uuidv4) for the rule.'\n        },\n        attributes: {\n          type: 'object',\n          description: 'Specifies the fields to be applied when the condition is met.',\n          properties: {\n            metadata: {\n              type: 'object',\n              description: 'The metadata to be attached in the entity. It is a key-value pairs where the values can be of any type (string, number, boolean, object, array, etc.).',\n              additionalProperties: true\n            }\n          }\n        },\n        conditions: {\n          type: 'array',\n          items: {\n            type: 'object',\n            properties: {\n              field: {\n                type: 'string',\n                description: 'The field to be checked in the rule.'\n              },\n              operator: {\n                type: 'string',\n                description: 'The operator to be used in the rule.',\n                enum: [                  'equals'\n                ]\n              },\n              value: {\n                type: 'string',\n                description: 'The value of the field to be checked in the rule.'\n              }\n            }\n          }\n        },\n        created_at: {\n          type: 'string',\n          description: 'The datetime when the rule was created.',\n          format: 'date-time'\n        },\n        effective_end_date: {\n          type: 'string',\n          title: 'Date',\n          description: 'Specifies when the rules should stop applying rules based on the date.'\n        },\n        effective_start_date: {\n          type: 'string',\n          title: 'Date',\n          description: 'Specifies when the rule should begin applying based on the date.'\n        },\n        entity_type: {\n          type: 'string',\n          description: 'The entity type to which the rule is applied.',\n          enum: [            'pay_statement_item'\n          ]\n        },\n        priority: {\n          type: 'integer',\n          description: 'The priority of the rule.'\n        },\n        updated_at: {\n          type: 'string',\n          description: 'The datetime when the rule was last updated.',\n          format: 'date-time'\n        }\n      }\n    }\n  }\n}\n```",
-  inputSchema: {
-    type: 'object',
-    properties: {
-      entity_ids: {
-        type: 'array',
-        description: 'The entity IDs to create the rule for.',
-        items: {
-          type: 'string',
-        },
-      },
-      attributes: {
-        type: 'object',
-        description: 'Specifies the fields to be applied when the condition is met.',
-        properties: {
-          metadata: {
-            type: 'object',
-            description:
-              'The metadata to be attached in the entity. It is a key-value pairs where the values can be of any type (string, number, boolean, object, array, etc.).',
-            additionalProperties: true,
-          },
-        },
-      },
-      conditions: {
-        type: 'array',
-        items: {
-          type: 'object',
-          properties: {
-            field: {
-              type: 'string',
-              description: 'The field to be checked in the rule.',
-            },
-            operator: {
-              type: 'string',
-              description: 'The operator to be used in the rule.',
-              enum: ['equals'],
-            },
-            value: {
-              type: 'string',
-              description: 'The value of the field to be checked in the rule.',
-            },
-          },
-        },
-      },
-      effective_end_date: {
-        type: 'string',
-        title: 'Date',
-        description: 'Specifies when the rules should stop applying rules based on the date.',
-      },
-      effective_start_date: {
-        type: 'string',
-        title: 'Date',
-        description: 'Specifies when the rule should begin applying based on the date.',
-      },
-      entity_type: {
-        type: 'string',
-        description: 'The entity type to which the rule is applied.',
-        enum: ['pay_statement_item'],
-      },
-      jq_filter: {
-        type: 'string',
-        title: 'jq Filter',
-        description:
-          'A jq filter to apply to the response to include certain fields. Consult the output schema in the tool description to see the fields that are available.\n\nFor example: to include only the `name` field in every object of a results array, you can provide ".results[].name".\n\nFor more information, see the [jq documentation](https://jqlang.org/manual/).',
-      },
-    },
-    required: [],
-  },
-  annotations: {},
-};
-
-export const handler = async (client: Finch, args: Record<string, unknown> | undefined) => {
-  const { jq_filter, ...body } = args as any;
-  try {
-    return asTextContentResult(
-      await maybeFilter(jq_filter, await client.hris.company.payStatementItem.rules.create(body)),
-    );
-  } catch (error) {
-    if (error instanceof Finch.APIError || isJqError(error)) {
-      return asErrorResult(error.message);
-    }
-    throw error;
-  }
-};
-
-export default { metadata, tool, handler };

package/src/tools/hris/company/pay-statement-item/rules/delete-pay-statement-item-company-hris-rules.ts

@@ -1,63 +0,0 @@
-// File generated from our OpenAPI spec by Stainless. See CONTRIBUTING.md for details.
-
-import { isJqError, maybeFilter } from '@tryfinch/finch-api-mcp/filtering';
-import { Metadata, asErrorResult, asTextContentResult } from '@tryfinch/finch-api-mcp/tools/types';
-
-import { Tool } from '@modelcontextprotocol/sdk/types.js';
-import Finch from '@tryfinch/finch-api';
-
-export const metadata: Metadata = {
-  resource: 'hris.company.pay_statement_item.rules',
-  operation: 'write',
-  tags: [],
-  httpMethod: 'delete',
-  httpPath: '/employer/pay-statement-item/rule/{rule_id}',
-  operationId: 'delete-rule',
-};
-
-export const tool: Tool = {
-  name: 'delete_pay_statement_item_company_hris_rules',
-  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\n**Beta:** this endpoint currently serves employers onboarded after March 4th and historical support will be added soon\nDelete a rule for a pay statement item.\n\n\n# Response Schema\n```json\n{\n  $ref: '#/$defs/rule_delete_response',\n  $defs: {\n    rule_delete_response: {\n      type: 'object',\n      properties: {\n        id: {\n          type: 'string',\n          description: 'Finch id (uuidv4) for the rule.'\n        },\n        attributes: {\n          type: 'object',\n          description: 'Specifies the fields to be applied when the condition is met.',\n          properties: {\n            metadata: {\n              type: 'object',\n              description: 'The metadata to be attached in the entity. It is a key-value pairs where the values can be of any type (string, number, boolean, object, array, etc.).',\n              additionalProperties: true\n            }\n          }\n        },\n        conditions: {\n          type: 'array',\n          items: {\n            type: 'object',\n            properties: {\n              field: {\n                type: 'string',\n                description: 'The field to be checked in the rule.'\n              },\n              operator: {\n                type: 'string',\n                description: 'The operator to be used in the rule.',\n                enum: [                  'equals'\n                ]\n              },\n              value: {\n                type: 'string',\n                description: 'The value of the field to be checked in the rule.'\n              }\n            }\n          }\n        },\n        created_at: {\n          type: 'string',\n          description: 'The datetime when the rule was created.',\n          format: 'date-time'\n        },\n        deleted_at: {\n          type: 'string',\n          description: 'The datetime when the rule was deleted.',\n          format: 'date-time'\n        },\n        effective_end_date: {\n          type: 'string',\n          title: 'Date',\n          description: 'Specifies when the rules should stop applying rules based on the date.'\n        },\n        effective_start_date: {\n          type: 'string',\n          title: 'Date',\n          description: 'Specifies when the rule should begin applying based on the date.'\n        },\n        entity_type: {\n          type: 'string',\n          description: 'The entity type to which the rule is applied.',\n          enum: [            'pay_statement_item'\n          ]\n        },\n        priority: {\n          type: 'integer',\n          description: 'The priority of the rule.'\n        },\n        updated_at: {\n          type: 'string',\n          description: 'The datetime when the rule was last updated.',\n          format: 'date-time'\n        }\n      }\n    }\n  }\n}\n```",
-  inputSchema: {
-    type: 'object',
-    properties: {
-      rule_id: {
-        type: 'string',
-      },
-      entity_ids: {
-        type: 'array',
-        description: 'The entity IDs to delete the rule for.',
-        items: {
-          type: 'string',
-        },
-      },
-      jq_filter: {
-        type: 'string',
-        title: 'jq Filter',
-        description:
-          'A jq filter to apply to the response to include certain fields. Consult the output schema in the tool description to see the fields that are available.\n\nFor example: to include only the `name` field in every object of a results array, you can provide ".results[].name".\n\nFor more information, see the [jq documentation](https://jqlang.org/manual/).',
-      },
-    },
-    required: ['rule_id'],
-  },
-  annotations: {
-    idempotentHint: true,
-  },
-};
-
-export const handler = async (client: Finch, args: Record<string, unknown> | undefined) => {
-  const { rule_id, jq_filter, ...body } = args as any;
-  try {
-    return asTextContentResult(
-      await maybeFilter(jq_filter, await client.hris.company.payStatementItem.rules.delete(rule_id, body)),
-    );
-  } catch (error) {
-    if (error instanceof Finch.APIError || isJqError(error)) {
-      return asErrorResult(error.message);
-    }
-    throw error;
-  }
-};
-
-export default { metadata, tool, handler };

package/src/tools/hris/company/pay-statement-item/rules/list-pay-statement-item-company-hris-rules.ts

@@ -1,59 +0,0 @@
-// File generated from our OpenAPI spec by Stainless. See CONTRIBUTING.md for details.
-
-import { isJqError, maybeFilter } from '@tryfinch/finch-api-mcp/filtering';
-import { Metadata, asErrorResult, asTextContentResult } from '@tryfinch/finch-api-mcp/tools/types';
-
-import { Tool } from '@modelcontextprotocol/sdk/types.js';
-import Finch from '@tryfinch/finch-api';
-
-export const metadata: Metadata = {
-  resource: 'hris.company.pay_statement_item.rules',
-  operation: 'read',
-  tags: [],
-  httpMethod: 'get',
-  httpPath: '/employer/pay-statement-item/rule',
-  operationId: 'get-rules',
-};
-
-export const tool: Tool = {
-  name: 'list_pay_statement_item_company_hris_rules',
-  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\n**Beta:** this endpoint currently serves employers onboarded after March 4th and historical support will be added soon\nList all rules of a connection account.\n\n\n# Response Schema\n```json\n{\n  type: 'object',\n  properties: {\n    responses: {\n      type: 'array',\n      items: {\n        $ref: '#/$defs/rule_list_response'\n      }\n    }\n  },\n  required: [    'responses'\n  ],\n  $defs: {\n    rule_list_response: {\n      type: 'object',\n      properties: {\n        id: {\n          type: 'string',\n          description: 'Finch id (uuidv4) for the rule.'\n        },\n        attributes: {\n          type: 'object',\n          description: 'Specifies the fields to be applied when the condition is met.',\n          properties: {\n            metadata: {\n              type: 'object',\n              description: 'The metadata to be attached in the entity. It is a key-value pairs where the values can be of any type (string, number, boolean, object, array, etc.).',\n              additionalProperties: true\n            }\n          }\n        },\n        conditions: {\n          type: 'array',\n          items: {\n            type: 'object',\n            properties: {\n              field: {\n                type: 'string',\n                description: 'The field to be checked in the rule.'\n              },\n              operator: {\n                type: 'string',\n                description: 'The operator to be used in the rule.',\n                enum: [                  'equals'\n                ]\n              },\n              value: {\n                type: 'string',\n                description: 'The value of the field to be checked in the rule.'\n              }\n            }\n          }\n        },\n        created_at: {\n          type: 'string',\n          description: 'The datetime when the rule was created.',\n          format: 'date-time'\n        },\n        effective_end_date: {\n          type: 'string',\n          title: 'Date',\n          description: 'Specifies when the rules should stop applying rules based on the date.'\n        },\n        effective_start_date: {\n          type: 'string',\n          title: 'Date',\n          description: 'Specifies when the rule should begin applying based on the date.'\n        },\n        entity_type: {\n          type: 'string',\n          description: 'The entity type to which the rule is applied.',\n          enum: [            'pay_statement_item'\n          ]\n        },\n        priority: {\n          type: 'integer',\n          description: 'The priority of the rule.'\n        },\n        updated_at: {\n          type: 'string',\n          description: 'The datetime when the rule was last updated.',\n          format: 'date-time'\n        }\n      }\n    }\n  }\n}\n```",
-  inputSchema: {
-    type: 'object',
-    properties: {
-      entity_ids: {
-        type: 'array',
-        description: 'The entity IDs to retrieve rules for.',
-        items: {
-          type: 'string',
-        },
-      },
-      jq_filter: {
-        type: 'string',
-        title: 'jq Filter',
-        description:
-          'A jq filter to apply to the response to include certain fields. Consult the output schema in the tool description to see the fields that are available.\n\nFor example: to include only the `name` field in every object of a results array, you can provide ".results[].name".\n\nFor more information, see the [jq documentation](https://jqlang.org/manual/).',
-      },
-    },
-    required: [],
-  },
-  annotations: {
-    readOnlyHint: true,
-  },
-};
-
-export const handler = async (client: Finch, args: Record<string, unknown> | undefined) => {
-  const { jq_filter, ...body } = args as any;
-  const response = await client.hris.company.payStatementItem.rules.list(body).asResponse();
-  try {
-    return asTextContentResult(await maybeFilter(jq_filter, await response.json()));
-  } catch (error) {
-    if (error instanceof Finch.APIError || isJqError(error)) {
-      return asErrorResult(error.message);
-    }
-    throw error;
-  }
-};
-
-export default { metadata, tool, handler };

package/src/tools/hris/company/pay-statement-item/rules/update-pay-statement-item-company-hris-rules.ts

@@ -1,67 +0,0 @@
-// File generated from our OpenAPI spec by Stainless. See CONTRIBUTING.md for details.
-
-import { isJqError, maybeFilter } from '@tryfinch/finch-api-mcp/filtering';
-import { Metadata, asErrorResult, asTextContentResult } from '@tryfinch/finch-api-mcp/tools/types';
-
-import { Tool } from '@modelcontextprotocol/sdk/types.js';
-import Finch from '@tryfinch/finch-api';
-
-export const metadata: Metadata = {
-  resource: 'hris.company.pay_statement_item.rules',
-  operation: 'write',
-  tags: [],
-  httpMethod: 'put',
-  httpPath: '/employer/pay-statement-item/rule/{rule_id}',
-  operationId: 'update-rule',
-};
-
-export const tool: Tool = {
-  name: 'update_pay_statement_item_company_hris_rules',
-  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\n**Beta:** this endpoint currently serves employers onboarded after March 4th and historical support will be added soon\nUpdate a rule for a pay statement item.\n\n\n# Response Schema\n```json\n{\n  $ref: '#/$defs/rule_update_response',\n  $defs: {\n    rule_update_response: {\n      type: 'object',\n      properties: {\n        id: {\n          type: 'string',\n          description: 'Finch id (uuidv4) for the rule.'\n        },\n        attributes: {\n          type: 'object',\n          description: 'Specifies the fields to be applied when the condition is met.',\n          properties: {\n            metadata: {\n              type: 'object',\n              description: 'The metadata to be attached in the entity. It is a key-value pairs where the values can be of any type (string, number, boolean, object, array, etc.).',\n              additionalProperties: true\n            }\n          }\n        },\n        conditions: {\n          type: 'array',\n          items: {\n            type: 'object',\n            properties: {\n              field: {\n                type: 'string',\n                description: 'The field to be checked in the rule.'\n              },\n              operator: {\n                type: 'string',\n                description: 'The operator to be used in the rule.',\n                enum: [                  'equals'\n                ]\n              },\n              value: {\n                type: 'string',\n                description: 'The value of the field to be checked in the rule.'\n              }\n            }\n          }\n        },\n        created_at: {\n          type: 'string',\n          description: 'The datetime when the rule was created.',\n          format: 'date-time'\n        },\n        effective_end_date: {\n          type: 'string',\n          title: 'Date',\n          description: 'Specifies when the rules should stop applying rules based on the date.'\n        },\n        effective_start_date: {\n          type: 'string',\n          title: 'Date',\n          description: 'Specifies when the rule should begin applying based on the date.'\n        },\n        entity_type: {\n          type: 'string',\n          description: 'The entity type to which the rule is applied.',\n          enum: [            'pay_statement_item'\n          ]\n        },\n        priority: {\n          type: 'integer',\n          description: 'The priority of the rule.'\n        },\n        updated_at: {\n          type: 'string',\n          description: 'The datetime when the rule was last updated.',\n          format: 'date-time'\n        }\n      }\n    }\n  }\n}\n```",
-  inputSchema: {
-    type: 'object',
-    properties: {
-      rule_id: {
-        type: 'string',
-      },
-      entity_ids: {
-        type: 'array',
-        description: 'The entity IDs to update the rule for.',
-        items: {
-          type: 'string',
-        },
-      },
-      optionalProperty: {
-        type: 'object',
-        additionalProperties: true,
-      },
-      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: ['rule_id'],
-  },
-  annotations: {
-    idempotentHint: true,
-  },
-};
-
-export const handler = async (client: Finch, args: Record<string, unknown> | undefined) => {
-  const { rule_id, jq_filter, ...body } = args as any;
-  try {
-    return asTextContentResult(
-      await maybeFilter(jq_filter, await client.hris.company.payStatementItem.rules.update(rule_id, body)),
-    );
-  } catch (error) {
-    if (error instanceof Finch.APIError || isJqError(error)) {
-      return asErrorResult(error.message);
-    }
-    throw error;
-  }
-};
-
-export default { metadata, tool, handler };

package/src/tools/hris/company/retrieve-hris-company.ts

@@ -1,58 +0,0 @@
-// File generated from our OpenAPI spec by Stainless. See CONTRIBUTING.md for details.
-
-import { isJqError, maybeFilter } from '@tryfinch/finch-api-mcp/filtering';
-import { Metadata, asErrorResult, asTextContentResult } from '@tryfinch/finch-api-mcp/tools/types';
-
-import { Tool } from '@modelcontextprotocol/sdk/types.js';
-import Finch from '@tryfinch/finch-api';
-
-export const metadata: Metadata = {
-  resource: 'hris.company',
-  operation: 'read',
-  tags: [],
-  httpMethod: 'get',
-  httpPath: '/employer/company',
-  operationId: 'get-company',
-};
-
-export const tool: Tool = {
-  name: 'retrieve_hris_company',
-  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\nRead basic company data\n\n# Response Schema\n```json\n{\n  $ref: '#/$defs/company',\n  $defs: {\n    company: {\n      type: 'object',\n      title: 'GetCompany',\n      properties: {\n        id: {\n          type: 'string',\n          description: 'A stable Finch `id` (UUID v4) for the company.'\n        },\n        accounts: {\n          type: 'array',\n          description: 'An array of bank account objects associated with the payroll/HRIS system.',\n          items: {\n            type: 'object',\n            properties: {\n              account_name: {\n                type: 'string',\n                description: 'The name of the bank associated in the payroll/HRIS system.'\n              },\n              account_number: {\n                type: 'string',\n                description: '10-12 digit number to specify the bank account'\n              },\n              account_type: {\n                type: 'string',\n                description: 'The type of bank account.',\n                enum: [                  'checking',\n                  'savings'\n                ]\n              },\n              institution_name: {\n                type: 'string',\n                description: 'Name of the banking institution.'\n              },\n              routing_number: {\n                type: 'string',\n                description: 'A nine-digit code that\\'s based on the U.S. Bank location where your account was opened.'\n              }\n            },\n            required: [              'account_name',\n              'account_number',\n              'account_type',\n              'institution_name',\n              'routing_number'\n            ]\n          }\n        },\n        departments: {\n          type: 'array',\n          description: 'The array of company departments.',\n          items: {\n            type: 'object',\n            properties: {\n              name: {\n                type: 'string',\n                description: 'The department name.'\n              },\n              parent: {\n                type: 'object',\n                description: 'The parent department, if present.',\n                properties: {\n                  name: {\n                    type: 'string',\n                    description: 'The parent department\\'s name.'\n                  }\n                },\n                required: [                  'name'\n                ]\n              }\n            },\n            required: [              'name',\n              'parent'\n            ]\n          }\n        },\n        ein: {\n          type: 'string',\n          description: 'The employer identification number.'\n        },\n        entity: {\n          type: 'object',\n          description: 'The entity type object.',\n          properties: {\n            subtype: {\n              type: 'string',\n              description: 'The tax payer subtype of the company.',\n              enum: [                's_corporation',\n                'c_corporation',\n                'b_corporation'\n              ]\n            },\n            type: {\n              type: 'string',\n              description: 'The tax payer type of the company.',\n              enum: [                'llc',\n                'lp',\n                'corporation',\n                'sole_proprietor',\n                'non_profit',\n                'partnership',\n                'cooperative'\n              ]\n            }\n          },\n          required: [            'subtype',\n            'type'\n          ]\n        },\n        legal_name: {\n          type: 'string',\n          description: 'The legal name of the company.'\n        },\n        locations: {\n          type: 'array',\n          items: {\n            $ref: '#/$defs/location'\n          }\n        },\n        primary_email: {\n          type: 'string',\n          description: 'The email of the main administrator on the account.'\n        },\n        primary_phone_number: {\n          type: 'string',\n          description: 'The phone number of the main administrator on the account. Format: E.164, with extension where applicable, e.g. `+NNNNNNNNNNN xExtension`'\n        }\n      },\n      required: [        'id',\n        'accounts',\n        'departments',\n        'ein',\n        'entity',\n        'legal_name',\n        'locations',\n        'primary_email',\n        'primary_phone_number'\n      ]\n    },\n    location: {\n      type: 'object',\n      title: 'Location',\n      properties: {\n        city: {\n          type: 'string',\n          description: 'City, district, suburb, town, or village.'\n        },\n        country: {\n          type: 'string',\n          description: 'The 2-letter ISO 3166 country code.'\n        },\n        line1: {\n          type: 'string',\n          description: 'Street address or PO box.'\n        },\n        line2: {\n          type: 'string',\n          description: 'Apartment, suite, unit, or building.'\n        },\n        postal_code: {\n          type: 'string',\n          description: 'The postal code or zip code.'\n        },\n        state: {\n          type: 'string',\n          description: 'The state code.'\n        },\n        name: {\n          type: 'string'\n        },\n        source_id: {\n          type: 'string'\n        }\n      },\n      required: [        'city',\n        'country',\n        'line1',\n        'line2',\n        'postal_code',\n        'state'\n      ]\n    }\n  }\n}\n```",
-  inputSchema: {
-    type: 'object',
-    properties: {
-      entity_ids: {
-        type: 'array',
-        description: "The entity IDs to specify which entities' data to access.",
-        items: {
-          type: 'string',
-        },
-      },
-      jq_filter: {
-        type: 'string',
-        title: 'jq Filter',
-        description:
-          'A jq filter to apply to the response to include certain fields. Consult the output schema in the tool description to see the fields that are available.\n\nFor example: to include only the `name` field in every object of a results array, you can provide ".results[].name".\n\nFor more information, see the [jq documentation](https://jqlang.org/manual/).',
-      },
-    },
-    required: [],
-  },
-  annotations: {
-    readOnlyHint: true,
-  },
-};
-
-export const handler = async (client: Finch, args: Record<string, unknown> | undefined) => {
-  const { jq_filter, ...body } = args as any;
-  try {
-    return asTextContentResult(await maybeFilter(jq_filter, await client.hris.company.retrieve(body)));
-  } catch (error) {
-    if (error instanceof Finch.APIError || isJqError(error)) {
-      return asErrorResult(error.message);
-    }
-    throw error;
-  }
-};
-
-export default { metadata, tool, handler };