Skip to main content
Glama
us-all

openmetadata-mcp-server

by us-all

delete-database-service

Delete a database service from OpenMetadata by providing its UUID. Optionally perform a hard delete or remove children recursively.

Instructions

Delete a database service

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesService UUID
hardDeleteNo
recursiveNo

Implementation Reference

  • The handler function that deletes a database service. Calls assertWriteAllowed() then sends a DELETE request to /services/databaseServices/{id} with hardDelete and recursive query parameters.
    export async function deleteDatabaseService(params: z.infer<typeof deleteDatabaseServiceSchema>) {
      assertWriteAllowed();
      return omClient.delete(`/services/databaseServices/${params.id}`, {
        hardDelete: params.hardDelete,
        recursive: params.recursive,
      });
    }
  • Zod schema defining input parameters for delete-database-service: id (string, required), hardDelete (boolean, optional, default false), recursive (boolean, optional, default false).
    export const deleteDatabaseServiceSchema = z.object({
      id: z.string().describe("Service UUID"),
      hardDelete: z.boolean().optional().default(false),
      recursive: z.boolean().optional().default(false),
    });
  • src/index.ts:216-216 (registration)
    Registration of the 'delete-database-service' tool in the MCP server using the schema and wrapped handler.
    tool("delete-database-service", "Delete a database service", deleteDatabaseServiceSchema.shape, wrapToolHandler(deleteDatabaseService));
  • Imported assertWriteAllowed helper which enforces that write operations are permitted.
    import { assertWriteAllowed } from "./utils.js";
Behavior2/5

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

With no annotations, the description carries the full burden but only states 'Delete', which implies destruction. It does not explain what actually happens (e.g., whether associated data is removed), the impact of the boolean parameters, or any safety considerations. The description adds minimal behavioral insight beyond the tool's name.

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 short sentence, which is concise, but it does not earn its place because it lacks necessary detail. It is not verbose, but it is also not sufficiently informative.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no annotations, no output schema, and two parameters left unexplained, the description is incomplete. It does not clarify the effects of hardDelete and recursive, return values, or error conditions, leaving critical gaps for safe and correct usage.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With only 33% schema description coverage, the description should compensate but adds no parameter explanations. The schema already has a description for 'id' ('Service UUID'), but 'hardDelete' and 'recursive' remain undefined in both schema and description. This leaves the agent uncertain about their meaning and usage.

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 database service' clearly states the verb and resource, making the purpose immediately understandable. However, it does not distinguish this delete action from sibling delete tools like delete-database or delete-container, missing an opportunity for differentiation.

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 vs alternatives, nor are there any prerequisites or warnings. The agent receives no context about appropriate scenarios or when not to use it.

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