Skip to main content
Glama
yangkyeongmo

MCP Server for OpenMetadata

by yangkyeongmo

delete_user

Deletes a user from OpenMetadata by user ID. Choose hard delete or recursive removal to also delete associated resources.

Instructions

Delete a user from OpenMetadata

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
user_idYes
hard_deleteNo
recursiveNo
Behavior2/5

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

The description only says 'delete', implying destruction, but lacks details on reversibility, cascading effects, or required permissions. With no annotations, the description should offer more behavioral context.

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 and front-loaded, but it sacrifices essential information, making it barely adequate.

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 three parameters with no schema descriptions, no annotations, and no output schema, the description fails to provide necessary details about behavior, parameter roles, or return values, making it incomplete for safe use.

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?

The schema has 0% description coverage for its three parameters, and the description adds no information about user_id, hard_delete, or recursive. The parameter names give hints, but the description should explain their meaning and usage.

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 clearly states the verb 'Delete' and the resource 'user from OpenMetadata', making it specific and distinct from sibling tools like delete_bot or delete_chart.

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 on when to set the hard_delete or recursive parameters. For example, it does not explain if a soft delete is available via update_user.

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/yangkyeongmo/mcp-server-openmetadata'

If you have feedback or need assistance with the MCP directory API, please join our Discord server