Skip to main content
Glama
us-all

openmetadata-mcp-server

by us-all

get-test-suite-by-name

Retrieve a test suite by its fully qualified name from OpenMetadata. Optionally specify included fields and deletion status for refined results.

Instructions

Get test suite by fully qualified name

Input Schema

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

Implementation Reference

  • The handler function that executes the get-test-suite-by-name tool. It extracts the 'fqn' parameter and makes a GET request to /dataQuality/testSuites/name/{fqn} using the OpenMetadata API client.
    export async function getTestSuiteByName(params: z.infer<typeof getTestSuiteByNameSchema>) {
      const { fqn, ...query } = params;
      return omClient.get(`/dataQuality/testSuites/name/${encodeURIComponent(fqn)}`, query);
    }
  • Zod schema for get-test-suite-by-name tool, defining input parameters: fqn (required string), fields (optional string), include (optional enum 'non-deleted', 'deleted', 'all').
    export const getTestSuiteByNameSchema = z.object({
      fqn: z.string().describe("Fully qualified name of the test suite"),
      fields: z.string().optional().describe("Comma-separated fields to include"),
      include: z.enum(["non-deleted", "deleted", "all"]).optional(),
    });
  • src/index.ts:383-383 (registration)
    Registration of the tool 'get-test-suite-by-name' with its schema and handler via the tool() function.
    tool("get-test-suite-by-name", "Get test suite by fully qualified name", getTestSuiteByNameSchema.shape, wrapToolHandler(getTestSuiteByName));
  • src/index.ts:107-112 (registration)
    Import of getTestSuiteByNameSchema and getTestSuiteByName from the data-quality tools 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 provided, the description must convey behavioral traits. It only states the basic retrieve action, omitting details like read-only nature, potential return of deleted suites (hinted by the 'include' parameter), or any side effects. The description adds no behavioral context beyond the name.

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

Conciseness4/5

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

The description is a single sentence with no wasted words. It is front-loaded with the action and resource. Slightly more detail could be added without harming conciseness, but it is effectively brief.

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 the tool has three parameters, no output schema, and no annotations, the description is incomplete. It does not explain the effect of the 'include' parameter (e.g., ability to retrieve deleted suites) or what the response contains. The agent missing key context for proper usage.

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?

The input schema descriptions are fairly detailed for 'fqn' and 'fields' (67% coverage). The description adds no additional meaning to the parameters, such as explaining the 'include' enum or how 'fields' works. Baseline 3 is appropriate as the schema carries most of the burden.

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 verb 'Get' and the resource 'test suite', and specifies the identification method 'by fully qualified name'. It distinguishes from sibling tools like 'list-test-suites' (list) and 'get-test-case-by-name' (different resource), but does not explicitly differentiate from 'get-test-suite', which could be ambiguous.

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 like 'get-test-suite' or 'list-test-suites'. There is no mention of prerequisites, context, or when not to use it. The agent is left to infer from the name alone.

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