Skip to main content
Glama
us-all

openmetadata-mcp-server

by us-all

get-tag

Retrieve tag details by providing its UUID. Specify fields and include status for filtered results.

Instructions

Get tag details by UUID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesTag UUID
fieldsNoComma-separated fields to include
includeNo

Implementation Reference

  • Zod schema for 'get-tag' tool: validates id (UUID), optional fields, and optional include filter.
    export const getTagSchema = z.object({
      id: z.string().describe("Tag UUID"),
      fields: z.string().optional().describe("Comma-separated fields to include"),
      include: z.enum(["non-deleted", "deleted", "all"]).optional(),
    });
    
    export async function getTag(params: z.infer<typeof getTagSchema>) {
      const { id, ...query } = params;
      return omClient.get(`/tags/${id}`, query);
    }
  • Handler function for 'get-tag': extracts id and query params, then calls GET /tags/{id} on the OpenMetadata client.
    export async function getTag(params: z.infer<typeof getTagSchema>) {
      const { id, ...query } = params;
      return omClient.get(`/tags/${id}`, query);
    }
  • src/index.ts:89-91 (registration)
    Import of getTagSchema and getTag from tools/tags.ts into the main server file.
      listTagsSchema, listTags, getTagSchema, getTag, getTagByNameSchema, getTagByName,
      createTagSchema, createTag, updateTagSchema, updateTag, deleteTagSchema, deleteTag,
    } from "./tools/tags.js";
  • src/index.ts:328-328 (registration)
    Registration of 'get-tag' tool on the MCP server with the schema and wrapped handler.
    tool("get-tag", "Get tag details by UUID", getTagSchema.shape, wrapToolHandler(getTag));
Behavior2/5

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

With no annotations, the description fails to disclose behavioral traits like handling of missing UUIDs, default inclusion of deleted tags, or error responses.

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?

Single sentence, no unnecessary words, front-loaded with the core action.

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

Completeness3/5

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

Adequate for a simple get tool, but lacks details on return format and behavior for missing or deleted tags. Output schema absent.

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 67%, not low, so baseline 3. Description adds no extra meaning beyond schema descriptions for id, fields, and include.

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 'Get tag details' and the key resource 'by UUID', distinguishing it from sibling like get-tag-by-name.

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 provided on when to use this tool vs alternatives such as list-tags or get-tag-by-name. Lacks usage context and exclusions.

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