Skip to main content
Glama
us-all

openmetadata-mcp-server

by us-all

get-lineage-by-name

Retrieve upstream and downstream lineage for a data entity using its fully qualified name. Specify entity type and lineage depth.

Instructions

Get upstream and downstream lineage for an entity by FQN

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
entityYesEntity type
fqnYesEntity fully qualified name
upstreamDepthNo
downstreamDepthNo

Implementation Reference

  • src/index.ts:32-34 (registration)
    Import of getLineageByNameSchema and getLineageByName from the lineage module
      getLineageSchema, getLineage, getLineageByNameSchema, getLineageByName,
      addLineageSchema, addLineage, deleteLineageSchema, deleteLineage,
    } from "./tools/lineage.js";
  • src/index.ts:204-204 (registration)
    Tool registration for 'get-lineage-by-name' using the schema and handler
    tool("get-lineage-by-name", "Get upstream and downstream lineage for an entity by FQN", getLineageByNameSchema.shape, wrapToolHandler(getLineageByName));
  • Zod schema for getLineageByName: validates entity (enum), fqn (string), upstreamDepth, downstreamDepth
    export const getLineageByNameSchema = z.object({
      entity: entityTypeEnum,
      fqn: z.string().describe("Entity fully qualified name"),
      upstreamDepth: z.coerce.number().optional().default(1),
      downstreamDepth: z.coerce.number().optional().default(1),
    });
  • Handler function getLineageByName: destructures params, calls omClient.get(`/lineage/${entity}/name/${encodeURIComponent(fqn)}`) with query params
    export async function getLineageByName(params: z.infer<typeof getLineageByNameSchema>) {
      const { entity, fqn, ...query } = params;
      return omClient.get(`/lineage/${entity}/name/${encodeURIComponent(fqn)}`, query);
    }
Behavior2/5

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

No annotations provided, so description must disclose behavioral traits. It only states it retrieves lineage but omits that it is read-only, default depths, and whether any side effects occur. The agent cannot infer safety or constraints.

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?

One efficient sentence with no waste. However, structured elements like bullet points or example usage are absent.

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?

With 4 parameters, no output schema, and no annotations, the description is too sparse. It doesn't explain depth parameters, supported entity types (though schema enum hints), or return shape, leaving the agent underinformed.

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 only 50%; 'entity' and 'fqn' have descriptions, but 'upstreamDepth' and 'downstreamDepth' lack any. The description adds no extra meaning beyond the schema, especially failing to clarify depth defaults or behavior.

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?

The description clearly states the action (get), resource (lineage), and qualifiers (upstream/downstream, by FQN). It distinguishes itself from siblings like 'get-lineage' or 'lineage-impact' by specifying retrieval via fully qualified name.

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-lineage' or 'lineage-impact'. The description lacks context about prerequisites or suitable scenarios.

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