scorecard-ai-mcp 2.0.0 → 2.1.0

package/src/tools/testcases/create-testcases.ts

@@ -1,9 +1,9 @@
 // File generated from our OpenAPI spec by Stainless. See CONTRIBUTING.md for details.
 
-import { asTextContentResult } from 'scorecard-ai-mcp/tools/types';
+import { maybeFilter } from 'scorecard-ai-mcp/filtering';
+import { Metadata, asTextContentResult } from 'scorecard-ai-mcp/tools/types';
 
 import { Tool } from '@modelcontextprotocol/sdk/types.js';
-import type { Metadata } from '../';
 import Scorecard from 'scorecard-ai';
 
 export const metadata: Metadata = {
@@ -17,7 +17,8 @@ export const metadata: Metadata = {
 
 export const tool: Tool = {
   name: 'create_testcases',
-  description: 'Create multiple Testcases in the specified Testset.',
+  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 multiple Testcases in the specified Testset.\n\n# Response Schema\n```json\n{\n  type: 'object',\n  properties: {\n    items: {\n      type: 'array',\n      items: {\n        $ref: '#/$defs/testcase'\n      }\n    }\n  },\n  required: [    'items'\n  ],\n  $defs: {\n    testcase: {\n      type: 'object',\n      description: 'A test case in the Scorecard system. Contains JSON data that is validated against the schema defined by its Testset.\\nThe `inputs` and `expected` fields are derived from the `data` field based on the Testset\\'s `fieldMapping`, and include all mapped fields, including those with validation errors.\\nTestcases are stored regardless of validation results, with any validation errors included in the `validationErrors` field.',\n      properties: {\n        id: {\n          type: 'string',\n          description: 'The ID of the Testcase.'\n        },\n        expected: {\n          type: 'object',\n          description: 'Derived from data based on the Testset\\'s fieldMapping. Contains all fields marked as expected outputs, including those with validation errors.',\n          additionalProperties: true\n        },\n        inputs: {\n          type: 'object',\n          description: 'Derived from data based on the Testset\\'s fieldMapping. Contains all fields marked as inputs, including those with validation errors.',\n          additionalProperties: true\n        },\n        jsonData: {\n          type: 'object',\n          description: 'The JSON data of the Testcase, which is validated against the Testset\\'s schema.',\n          additionalProperties: true\n        },\n        testsetId: {\n          type: 'string',\n          description: 'The ID of the Testset this Testcase belongs to.'\n        },\n        validationErrors: {\n          type: 'array',\n          description: 'Validation errors found in the Testcase data. If present, the Testcase doesn\\'t fully conform to its Testset\\'s schema.',\n          items: {\n            type: 'object',\n            properties: {\n              message: {\n                type: 'string',\n                description: 'Human-readable error description.'\n              },\n              path: {\n                type: 'string',\n                description: 'JSON Pointer to the field with the validation error.'\n              }\n            },\n            required: [              'message',\n              'path'\n            ]\n          }\n        }\n      },\n      required: [        'id',\n        'expected',\n        'inputs',\n        'jsonData',\n        'testsetId'\n      ]\n    }\n  }\n}\n```",
   inputSchema: {
     type: 'object',
     properties: {
@@ -33,18 +34,27 @@ export const tool: Tool = {
             jsonData: {
               type: 'object',
               description: "The JSON data of the Testcase, which is validated against the Testset's schema.",
+              additionalProperties: true,
             },
           },
           required: ['jsonData'],
         },
       },
+      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: ['testsetId', 'items'],
   },
+  annotations: {},
 };
 
 export const handler = async (client: Scorecard, args: Record<string, unknown> | undefined) => {
-  const { testsetId, ...body } = args as any;
-  return asTextContentResult(await client.testcases.create(testsetId, body));
+  const { testsetId, jq_filter, ...body } = args as any;
+  return asTextContentResult(await maybeFilter(jq_filter, await client.testcases.create(testsetId, body)));
 };
 
 export default { metadata, tool, handler };

package/src/tools/testcases/delete-testcases.ts

@@ -1,9 +1,9 @@
 // File generated from our OpenAPI spec by Stainless. See CONTRIBUTING.md for details.
 
-import { asTextContentResult } from 'scorecard-ai-mcp/tools/types';
+import { maybeFilter } from 'scorecard-ai-mcp/filtering';
+import { Metadata, asTextContentResult } from 'scorecard-ai-mcp/tools/types';
 
 import { Tool } from '@modelcontextprotocol/sdk/types.js';
-import type { Metadata } from '../';
 import Scorecard from 'scorecard-ai';
 
 export const metadata: Metadata = {
@@ -17,7 +17,8 @@ export const metadata: Metadata = {
 
 export const tool: Tool = {
   name: 'delete_testcases',
-  description: 'Delete multiple Testcases by their IDs.',
+  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\nDelete multiple Testcases by their IDs.\n\n# Response Schema\n```json\n{\n  type: 'object',\n  properties: {\n    success: {\n      type: 'boolean',\n      description: 'Whether the deletion was successful.'\n    }\n  },\n  required: [    'success'\n  ]\n}\n```",
   inputSchema: {
     type: 'object',
     properties: {
@@ -28,13 +29,21 @@ export const tool: Tool = {
           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: ['ids'],
   },
+  annotations: {},
 };
 
 export const handler = async (client: Scorecard, args: Record<string, unknown> | undefined) => {
-  const body = args as any;
-  return asTextContentResult(await client.testcases.delete(body));
+  const { jq_filter, ...body } = args as any;
+  return asTextContentResult(await maybeFilter(jq_filter, await client.testcases.delete(body)));
 };
 
 export default { metadata, tool, handler };

package/src/tools/testcases/get-testcases.ts

@@ -1,9 +1,9 @@
 // File generated from our OpenAPI spec by Stainless. See CONTRIBUTING.md for details.
 
-import { asTextContentResult } from 'scorecard-ai-mcp/tools/types';
+import { maybeFilter } from 'scorecard-ai-mcp/filtering';
+import { Metadata, asTextContentResult } from 'scorecard-ai-mcp/tools/types';
 
 import { Tool } from '@modelcontextprotocol/sdk/types.js';
-import type { Metadata } from '../';
 import Scorecard from 'scorecard-ai';
 
 export const metadata: Metadata = {
@@ -17,20 +17,31 @@ export const metadata: Metadata = {
 
 export const tool: Tool = {
   name: 'get_testcases',
-  description: 'Retrieve a specific Testcase by ID.',
+  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 a specific Testcase by ID.\n\n# Response Schema\n```json\n{\n  $ref: '#/$defs/testcase',\n  $defs: {\n    testcase: {\n      type: 'object',\n      description: 'A test case in the Scorecard system. Contains JSON data that is validated against the schema defined by its Testset.\\nThe `inputs` and `expected` fields are derived from the `data` field based on the Testset\\'s `fieldMapping`, and include all mapped fields, including those with validation errors.\\nTestcases are stored regardless of validation results, with any validation errors included in the `validationErrors` field.',\n      properties: {\n        id: {\n          type: 'string',\n          description: 'The ID of the Testcase.'\n        },\n        expected: {\n          type: 'object',\n          description: 'Derived from data based on the Testset\\'s fieldMapping. Contains all fields marked as expected outputs, including those with validation errors.',\n          additionalProperties: true\n        },\n        inputs: {\n          type: 'object',\n          description: 'Derived from data based on the Testset\\'s fieldMapping. Contains all fields marked as inputs, including those with validation errors.',\n          additionalProperties: true\n        },\n        jsonData: {\n          type: 'object',\n          description: 'The JSON data of the Testcase, which is validated against the Testset\\'s schema.',\n          additionalProperties: true\n        },\n        testsetId: {\n          type: 'string',\n          description: 'The ID of the Testset this Testcase belongs to.'\n        },\n        validationErrors: {\n          type: 'array',\n          description: 'Validation errors found in the Testcase data. If present, the Testcase doesn\\'t fully conform to its Testset\\'s schema.',\n          items: {\n            type: 'object',\n            properties: {\n              message: {\n                type: 'string',\n                description: 'Human-readable error description.'\n              },\n              path: {\n                type: 'string',\n                description: 'JSON Pointer to the field with the validation error.'\n              }\n            },\n            required: [              'message',\n              'path'\n            ]\n          }\n        }\n      },\n      required: [        'id',\n        'expected',\n        'inputs',\n        'jsonData',\n        'testsetId'\n      ]\n    }\n  }\n}\n```",
   inputSchema: {
     type: 'object',
     properties: {
       testcaseId: {
         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: ['testcaseId'],
+  },
+  annotations: {
+    readOnlyHint: true,
   },
 };
 
 export const handler = async (client: Scorecard, args: Record<string, unknown> | undefined) => {
-  const { testcaseId, ...body } = args as any;
-  return asTextContentResult(await client.testcases.get(testcaseId));
+  const { testcaseId, jq_filter, ...body } = args as any;
+  return asTextContentResult(await maybeFilter(jq_filter, await client.testcases.get(testcaseId)));
 };
 
 export default { metadata, tool, handler };

package/src/tools/testcases/list-testcases.ts

@@ -1,9 +1,9 @@
 // File generated from our OpenAPI spec by Stainless. See CONTRIBUTING.md for details.
 
-import { asTextContentResult } from 'scorecard-ai-mcp/tools/types';
+import { maybeFilter } from 'scorecard-ai-mcp/filtering';
+import { Metadata, asTextContentResult } from 'scorecard-ai-mcp/tools/types';
 
 import { Tool } from '@modelcontextprotocol/sdk/types.js';
-import type { Metadata } from '../';
 import Scorecard from 'scorecard-ai';
 
 export const metadata: Metadata = {
@@ -17,7 +17,8 @@ export const metadata: Metadata = {
 
 export const tool: Tool = {
   name: 'list_testcases',
-  description: 'Retrieve a paginated list of Testcases belonging to a Testset.',
+  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 a paginated list of Testcases belonging to a Testset.\n\n# Response Schema\n```json\n{\n  type: 'object',\n  properties: {\n    data: {\n      type: 'array',\n      items: {\n        $ref: '#/$defs/testcase'\n      }\n    },\n    hasMore: {\n      type: 'boolean'\n    },\n    nextCursor: {\n      type: 'string'\n    },\n    total: {\n      type: 'integer'\n    }\n  },\n  required: [    'data',\n    'hasMore',\n    'nextCursor'\n  ],\n  $defs: {\n    testcase: {\n      type: 'object',\n      description: 'A test case in the Scorecard system. Contains JSON data that is validated against the schema defined by its Testset.\\nThe `inputs` and `expected` fields are derived from the `data` field based on the Testset\\'s `fieldMapping`, and include all mapped fields, including those with validation errors.\\nTestcases are stored regardless of validation results, with any validation errors included in the `validationErrors` field.',\n      properties: {\n        id: {\n          type: 'string',\n          description: 'The ID of the Testcase.'\n        },\n        expected: {\n          type: 'object',\n          description: 'Derived from data based on the Testset\\'s fieldMapping. Contains all fields marked as expected outputs, including those with validation errors.',\n          additionalProperties: true\n        },\n        inputs: {\n          type: 'object',\n          description: 'Derived from data based on the Testset\\'s fieldMapping. Contains all fields marked as inputs, including those with validation errors.',\n          additionalProperties: true\n        },\n        jsonData: {\n          type: 'object',\n          description: 'The JSON data of the Testcase, which is validated against the Testset\\'s schema.',\n          additionalProperties: true\n        },\n        testsetId: {\n          type: 'string',\n          description: 'The ID of the Testset this Testcase belongs to.'\n        },\n        validationErrors: {\n          type: 'array',\n          description: 'Validation errors found in the Testcase data. If present, the Testcase doesn\\'t fully conform to its Testset\\'s schema.',\n          items: {\n            type: 'object',\n            properties: {\n              message: {\n                type: 'string',\n                description: 'Human-readable error description.'\n              },\n              path: {\n                type: 'string',\n                description: 'JSON Pointer to the field with the validation error.'\n              }\n            },\n            required: [              'message',\n              'path'\n            ]\n          }\n        }\n      },\n      required: [        'id',\n        'expected',\n        'inputs',\n        'jsonData',\n        'testsetId'\n      ]\n    }\n  }\n}\n```",
   inputSchema: {
     type: 'object',
     properties: {
@@ -34,13 +35,24 @@ export const tool: Tool = {
         description:
           'Maximum number of items to return (1-100). Use with `cursor` for pagination through large sets.',
       },
+      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: ['testsetId'],
+  },
+  annotations: {
+    readOnlyHint: true,
   },
 };
 
 export const handler = async (client: Scorecard, args: Record<string, unknown> | undefined) => {
-  const { testsetId, ...body } = args as any;
-  return asTextContentResult(await client.testcases.list(testsetId, body));
+  const { testsetId, jq_filter, ...body } = args as any;
+  const response = await client.testcases.list(testsetId, body).asResponse();
+  return asTextContentResult(await maybeFilter(jq_filter, await response.json()));
 };
 
 export default { metadata, tool, handler };

package/src/tools/testcases/update-testcases.ts

@@ -1,9 +1,9 @@
 // File generated from our OpenAPI spec by Stainless. See CONTRIBUTING.md for details.
 
-import { asTextContentResult } from 'scorecard-ai-mcp/tools/types';
+import { maybeFilter } from 'scorecard-ai-mcp/filtering';
+import { Metadata, asTextContentResult } from 'scorecard-ai-mcp/tools/types';
 
 import { Tool } from '@modelcontextprotocol/sdk/types.js';
-import type { Metadata } from '../';
 import Scorecard from 'scorecard-ai';
 
 export const metadata: Metadata = {
@@ -17,7 +17,8 @@ export const metadata: Metadata = {
 
 export const tool: Tool = {
   name: 'update_testcases',
-  description: 'Replace the data of an existing Testcase while keeping its ID.',
+  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\nReplace the data of an existing Testcase while keeping its ID.\n\n# Response Schema\n```json\n{\n  $ref: '#/$defs/testcase',\n  $defs: {\n    testcase: {\n      type: 'object',\n      description: 'A test case in the Scorecard system. Contains JSON data that is validated against the schema defined by its Testset.\\nThe `inputs` and `expected` fields are derived from the `data` field based on the Testset\\'s `fieldMapping`, and include all mapped fields, including those with validation errors.\\nTestcases are stored regardless of validation results, with any validation errors included in the `validationErrors` field.',\n      properties: {\n        id: {\n          type: 'string',\n          description: 'The ID of the Testcase.'\n        },\n        expected: {\n          type: 'object',\n          description: 'Derived from data based on the Testset\\'s fieldMapping. Contains all fields marked as expected outputs, including those with validation errors.',\n          additionalProperties: true\n        },\n        inputs: {\n          type: 'object',\n          description: 'Derived from data based on the Testset\\'s fieldMapping. Contains all fields marked as inputs, including those with validation errors.',\n          additionalProperties: true\n        },\n        jsonData: {\n          type: 'object',\n          description: 'The JSON data of the Testcase, which is validated against the Testset\\'s schema.',\n          additionalProperties: true\n        },\n        testsetId: {\n          type: 'string',\n          description: 'The ID of the Testset this Testcase belongs to.'\n        },\n        validationErrors: {\n          type: 'array',\n          description: 'Validation errors found in the Testcase data. If present, the Testcase doesn\\'t fully conform to its Testset\\'s schema.',\n          items: {\n            type: 'object',\n            properties: {\n              message: {\n                type: 'string',\n                description: 'Human-readable error description.'\n              },\n              path: {\n                type: 'string',\n                description: 'JSON Pointer to the field with the validation error.'\n              }\n            },\n            required: [              'message',\n              'path'\n            ]\n          }\n        }\n      },\n      required: [        'id',\n        'expected',\n        'inputs',\n        'jsonData',\n        'testsetId'\n      ]\n    }\n  }\n}\n```",
   inputSchema: {
     type: 'object',
     properties: {
@@ -27,14 +28,25 @@ export const tool: Tool = {
       jsonData: {
         type: 'object',
         description: "The JSON data of the Testcase, which is validated against the Testset's schema.",
+        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: ['testcaseId', 'jsonData'],
+  },
+  annotations: {
+    idempotentHint: true,
   },
 };
 
 export const handler = async (client: Scorecard, args: Record<string, unknown> | undefined) => {
-  const { testcaseId, ...body } = args as any;
-  return asTextContentResult(await client.testcases.update(testcaseId, body));
+  const { testcaseId, jq_filter, ...body } = args as any;
+  return asTextContentResult(await maybeFilter(jq_filter, await client.testcases.update(testcaseId, body)));
 };
 
 export default { metadata, tool, handler };

package/src/tools/testsets/create-testsets.ts

@@ -1,9 +1,9 @@
 // File generated from our OpenAPI spec by Stainless. See CONTRIBUTING.md for details.
 
-import { asTextContentResult } from 'scorecard-ai-mcp/tools/types';
+import { maybeFilter } from 'scorecard-ai-mcp/filtering';
+import { Metadata, asTextContentResult } from 'scorecard-ai-mcp/tools/types';
 
 import { Tool } from '@modelcontextprotocol/sdk/types.js';
-import type { Metadata } from '../';
 import Scorecard from 'scorecard-ai';
 
 export const metadata: Metadata = {
@@ -18,7 +18,7 @@ export const metadata: Metadata = {
 export const tool: Tool = {
   name: 'create_testsets',
   description:
-    'Create a new Testset for a Project. The Testset will be created in the Project specified in the path.',
+    "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 a new Testset for a Project. The Testset will be created in the Project specified in the path.\n\n# Response Schema\n```json\n{\n  $ref: '#/$defs/testset',\n  $defs: {\n    testset: {\n      type: 'object',\n      description: 'A collection of Testcases that share the same schema.\\nEach Testset defines the structure of its Testcases through a JSON schema.\\nThe `fieldMapping` object maps top-level keys of the Testcase schema to their roles (input/expected output).\\nFields not mentioned in the `fieldMapping` during creation or update are treated as metadata.\\n\\n## JSON Schema validation constraints supported:\\n\\n- **Required fields** - Fields listed in the schema\\'s `required` array must be present in Testcases.\\n- **Type validation** - Values must match the specified type (string, number, boolean, null, integer, object, array).\\n- **Enum validation** - Values must be one of the options specified in the `enum` array.\\n- **Object property validation** - Properties of objects must conform to their defined schemas.\\n- **Array item validation** - Items in arrays must conform to the `items` schema.\\n- **Logical composition** - Values must conform to at least one schema in the `anyOf` array.\\n\\nTestcases that fail validation will still be stored, but will include `validationErrors` detailing the issues.\\nExtra fields in the Testcase data that are not in the schema will be stored but are ignored during validation.',\n      properties: {\n        id: {\n          type: 'string',\n          description: 'The ID of the Testset.'\n        },\n        description: {\n          type: 'string',\n          description: 'The description of the Testset.'\n        },\n        fieldMapping: {\n          type: 'object',\n          description: 'Maps top-level keys of the Testcase schema to their roles (input/expected output). Unmapped fields are treated as metadata.',\n          properties: {\n            expected: {\n              type: 'array',\n              description: 'Fields that represent expected outputs.',\n              items: {\n                type: 'string'\n              }\n            },\n            inputs: {\n              type: 'array',\n              description: 'Fields that represent inputs to the AI system.',\n              items: {\n                type: 'string'\n              }\n            },\n            metadata: {\n              type: 'array',\n              description: 'Fields that are not inputs or expected outputs.',\n              items: {\n                type: 'string'\n              }\n            }\n          },\n          required: [            'expected',\n            'inputs',\n            'metadata'\n          ]\n        },\n        jsonSchema: {\n          type: 'object',\n          description: 'The JSON schema for each Testcase in the Testset.',\n          additionalProperties: true\n        },\n        name: {\n          type: 'string',\n          description: 'The name of the Testset.'\n        }\n      },\n      required: [        'id',\n        'description',\n        'fieldMapping',\n        'jsonSchema',\n        'name'\n      ]\n    }\n  }\n}\n```",
   inputSchema: {
     type: 'object',
     properties: {
@@ -61,18 +61,27 @@ export const tool: Tool = {
       jsonSchema: {
         type: 'object',
         description: 'The JSON schema for each Testcase in the Testset.',
+        additionalProperties: true,
       },
       name: {
         type: 'string',
         description: 'The name of the Testset.',
       },
+      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: ['projectId', 'description', 'fieldMapping', 'jsonSchema', 'name'],
   },
+  annotations: {},
 };
 
 export const handler = async (client: Scorecard, args: Record<string, unknown> | undefined) => {
-  const { projectId, ...body } = args as any;
-  return asTextContentResult(await client.testsets.create(projectId, body));
+  const { projectId, jq_filter, ...body } = args as any;
+  return asTextContentResult(await maybeFilter(jq_filter, await client.testsets.create(projectId, body)));
 };
 
 export default { metadata, tool, handler };

package/src/tools/testsets/delete-testsets.ts

@@ -1,9 +1,9 @@
 // File generated from our OpenAPI spec by Stainless. See CONTRIBUTING.md for details.
 
-import { asTextContentResult } from 'scorecard-ai-mcp/tools/types';
+import { maybeFilter } from 'scorecard-ai-mcp/filtering';
+import { Metadata, asTextContentResult } from 'scorecard-ai-mcp/tools/types';
 
 import { Tool } from '@modelcontextprotocol/sdk/types.js';
-import type { Metadata } from '../';
 import Scorecard from 'scorecard-ai';
 
 export const metadata: Metadata = {
@@ -17,20 +17,31 @@ export const metadata: Metadata = {
 
 export const tool: Tool = {
   name: 'delete_testsets',
-  description: 'Delete Testset',
+  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\nDelete Testset\n\n# Response Schema\n```json\n{\n  type: 'object',\n  properties: {\n    success: {\n      type: 'boolean',\n      description: 'Whether the deletion was successful.'\n    }\n  },\n  required: [    'success'\n  ]\n}\n```",
   inputSchema: {
     type: 'object',
     properties: {
       testsetId: {
         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: ['testsetId'],
+  },
+  annotations: {
+    idempotentHint: true,
   },
 };
 
 export const handler = async (client: Scorecard, args: Record<string, unknown> | undefined) => {
-  const { testsetId, ...body } = args as any;
-  return asTextContentResult(await client.testsets.delete(testsetId));
+  const { testsetId, jq_filter, ...body } = args as any;
+  return asTextContentResult(await maybeFilter(jq_filter, await client.testsets.delete(testsetId)));
 };
 
 export default { metadata, tool, handler };

package/src/tools/testsets/get-testsets.ts

@@ -1,9 +1,9 @@
 // File generated from our OpenAPI spec by Stainless. See CONTRIBUTING.md for details.
 
-import { asTextContentResult } from 'scorecard-ai-mcp/tools/types';
+import { maybeFilter } from 'scorecard-ai-mcp/filtering';
+import { Metadata, asTextContentResult } from 'scorecard-ai-mcp/tools/types';
 
 import { Tool } from '@modelcontextprotocol/sdk/types.js';
-import type { Metadata } from '../';
 import Scorecard from 'scorecard-ai';
 
 export const metadata: Metadata = {
@@ -17,20 +17,31 @@ export const metadata: Metadata = {
 
 export const tool: Tool = {
   name: 'get_testsets',
-  description: 'Get Testset',
+  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\nGet Testset\n\n# Response Schema\n```json\n{\n  $ref: '#/$defs/testset',\n  $defs: {\n    testset: {\n      type: 'object',\n      description: 'A collection of Testcases that share the same schema.\\nEach Testset defines the structure of its Testcases through a JSON schema.\\nThe `fieldMapping` object maps top-level keys of the Testcase schema to their roles (input/expected output).\\nFields not mentioned in the `fieldMapping` during creation or update are treated as metadata.\\n\\n## JSON Schema validation constraints supported:\\n\\n- **Required fields** - Fields listed in the schema\\'s `required` array must be present in Testcases.\\n- **Type validation** - Values must match the specified type (string, number, boolean, null, integer, object, array).\\n- **Enum validation** - Values must be one of the options specified in the `enum` array.\\n- **Object property validation** - Properties of objects must conform to their defined schemas.\\n- **Array item validation** - Items in arrays must conform to the `items` schema.\\n- **Logical composition** - Values must conform to at least one schema in the `anyOf` array.\\n\\nTestcases that fail validation will still be stored, but will include `validationErrors` detailing the issues.\\nExtra fields in the Testcase data that are not in the schema will be stored but are ignored during validation.',\n      properties: {\n        id: {\n          type: 'string',\n          description: 'The ID of the Testset.'\n        },\n        description: {\n          type: 'string',\n          description: 'The description of the Testset.'\n        },\n        fieldMapping: {\n          type: 'object',\n          description: 'Maps top-level keys of the Testcase schema to their roles (input/expected output). Unmapped fields are treated as metadata.',\n          properties: {\n            expected: {\n              type: 'array',\n              description: 'Fields that represent expected outputs.',\n              items: {\n                type: 'string'\n              }\n            },\n            inputs: {\n              type: 'array',\n              description: 'Fields that represent inputs to the AI system.',\n              items: {\n                type: 'string'\n              }\n            },\n            metadata: {\n              type: 'array',\n              description: 'Fields that are not inputs or expected outputs.',\n              items: {\n                type: 'string'\n              }\n            }\n          },\n          required: [            'expected',\n            'inputs',\n            'metadata'\n          ]\n        },\n        jsonSchema: {\n          type: 'object',\n          description: 'The JSON schema for each Testcase in the Testset.',\n          additionalProperties: true\n        },\n        name: {\n          type: 'string',\n          description: 'The name of the Testset.'\n        }\n      },\n      required: [        'id',\n        'description',\n        'fieldMapping',\n        'jsonSchema',\n        'name'\n      ]\n    }\n  }\n}\n```",
   inputSchema: {
     type: 'object',
     properties: {
       testsetId: {
         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: ['testsetId'],
+  },
+  annotations: {
+    readOnlyHint: true,
   },
 };
 
 export const handler = async (client: Scorecard, args: Record<string, unknown> | undefined) => {
-  const { testsetId, ...body } = args as any;
-  return asTextContentResult(await client.testsets.get(testsetId));
+  const { testsetId, jq_filter, ...body } = args as any;
+  return asTextContentResult(await maybeFilter(jq_filter, await client.testsets.get(testsetId)));
 };
 
 export default { metadata, tool, handler };

package/src/tools/testsets/list-testsets.ts

@@ -1,9 +1,9 @@
 // File generated from our OpenAPI spec by Stainless. See CONTRIBUTING.md for details.
 
-import { asTextContentResult } from 'scorecard-ai-mcp/tools/types';
+import { maybeFilter } from 'scorecard-ai-mcp/filtering';
+import { Metadata, asTextContentResult } from 'scorecard-ai-mcp/tools/types';
 
 import { Tool } from '@modelcontextprotocol/sdk/types.js';
-import type { Metadata } from '../';
 import Scorecard from 'scorecard-ai';
 
 export const metadata: Metadata = {
@@ -17,7 +17,8 @@ export const metadata: Metadata = {
 
 export const tool: Tool = {
   name: 'list_testsets',
-  description: 'Retrieve a paginated list of Testsets belonging to a Project.',
+  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 a paginated list of Testsets belonging to a Project.\n\n# Response Schema\n```json\n{\n  type: 'object',\n  properties: {\n    data: {\n      type: 'array',\n      items: {\n        $ref: '#/$defs/testset'\n      }\n    },\n    hasMore: {\n      type: 'boolean'\n    },\n    nextCursor: {\n      type: 'string'\n    },\n    total: {\n      type: 'integer'\n    }\n  },\n  required: [    'data',\n    'hasMore',\n    'nextCursor'\n  ],\n  $defs: {\n    testset: {\n      type: 'object',\n      description: 'A collection of Testcases that share the same schema.\\nEach Testset defines the structure of its Testcases through a JSON schema.\\nThe `fieldMapping` object maps top-level keys of the Testcase schema to their roles (input/expected output).\\nFields not mentioned in the `fieldMapping` during creation or update are treated as metadata.\\n\\n## JSON Schema validation constraints supported:\\n\\n- **Required fields** - Fields listed in the schema\\'s `required` array must be present in Testcases.\\n- **Type validation** - Values must match the specified type (string, number, boolean, null, integer, object, array).\\n- **Enum validation** - Values must be one of the options specified in the `enum` array.\\n- **Object property validation** - Properties of objects must conform to their defined schemas.\\n- **Array item validation** - Items in arrays must conform to the `items` schema.\\n- **Logical composition** - Values must conform to at least one schema in the `anyOf` array.\\n\\nTestcases that fail validation will still be stored, but will include `validationErrors` detailing the issues.\\nExtra fields in the Testcase data that are not in the schema will be stored but are ignored during validation.',\n      properties: {\n        id: {\n          type: 'string',\n          description: 'The ID of the Testset.'\n        },\n        description: {\n          type: 'string',\n          description: 'The description of the Testset.'\n        },\n        fieldMapping: {\n          type: 'object',\n          description: 'Maps top-level keys of the Testcase schema to their roles (input/expected output). Unmapped fields are treated as metadata.',\n          properties: {\n            expected: {\n              type: 'array',\n              description: 'Fields that represent expected outputs.',\n              items: {\n                type: 'string'\n              }\n            },\n            inputs: {\n              type: 'array',\n              description: 'Fields that represent inputs to the AI system.',\n              items: {\n                type: 'string'\n              }\n            },\n            metadata: {\n              type: 'array',\n              description: 'Fields that are not inputs or expected outputs.',\n              items: {\n                type: 'string'\n              }\n            }\n          },\n          required: [            'expected',\n            'inputs',\n            'metadata'\n          ]\n        },\n        jsonSchema: {\n          type: 'object',\n          description: 'The JSON schema for each Testcase in the Testset.',\n          additionalProperties: true\n        },\n        name: {\n          type: 'string',\n          description: 'The name of the Testset.'\n        }\n      },\n      required: [        'id',\n        'description',\n        'fieldMapping',\n        'jsonSchema',\n        'name'\n      ]\n    }\n  }\n}\n```",
   inputSchema: {
     type: 'object',
     properties: {
@@ -34,13 +35,24 @@ export const tool: Tool = {
         description:
           'Maximum number of items to return (1-100). Use with `cursor` for pagination through large sets.',
       },
+      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: ['projectId'],
+  },
+  annotations: {
+    readOnlyHint: true,
   },
 };
 
 export const handler = async (client: Scorecard, args: Record<string, unknown> | undefined) => {
-  const { projectId, ...body } = args as any;
-  return asTextContentResult(await client.testsets.list(projectId, body));
+  const { projectId, jq_filter, ...body } = args as any;
+  const response = await client.testsets.list(projectId, body).asResponse();
+  return asTextContentResult(await maybeFilter(jq_filter, await response.json()));
 };
 
 export default { metadata, tool, handler };

package/src/tools/testsets/update-testsets.ts

@@ -1,9 +1,9 @@
 // File generated from our OpenAPI spec by Stainless. See CONTRIBUTING.md for details.
 
-import { asTextContentResult } from 'scorecard-ai-mcp/tools/types';
+import { maybeFilter } from 'scorecard-ai-mcp/filtering';
+import { Metadata, asTextContentResult } from 'scorecard-ai-mcp/tools/types';
 
 import { Tool } from '@modelcontextprotocol/sdk/types.js';
-import type { Metadata } from '../';
 import Scorecard from 'scorecard-ai';
 
 export const metadata: Metadata = {
@@ -18,7 +18,7 @@ export const metadata: Metadata = {
 export const tool: Tool = {
   name: 'update_testsets',
   description:
-    'Update a Testset. Only the fields provided in the request body will be updated.\nIf a field is provided, the new content will replace the existing content.\nIf a field is not provided, the existing content will remain unchanged.\n\nWhen updating the schema:\n- If field mappings are not provided and existing mappings reference fields that no longer exist, those mappings will be automatically removed\n- To preserve all existing mappings, ensure all referenced fields remain in the updated schema\n- For complete control, provide both schema and fieldMapping when updating the schema',
+    "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\nUpdate a Testset. Only the fields provided in the request body will be updated.\nIf a field is provided, the new content will replace the existing content.\nIf a field is not provided, the existing content will remain unchanged.\n\nWhen updating the schema:\n- If field mappings are not provided and existing mappings reference fields that no longer exist, those mappings will be automatically removed\n- To preserve all existing mappings, ensure all referenced fields remain in the updated schema\n- For complete control, provide both schema and fieldMapping when updating the schema\n\n# Response Schema\n```json\n{\n  $ref: '#/$defs/testset',\n  $defs: {\n    testset: {\n      type: 'object',\n      description: 'A collection of Testcases that share the same schema.\\nEach Testset defines the structure of its Testcases through a JSON schema.\\nThe `fieldMapping` object maps top-level keys of the Testcase schema to their roles (input/expected output).\\nFields not mentioned in the `fieldMapping` during creation or update are treated as metadata.\\n\\n## JSON Schema validation constraints supported:\\n\\n- **Required fields** - Fields listed in the schema\\'s `required` array must be present in Testcases.\\n- **Type validation** - Values must match the specified type (string, number, boolean, null, integer, object, array).\\n- **Enum validation** - Values must be one of the options specified in the `enum` array.\\n- **Object property validation** - Properties of objects must conform to their defined schemas.\\n- **Array item validation** - Items in arrays must conform to the `items` schema.\\n- **Logical composition** - Values must conform to at least one schema in the `anyOf` array.\\n\\nTestcases that fail validation will still be stored, but will include `validationErrors` detailing the issues.\\nExtra fields in the Testcase data that are not in the schema will be stored but are ignored during validation.',\n      properties: {\n        id: {\n          type: 'string',\n          description: 'The ID of the Testset.'\n        },\n        description: {\n          type: 'string',\n          description: 'The description of the Testset.'\n        },\n        fieldMapping: {\n          type: 'object',\n          description: 'Maps top-level keys of the Testcase schema to their roles (input/expected output). Unmapped fields are treated as metadata.',\n          properties: {\n            expected: {\n              type: 'array',\n              description: 'Fields that represent expected outputs.',\n              items: {\n                type: 'string'\n              }\n            },\n            inputs: {\n              type: 'array',\n              description: 'Fields that represent inputs to the AI system.',\n              items: {\n                type: 'string'\n              }\n            },\n            metadata: {\n              type: 'array',\n              description: 'Fields that are not inputs or expected outputs.',\n              items: {\n                type: 'string'\n              }\n            }\n          },\n          required: [            'expected',\n            'inputs',\n            'metadata'\n          ]\n        },\n        jsonSchema: {\n          type: 'object',\n          description: 'The JSON schema for each Testcase in the Testset.',\n          additionalProperties: true\n        },\n        name: {\n          type: 'string',\n          description: 'The name of the Testset.'\n        }\n      },\n      required: [        'id',\n        'description',\n        'fieldMapping',\n        'jsonSchema',\n        'name'\n      ]\n    }\n  }\n}\n```",
   inputSchema: {
     type: 'object',
     properties: {
@@ -61,18 +61,27 @@ export const tool: Tool = {
       jsonSchema: {
         type: 'object',
         description: 'The JSON schema for each Testcase in the Testset.',
+        additionalProperties: true,
       },
       name: {
         type: 'string',
         description: 'The name of the Testset.',
       },
+      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: ['testsetId'],
   },
+  annotations: {},
 };
 
 export const handler = async (client: Scorecard, args: Record<string, unknown> | undefined) => {
-  const { testsetId, ...body } = args as any;
-  return asTextContentResult(await client.testsets.update(testsetId, body));
+  const { testsetId, jq_filter, ...body } = args as any;
+  return asTextContentResult(await maybeFilter(jq_filter, await client.testsets.update(testsetId, body)));
 };
 
 export default { metadata, tool, handler };

package/src/tools/types.ts

@@ -47,7 +47,7 @@ export type HandlerFunction = (
   args: Record<string, unknown> | undefined,
 ) => Promise<ToolCallResult>;
 
-export function asTextContentResult(result: Object): ToolCallResult {
+export function asTextContentResult(result: unknown): ToolCallResult {
   return {
     content: [
       {

package/stdio.d.mts

@@ -0,0 +1,3 @@
+import { McpOptions } from "./options.mjs";
+export declare const launchStdioServer: (options: McpOptions) => Promise<void>;
+//# sourceMappingURL=stdio.d.mts.map

package/stdio.d.mts.map

@@ -0,0 +1 @@
+{"version":3,"file":"stdio.d.mts","sourceRoot":"","sources":["src/stdio.ts"],"names":[],"mappings":"OAEO,EAAE,UAAU,EAAE;AAErB,eAAO,MAAM,iBAAiB,GAAU,SAAS,UAAU,kBAQ1D,CAAC"}

package/stdio.d.ts

@@ -0,0 +1,3 @@
+import { McpOptions } from "./options.js";
+export declare const launchStdioServer: (options: McpOptions) => Promise<void>;
+//# sourceMappingURL=stdio.d.ts.map

package/stdio.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"stdio.d.ts","sourceRoot":"","sources":["src/stdio.ts"],"names":[],"mappings":"OAEO,EAAE,UAAU,EAAE;AAErB,eAAO,MAAM,iBAAiB,GAAU,SAAS,UAAU,kBAQ1D,CAAC"}

package/stdio.js

@@ -0,0 +1,14 @@
+"use strict";
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.launchStdioServer = void 0;
+const stdio_js_1 = require("@modelcontextprotocol/sdk/server/stdio.js");
+const server_1 = require("./server.js");
+const launchStdioServer = async (options) => {
+    const server = (0, server_1.newMcpServer)();
+    (0, server_1.initMcpServer)({ server, mcpOptions: options });
+    const transport = new stdio_js_1.StdioServerTransport();
+    await server.connect(transport);
+    console.error('MCP Server running on stdio');
+};
+exports.launchStdioServer = launchStdioServer;
+//# sourceMappingURL=stdio.js.map

package/stdio.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"stdio.js","sourceRoot":"","sources":["src/stdio.ts"],"names":[],"mappings":";;;AAAA,wEAAiF;AACjF,wCAAuD;AAGhD,MAAM,iBAAiB,GAAG,KAAK,EAAE,OAAmB,EAAE,EAAE;IAC7D,MAAM,MAAM,GAAG,IAAA,qBAAY,GAAE,CAAC;IAE9B,IAAA,sBAAa,EAAC,EAAE,MAAM,EAAE,UAAU,EAAE,OAAO,EAAE,CAAC,CAAC;IAE/C,MAAM,SAAS,GAAG,IAAI,+BAAoB,EAAE,CAAC;IAC7C,MAAM,MAAM,CAAC,OAAO,CAAC,SAAS,CAAC,CAAC;IAChC,OAAO,CAAC,KAAK,CAAC,6BAA6B,CAAC,CAAC;AAC/C,CAAC,CAAC;AARW,QAAA,iBAAiB,qBAQ5B"}

package/stdio.mjs

@@ -0,0 +1,10 @@
+import { StdioServerTransport } from '@modelcontextprotocol/sdk/server/stdio.js';
+import { initMcpServer, newMcpServer } from "./server.mjs";
+export const launchStdioServer = async (options) => {
+    const server = newMcpServer();
+    initMcpServer({ server, mcpOptions: options });
+    const transport = new StdioServerTransport();
+    await server.connect(transport);
+    console.error('MCP Server running on stdio');
+};
+//# sourceMappingURL=stdio.mjs.map

package/stdio.mjs.map

@@ -0,0 +1 @@
+{"version":3,"file":"stdio.mjs","sourceRoot":"","sources":["src/stdio.ts"],"names":[],"mappings":"OAAO,EAAE,oBAAoB,EAAE,MAAM,2CAA2C;OACzE,EAAE,aAAa,EAAE,YAAY,EAAE;AAGtC,MAAM,CAAC,MAAM,iBAAiB,GAAG,KAAK,EAAE,OAAmB,EAAE,EAAE;IAC7D,MAAM,MAAM,GAAG,YAAY,EAAE,CAAC;IAE9B,aAAa,CAAC,EAAE,MAAM,EAAE,UAAU,EAAE,OAAO,EAAE,CAAC,CAAC;IAE/C,MAAM,SAAS,GAAG,IAAI,oBAAoB,EAAE,CAAC;IAC7C,MAAM,MAAM,CAAC,OAAO,CAAC,SAAS,CAAC,CAAC;IAChC,OAAO,CAAC,KAAK,CAAC,6BAA6B,CAAC,CAAC;AAC/C,CAAC,CAAC"}

package/tools/metrics/create-metrics.d.mts

@@ -1,5 +1,5 @@
+import { Metadata } from 'scorecard-ai-mcp/tools/types';
 import { Tool } from '@modelcontextprotocol/sdk/types.js';
-import type { Metadata } from "..//index.mjs";
 import Scorecard from 'scorecard-ai';
 export declare const metadata: Metadata;
 export declare const tool: Tool;

package/tools/metrics/create-metrics.d.mts.map

@@ -1 +1 @@
-{"version":3,"file":"create-metrics.d.mts","sourceRoot":"","sources":["../../src/tools/metrics/create-metrics.ts"],"names":[],"mappings":"OAIO,EAAE,IAAI,EAAE,MAAM,oCAAoC;OAClD,KAAK,EAAE,QAAQ,EAAE;OACjB,SAAS,MAAM,cAAc;AAEpC,eAAO,MAAM,QAAQ,EAAE,QAOtB,CAAC;AAEF,eAAO,MAAM,IAAI,EAAE,IAmOlB,CAAC;AAEF,eAAO,MAAM,OAAO,GAAU,QAAQ,SAAS,EAAE,MAAM,MAAM,CAAC,MAAM,EAAE,OAAO,CAAC,GAAG,SAAS,mEAGzF,CAAC;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;sBAHoC,SAAS,QAAQ,MAAM,CAAC,MAAM,EAAE,OAAO,CAAC,GAAG,SAAS;;AAK1F,wBAA2C"}
+{"version":3,"file":"create-metrics.d.mts","sourceRoot":"","sources":["../../src/tools/metrics/create-metrics.ts"],"names":[],"mappings":"OAEO,EAAE,QAAQ,EAAuB,MAAM,8BAA8B;OAErE,EAAE,IAAI,EAAE,MAAM,oCAAoC;OAClD,SAAS,MAAM,cAAc;AAEpC,eAAO,MAAM,QAAQ,EAAE,QAOtB,CAAC;AAEF,eAAO,MAAM,IAAI,EAAE,IA0OlB,CAAC;AAEF,eAAO,MAAM,OAAO,GAAU,QAAQ,SAAS,EAAE,MAAM,MAAM,CAAC,MAAM,EAAE,OAAO,CAAC,GAAG,SAAS,mEAGzF,CAAC;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;sBAHoC,SAAS,QAAQ,MAAM,CAAC,MAAM,EAAE,OAAO,CAAC,GAAG,SAAS;;AAK1F,wBAA2C"}

package/tools/metrics/create-metrics.d.ts

@@ -1,5 +1,5 @@
+import { Metadata } from 'scorecard-ai-mcp/tools/types';
 import { Tool } from '@modelcontextprotocol/sdk/types.js';
-import type { Metadata } from "..//index.js";
 import Scorecard from 'scorecard-ai';
 export declare const metadata: Metadata;
 export declare const tool: Tool;

package/tools/metrics/create-metrics.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"create-metrics.d.ts","sourceRoot":"","sources":["../../src/tools/metrics/create-metrics.ts"],"names":[],"mappings":"OAIO,EAAE,IAAI,EAAE,MAAM,oCAAoC;OAClD,KAAK,EAAE,QAAQ,EAAE;OACjB,SAAS,MAAM,cAAc;AAEpC,eAAO,MAAM,QAAQ,EAAE,QAOtB,CAAC;AAEF,eAAO,MAAM,IAAI,EAAE,IAmOlB,CAAC;AAEF,eAAO,MAAM,OAAO,GAAU,QAAQ,SAAS,EAAE,MAAM,MAAM,CAAC,MAAM,EAAE,OAAO,CAAC,GAAG,SAAS,mEAGzF,CAAC;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;sBAHoC,SAAS,QAAQ,MAAM,CAAC,MAAM,EAAE,OAAO,CAAC,GAAG,SAAS;;AAK1F,wBAA2C"}
+{"version":3,"file":"create-metrics.d.ts","sourceRoot":"","sources":["../../src/tools/metrics/create-metrics.ts"],"names":[],"mappings":"OAEO,EAAE,QAAQ,EAAuB,MAAM,8BAA8B;OAErE,EAAE,IAAI,EAAE,MAAM,oCAAoC;OAClD,SAAS,MAAM,cAAc;AAEpC,eAAO,MAAM,QAAQ,EAAE,QAOtB,CAAC;AAEF,eAAO,MAAM,IAAI,EAAE,IA0OlB,CAAC;AAEF,eAAO,MAAM,OAAO,GAAU,QAAQ,SAAS,EAAE,MAAM,MAAM,CAAC,MAAM,EAAE,OAAO,CAAC,GAAG,SAAS,mEAGzF,CAAC;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;sBAHoC,SAAS,QAAQ,MAAM,CAAC,MAAM,EAAE,OAAO,CAAC,GAAG,SAAS;;AAK1F,wBAA2C"}