Skip to main content
Glama
us-all

openmetadata-mcp-server

by us-all

list-test-cases

List data quality test cases with filters for entity link, test suite, pagination, and field selection.

Instructions

List data quality test cases with filtering

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fieldsNoComma-separated fields to include
limitNoNumber of results per page
beforeNoCursor for backward pagination
afterNoCursor for forward pagination
entityLinkNoFilter by entity link (e.g. '<#E::table::service.db.schema.table>')
testSuiteIdNoFilter by test suite UUID
includeNoInclude deleted entitiesnon-deleted
extractFieldsNoComma-separated dotted paths to project from response (e.g. 'id,name,owner.name,columns.*.name'). Use `*` as wildcard for arrays/objects. Wrap field names with dots in backticks. Reduces response tokens dramatically on large entities.

Implementation Reference

  • Handler function that executes the list-test-cases tool logic. Calls the OpenMetadata API at /dataQuality/testCases with query params (fields, limit, before, after, entityLink, testSuiteId, include), then applies extractFields to shape the response.
    export async function listTestCases(params: z.infer<typeof listTestCasesSchema>) {
      const { extractFields, ...query } = params;
      const data = await omClient.get("/dataQuality/testCases", query);
      return applyExtractFields(data, extractFields ?? LIST_TEST_CASES_DEFAULT_FIELDS);
    }
  • Zod schema defining the input parameters for list-test-cases: fields, limit (default 10), before/after cursors, entityLink filter, testSuiteId filter, include (default 'non-deleted'), and extractFields.
    export const listTestCasesSchema = z.object({
      fields: z.string().optional().describe("Comma-separated fields to include"),
      limit: z.coerce.number().optional().default(10).describe("Number of results per page"),
      before: z.string().optional().describe("Cursor for backward pagination"),
      after: z.string().optional().describe("Cursor for forward pagination"),
      entityLink: z.string().optional().describe("Filter by entity link (e.g. '<#E::table::service.db.schema.table>')"),
      testSuiteId: z.string().optional().describe("Filter by test suite UUID"),
      include: z.enum(["non-deleted", "deleted", "all"]).optional().default("non-deleted").describe("Include deleted entities"),
      extractFields: z.string().optional().describe(extractFieldsDescription),
    });
  • src/index.ts:384-384 (registration)
    Registration of the 'list-test-cases' tool in the MCP server using McpServer.tool(), wiring the schema and handler together.
    tool("list-test-cases", "List data quality test cases with filtering", listTestCasesSchema.shape, wrapToolHandler(listTestCases));
  • Default fields constant used for list-test-cases when no extractFields is provided: includes id, name, fullyQualifiedName, testSuite.fullyQualifiedName, testCaseStatus, testCaseResult, and paging.
    const LIST_TEST_CASES_DEFAULT_FIELDS = "data.*.id,data.*.name,data.*.fullyQualifiedName,data.*.testSuite.fullyQualifiedName,data.*.testCaseStatus,data.*.testCaseResult,paging";
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations provided, so description must disclose behavior. It only says 'list' and 'with filtering', omitting pagination, return format, and non-destructive nature, which are critical for a tool with 8 parameters.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Single sentence, front-loaded with verb and resource, no extraneous words; perfectly concise for a simple listing tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 8 parameters and no output schema, description lacks details on pagination, default behavior, and what the response contains; minimally adequate but incomplete for full understanding.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so baseline is 3. Description adds 'with filtering' but that's already implied by the parameter names and descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Clearly states it lists data quality test cases with filtering, distinguishing it from sibling list tools for other entities like list-tables, list-test-case-results, and list-test-suites.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Implied usage context (list test cases) but no explicit when-to-use or when-not-to-use compared to alternatives like list-test-case-results.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/us-all/openmetadata-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server