Skip to main content
Glama
us-all

openmetadata-mcp-server

by us-all

delete-lineage

Remove a lineage connection between two data entities by providing their entity types and UUIDs.

Instructions

Delete a lineage edge between two entities

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fromEntityYesSource entity type (e.g. 'table')
fromIdYesSource entity UUID
toEntityYesTarget entity type
toIdYesTarget entity UUID

Implementation Reference

  • The actual handler function that executes the delete-lineage tool logic. It calls assertWriteAllowed() and then sends a DELETE request to /lineage/{fromEntity}/{fromId}/{toEntity}/{toId}.
    export async function deleteLineage(params: z.infer<typeof deleteLineageSchema>) {
      assertWriteAllowed();
      return omClient.delete(`/lineage/${params.fromEntity}/${params.fromId}/${params.toEntity}/${params.toId}`);
    }
  • Zod schema defining the input parameters for delete-lineage: fromEntity, fromId, toEntity, toId (all strings).
    export const deleteLineageSchema = z.object({
      fromEntity: z.string().describe("Source entity type (e.g. 'table')"),
      fromId: z.string().describe("Source entity UUID"),
      toEntity: z.string().describe("Target entity type"),
      toId: z.string().describe("Target entity UUID"),
    });
  • src/index.ts:206-206 (registration)
    Registration of the 'delete-lineage' tool with the MCP server, linking its schema and handler via wrapToolHandler.
    tool("delete-lineage", "Delete a lineage edge between two entities", deleteLineageSchema.shape, wrapToolHandler(deleteLineage));
Behavior2/5

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

No annotations exist, so description must disclose behavior. Only states 'delete', but does not mention permissions, whether operation is reversible, error conditions (e.g., edge not found), or idempotency.

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 concise sentence, front-loaded with key action and resource, no wasted words.

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?

No output schema, so description should clarify return value or success indicator. It does not. Despite many sibling delete tools, the description differentiates by mentioning 'lineage edge', but lacks completeness on behavior and result.

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?

Input schema has 100% coverage with descriptions for all 4 parameters; the description adds no extra meaning beyond the schema. Baseline of 3 is appropriate.

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?

Description clearly states the action (delete), the resource (lineage edge), and the context (between two entities). It distinguishes from sibling `add-lineage` which performs the opposite operation.

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 vs alternatives (e.g., `add-lineage`), nor any prerequisites (e.g., edge must exist). No exclusions or cautionary notes provided.

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