Skip to main content
Glama
us-all

openmetadata-mcp-server

by us-all

delete-query

Delete a saved query by UUID with optional hard delete for permanent removal.

Instructions

Delete a saved query by UUID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesQuery UUID to delete
hardDeleteNoHard delete (permanent) vs soft delete

Implementation Reference

  • The handler function for 'delete-query'. Calls assertWriteAllowed() and then sends a DELETE request to /queries/:id with an optional hardDelete parameter.
    export async function deleteQuery(params: z.infer<typeof deleteQuerySchema>) {
      assertWriteAllowed();
      return omClient.delete(`/queries/${params.id}`, {
        hardDelete: params.hardDelete,
      });
    }
  • Zod schema for 'delete-query' input validation. Requires id (string UUID) and optional hardDelete (boolean, default false).
    export const deleteQuerySchema = z.object({
      id: z.string().describe("Query UUID to delete"),
      hardDelete: z.boolean().optional().default(false).describe("Hard delete (permanent) vs soft delete"),
    });
  • src/index.ts:405-405 (registration)
    Registration of the 'delete-query' tool with the MCP server, using deleteQuerySchema for input shape and wrapToolHandler(deleteQuery) as handler.
    tool("delete-query", "Delete a saved query by UUID", deleteQuerySchema.shape, wrapToolHandler(deleteQuery));
  • The omClient.delete method used by the deleteQuery handler. Sends an HTTP DELETE with query params.
    async delete<T = unknown>(path: string, params?: Record<string, string | number | boolean | undefined>): Promise<T> {
      return this.request<T>("DELETE", path, { params });
    }
  • The assertWriteAllowed helper used in the deleteQuery handler to guard against write operations when writes are disabled.
    export function assertWriteAllowed(): void {
      if (!config.allowWrite) {
        throw new WriteBlockedError();
      }
    }
Behavior2/5

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

With no annotations, the description carries full burden for behavioral disclosure. It only states deletion by UUID but omits critical details: the existence of hard vs soft delete (though the hardDelete param exists, the description doesn't mention it), permissions, irreversibility, or side effects. The description is insufficient for safe invocation.

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 of 5 words, conveying the core purpose efficiently. No unnecessary words, though the trade-off is some lack of detail; still good for a simple tool.

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 presence of two parameters and no output schema or annotations, the description should at least mention the soft/hard delete distinction to avoid accidental permanent deletion. The description is incomplete for safe and effective use.

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 coverage is 100% (both parameters have descriptions in the schema). The description adds no additional meaning beyond what the schema already provides, so a baseline score 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?

The description 'Delete a saved query by UUID' clearly states the action (delete), the resource (saved query), and the identifier method (by UUID). This distinguishes it from sibling tools like 'update-query' or 'create-query', and from other delete tools targeting different 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 guidance on when to use this tool vs alternatives like 'update-query' or when to choose hard vs soft delete. The description does not mention any context or exclusions, leaving the agent with ambiguous decision boundaries.

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