Skip to main content
Glama
us-all

openmetadata-mcp-server

by us-all

get-test-case-by-name

Retrieve a test case by its fully qualified name. Optionally specify fields and inclusion status to get detailed metadata.

Instructions

Get test case by fully qualified name

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fqnYesFully qualified name of the test case
fieldsNoComma-separated fields to include
includeNo

Implementation Reference

  • The handler function that executes the 'get-test-case-by-name' tool. It takes a 'fqn' (fully qualified name) and optional 'fields'/'include' params, then makes a GET request to /dataQuality/testCases/name/{fqn}.
    export async function getTestCaseByName(params: z.infer<typeof getTestCaseByNameSchema>) {
      const { fqn, ...query } = params;
      return omClient.get(`/dataQuality/testCases/name/${encodeURIComponent(fqn)}`, query);
    }
  • The Zod schema for 'get-test-case-by-name'. Defines the input parameters: 'fqn' (required string), 'fields' (optional string), and 'include' (optional enum).
    export const getTestCaseByNameSchema = z.object({
      fqn: z.string().describe("Fully qualified name of the test case"),
      fields: z.string().optional().describe("Comma-separated fields to include"),
      include: z.enum(["non-deleted", "deleted", "all"]).optional(),
    });
  • src/index.ts:386-386 (registration)
    Tool registration using the MCP server's tool() function with schema and handler.
    tool("get-test-case-by-name", "Get test case by fully qualified name", getTestCaseByNameSchema.shape, wrapToolHandler(getTestCaseByName));
  • src/index.ts:107-112 (registration)
    Import statement for the getTestCaseByName handler and schema from the data-quality module.
    import {
      listTestSuitesSchema, listTestSuites, getTestSuiteSchema, getTestSuite,
      getTestSuiteByNameSchema, getTestSuiteByName, listTestCasesSchema, listTestCases,
      getTestCaseSchema, getTestCase, getTestCaseByNameSchema, getTestCaseByName,
      listTestCaseResultsSchema, listTestCaseResults,
    } from "./tools/data-quality.js";
Behavior2/5

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

With no annotations, the description carries full burden for behavioral disclosure. It fails to state that the operation is read-only, safe, or what happens on failure (e.g., not found). Minimal information beyond purpose.

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 that is perfectly concise and front-loaded with the essential information. No unnecessary words or filler.

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

Completeness2/5

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

Given three parameters and no output schema, the description is too sparse. It does not explain the return format, pagination, or how 'include' affects results. Incomplete for effective usage.

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

Parameters2/5

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

Schema coverage is 67%, but the description adds no value beyond what the schema already provides. The parameters 'fields' and 'include' are not explained, and their formats or constraints are left unspecified.

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

Purpose4/5

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

The description clearly states the action 'get' and the resource 'test case' with the key qualifier 'by fully qualified name'. It effectively distinguishes from siblings like 'get-test-case' which likely uses a different identifier.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives. Missing context on when a fully qualified name is required versus other lookup methods, and no mention of prerequisites or exclusions.

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