Skip to main content
Glama
us-all

openmetadata-mcp-server

by us-all

create-tag

Create a new tag by specifying its parent classification, name, and description. Optionally set a display name and style like color.

Instructions

Create a new tag under a classification

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
classificationYesFQN of the parent classification
nameYesTag name
descriptionYesTag description in markdown
displayNameNoDisplay name
styleNoTag style (e.g. color)

Implementation Reference

  • The handler function for create-tag tool. Validates write permissions and POSTs to /tags endpoint.
    export async function createTag(params: z.infer<typeof createTagSchema>) {
      assertWriteAllowed();
      return omClient.post("/tags", params);
    }
  • Zod schema defining the input parameters for create-tag: classification (FQN), name, description, optional displayName, and optional style.
    export const createTagSchema = z.object({
      classification: z.string().describe("FQN of the parent classification"),
      name: z.string().describe("Tag name"),
      description: z.string().describe("Tag description in markdown"),
      displayName: z.string().optional().describe("Display name"),
      style: z.record(z.string(), z.any()).optional().describe("Tag style (e.g. color)"),
    });
  • src/index.ts:330-330 (registration)
    Registration of the create-tag tool with MCP server, binding the schema and handler.
    tool("create-tag", "Create a new tag under a classification", createTagSchema.shape, wrapToolHandler(createTag));
Behavior2/5

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

The description lacks any behavioral details beyond the basic action. There is no mention of idempotency, error handling, permission requirements, or side effects. Since no annotations are provided, the description carries the full burden but fails to disclose important traits.

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 front-loads the core purpose. It avoids wordiness, but could benefit from a brief second sentence clarifying key constraints or behavior.

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 no output schema, the description should explain what is returned (e.g., the created tag object). It also omits context about uniqueness, validation of the classification FQN, and any side effects. The description is too sparse for a creation tool with moderate complexity.

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?

The input schema already provides descriptions for all 5 parameters (100% coverage). The description adds minimal context by linking the tag to a classification but does not explain terminology like 'FQN' or the structure of the 'style' object, which would be helpful beyond the schema.

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 action ('create'), the resource ('tag'), and the context ('under a classification'). It effectively distinguishes this tool from siblings like 'create-classification' and other create-* tools by specifying the hierarchical relationship.

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 (e.g., when to create a tag vs update an existing one). It does not mention prerequisites such as the classification already existing or any constraints on naming.

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