Skip to main content
Glama
us-all

openmetadata-mcp-server

by us-all

delete-classification

Delete a tag classification by UUID. Supports hard delete and recursive deletion of children.

Instructions

Delete a tag classification

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesClassification UUID to delete
hardDeleteNoHard delete (permanent) vs soft delete
recursiveNoRecursively delete children

Implementation Reference

  • The handler function that executes delete-classification logic. Calls assertWriteAllowed(), then sends a DELETE request to /classifications/{id} with hardDelete and recursive params.
    export async function deleteClassification(params: z.infer<typeof deleteClassificationSchema>) {
      assertWriteAllowed();
      return omClient.delete(`/classifications/${params.id}`, {
        hardDelete: params.hardDelete,
        recursive: params.recursive,
      });
    }
  • Zod schema for delete-classification input: id (string), hardDelete (optional boolean, default false), recursive (optional boolean, default false).
    export const deleteClassificationSchema = z.object({
      id: z.string().describe("Classification UUID to delete"),
      hardDelete: z.boolean().optional().default(false).describe("Hard delete (permanent) vs soft delete"),
      recursive: z.boolean().optional().default(false).describe("Recursively delete children"),
    });
  • src/index.ts:323-323 (registration)
    Registration of the delete-classification tool using tool() with its schema and wrapped handler.
    tool("delete-classification", "Delete a tag classification", deleteClassificationSchema.shape, wrapToolHandler(deleteClassification));
Behavior2/5

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

No annotations are present, so the description carries the full burden. It merely restates the action without disclosing behavioral traits such as destructiveness, reversibility (soft vs. hard delete), or recursive deletion behavior. The schema includes parameters for these, but the description adds no context.

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, concise sentence that quickly conveys the core purpose. While it is minimal, it avoids verbosity and earns its place. However, it could be slightly more informative without losing conciseness.

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 3 parameters and no output schema or annotations, the description is incomplete. It fails to explain key behaviors like hard vs. soft delete, recursive deletion, or what happens after deletion. The agent lacks sufficient context to use the tool reliably.

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?

Schema description coverage is 100%, so the input schema already defines all parameters adequately. The description adds no additional meaning beyond what's in the schema. Per guidelines, baseline is 3, which is appropriate here.

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 'Delete a tag classification' clearly states the verb and resource, making the tool's purpose immediately understandable. However, it does not differentiate from sibling tools like 'delete-tag', which might cause confusion if tag and tag classification are distinct entities.

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 usage guidance is provided. The description does not specify when to use this tool over alternatives, what prerequisites are needed, or any side effects. This leaves the agent to infer usage from context, which is insufficient.

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