Skip to main content
Glama
us-all

openmetadata-mcp-server

by us-all

delete-glossary

Remove a glossary using its unique identifier. Supports hard deletion and recursive removal of all related terms.

Instructions

Delete a glossary by UUID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesGlossary UUID
hardDeleteNo
recursiveNo

Implementation Reference

  • Zod schema for the delete-glossary tool: accepts 'id' (UUID), optional 'hardDelete' (boolean, default false), and optional 'recursive' (boolean, default false).
    export const deleteGlossarySchema = z.object({
      id: z.string().describe("Glossary UUID"),
      hardDelete: z.boolean().optional().default(false),
      recursive: z.boolean().optional().default(false),
    });
  • Handler function for delete-glossary: checks write permissions, then sends a DELETE request to /glossaries/{id} with query params hardDelete and recursive.
    export async function deleteGlossary(params: z.infer<typeof deleteGlossarySchema>) {
      assertWriteAllowed();
      return omClient.delete(`/glossaries/${params.id}`, {
        hardDelete: params.hardDelete,
        recursive: params.recursive,
      });
    }
  • src/index.ts:48-55 (registration)
    Import of deleteGlossarySchema and deleteGlossary from ./tools/glossary.ts into the main index file.
    import {
      listGlossariesSchema, listGlossaries, getGlossarySchema, getGlossary,
      getGlossaryByNameSchema, getGlossaryByName, createGlossarySchema, createGlossary,
      updateGlossarySchema, updateGlossary, deleteGlossarySchema, deleteGlossary,
      listGlossaryTermsSchema, listGlossaryTerms, getGlossaryTermSchema, getGlossaryTerm,
      getGlossaryTermByNameSchema, getGlossaryTermByName, createGlossaryTermSchema, createGlossaryTerm,
      updateGlossaryTermSchema, updateGlossaryTerm, deleteGlossaryTermSchema, deleteGlossaryTerm,
    } from "./tools/glossary.js";
  • src/index.ts:251-251 (registration)
    Registration of the 'delete-glossary' tool with the MCP server using tool(), linking the schema shape and wrapped handler.
    tool("delete-glossary", "Delete a glossary by UUID", deleteGlossarySchema.shape, wrapToolHandler(deleteGlossary));
Behavior2/5

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

With no annotations, the description carries the full burden. It does not disclose that deletion may be soft or hard, or whether it cascades to child terms. The parameters 'hardDelete' and 'recursive' are not explained in the description, leaving the behavior unclear.

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?

A single, front-loaded sentence with no extraneous words. Every word serves a clear purpose.

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 three parameters, no output schema, and no annotations, the description is insufficient. Key behaviors (e.g., return value, effect of boolean flags) are missing, leaving the agent without enough context to use the tool correctly.

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?

Only 33% of parameters have schema descriptions. The description adds 'by UUID' for the 'id' parameter but does not explain 'hardDelete' or 'recursive', which are critical for understanding the tool's effect.

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 'Delete' and resource 'glossary' with the method 'by UUID', distinguishing from sibling delete tools for other entities. However, it could be improved by mentioning the optional parameters that affect the deletion behavior.

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 is provided on when to use this tool versus alternatives (e.g., 'delete-glossary-term' for individual terms). There is no mention of prerequisites or conditions for safe usage.

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