Skip to main content
Glama
us-all

openmetadata-mcp-server

by us-all

get-tag-by-name

Fetch tag details by specifying the fully qualified name. Optionally include fields and filter by deletion status.

Instructions

Get tag by fully qualified name

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fqnYesFully qualified name (e.g. 'Classification.TagName')
fieldsNoComma-separated fields to include
includeNo

Implementation Reference

  • The handler function that executes the 'get-tag-by-name' tool logic. It accepts params with 'fqn' (fully qualified name), optional 'fields', and optional 'include', then calls omClient.get on the /tags/name/:fqn endpoint.
    export async function getTagByName(params: z.infer<typeof getTagByNameSchema>) {
      const { fqn, ...query } = params;
      return omClient.get(`/tags/name/${encodeURIComponent(fqn)}`, query);
    }
  • Zod schema for the 'get-tag-by-name' tool, defining the input parameters: fqn (string), fields (optional string), include (optional enum: non-deleted, deleted, all).
    export const getTagByNameSchema = z.object({
      fqn: z.string().describe("Fully qualified name (e.g. 'Classification.TagName')"),
      fields: z.string().optional().describe("Comma-separated fields to include"),
      include: z.enum(["non-deleted", "deleted", "all"]).optional(),
    });
  • src/index.ts:329-329 (registration)
    Registration of the 'get-tag-by-name' tool with the MCP server, binding the schema (getTagByNameSchema.shape) and handler (getTagByName) via wrapToolHandler.
    tool("get-tag-by-name", "Get tag by fully qualified name", getTagByNameSchema.shape, wrapToolHandler(getTagByName));
  • The tool registration helper function that wraps schema and handler, applies category-based filtering (OM_TOOLS / OM_DISABLE), and registers with the MCP server.
    function tool(name: string, description: string, schema: any, handler: any): void {
      registry.register(name, description, currentCategory);
      if (registry.isEnabled(currentCategory)) {
        server.tool(name, description, schema, handler);
      }
    }
Behavior2/5

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

No annotations provided, and the description does not disclose any behavioral traits such as permissions, side effects, or response format. The tool is a simple getter, but transparency is minimal.

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?

Extremely concise: a single sentence that gets straight to the point. No unnecessary words or redundancy.

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?

Given the simplicity of the tool and good schema coverage, the description is adequate but lacks mention of return values or additional context. Could be more complete with a brief note on output.

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 covers parameters well with descriptions for 'fqn' and 'fields', and an enum for 'include'. The tool description adds no extra parameter information, so baseline score is appropriate.

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 'Get tag by fully qualified name' clearly states the verb and resource. It distinguishes from siblings like 'get-chart-by-name' by specifying 'tag', but does not explicitly differentiate from 'get-tag' (if it exists). However, the purpose is clear.

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 versus alternatives like 'get-tag' or 'list-tags'. The description does not mention context, prerequisites, or 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