Skip to main content
Glama
us-all

openmetadata-mcp-server

by us-all

get-data-product-by-name

Retrieve details of a data product using its fully qualified name. Specify fields and include status for customized results.

Instructions

Get data product by fully qualified name

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fqnYesFully qualified name of the data product
fieldsNoComma-separated fields to include
includeNo

Implementation Reference

  • Zod schema defining the input for get-data-product-by-name: requires 'fqn' (fully qualified name), optional 'fields' and 'include'.
    export const getDataProductByNameSchema = z.object({
      fqn: z.string().describe("Fully qualified name of the data product"),
      fields: z.string().optional().describe("Comma-separated fields to include"),
      include: z.enum(["non-deleted", "deleted", "all"]).optional(),
    });
  • Handler function that calls the API endpoint /dataProducts/name/{fqn} to get a data product by its fully qualified name.
    export async function getDataProductByName(params: z.infer<typeof getDataProductByNameSchema>) {
      const { fqn, ...query } = params;
      return omClient.get(`/dataProducts/name/${encodeURIComponent(fqn)}`, query);
    }
  • src/index.ts:347-347 (registration)
    Registration of the tool with name 'get-data-product-by-name', description, schema shape, and wrapped handler.
    tool("get-data-product-by-name", "Get data product by fully qualified name", getDataProductByNameSchema.shape, wrapToolHandler(getDataProductByName));
Behavior2/5

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

No annotations are provided, so the description must convey behavioral traits. It only states the retrieval action, omitting any mention of side effects (none expected), authorization needs, rate limits, or default behavior for the 'include' parameter (e.g., non-deleted by default). Minimal transparency.

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

Conciseness3/5

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

The description is a single sentence, making it very concise. However, it lacks structure and fails to front-load critical information like parameter usage or sibling differentiation. It is short but not efficient in conveying useful guidance.

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 parameter complexity (three params, one with enum) and the presence of siblings, the description is incomplete. It does not explain the 'include' parameter's effect on results, nor does it mention return format or pagination. No output schema exists to fill gaps.

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%, with two parameters having descriptions in the schema itself. The description adds no extra meaning beyond the schema's 'fqn' parameter. The 'fields' and 'include' parameters are not elaborated, leaving their purpose unclear despite schema descriptions for two of them.

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 (data product) by a specific identifier (fully qualified name). However, it does not differentiate from siblings like 'get-data-product' or 'list-data-products', missing an opportunity to clarify its unique role.

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?

The description provides no guidance on when to use this tool versus alternatives. Siblings such as 'get-data-product' and 'list-data-products' exist, but no context is given for choosing this one. No exclusions or prerequisites are mentioned.

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