Skip to main content
Glama
us-all

openmetadata-mcp-server

by us-all

get-glossary-term-by-name

Retrieve a glossary term by its fully qualified name. Optionally specify fields to extract for a reduced response.

Instructions

Get glossary term by fully qualified name

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fqnYesTerm FQN (e.g. 'glossary.term')
fieldsNo
extractFieldsNoComma-separated dotted paths to project from response (e.g. 'id,name,owner.name,columns.*.name'). Use `*` as wildcard for arrays/objects. Wrap field names with dots in backticks. Reduces response tokens dramatically on large entities.

Implementation Reference

  • The actual handler function that executes the tool logic. It takes 'fqn' (fully qualified name like 'glossary.term') and optional 'fields'/'extractFields' query params, then calls omClient.get() to fetch the glossary term by name from the API endpoint /glossaryTerms/name/{fqn}.
    export async function getGlossaryTermByName(params: z.infer<typeof getGlossaryTermByNameSchema>) {
      const { fqn, ...query } = params;
      return omClient.get(`/glossaryTerms/name/${encodeURIComponent(fqn)}`, query);
    }
  • Zod schema for input validation. Accepts 'fqn' (required string), optional 'fields' string, and optional 'extractFields' string.
    export const getGlossaryTermByNameSchema = z.object({
      fqn: z.string().describe("Term FQN (e.g. 'glossary.term')"),
      fields: z.string().optional(),
      extractFields: ef,
    });
  • src/index.ts:257-257 (registration)
    Tool registration using the MCP server's tool() function, binding the schema and handler together under the name 'get-glossary-term-by-name'.
    tool("get-glossary-term-by-name", "Get glossary term by fully qualified name", getGlossaryTermByNameSchema.shape, wrapToolHandler(getGlossaryTermByName));
  • Import statement bringing getGlossaryTermByNameSchema and getGlossaryTermByName into index.ts from src/tools/glossary.ts.
    import {
      listGlossariesSchema, listGlossaries, getGlossarySchema, getGlossary,
      getGlossaryByNameSchema, getGlossaryByName, createGlossarySchema, createGlossary,
      updateGlossarySchema, updateGlossary, deleteGlossarySchema, deleteGlossary,
      listGlossaryTermsSchema, listGlossaryTerms, getGlossaryTermSchema, getGlossaryTerm,
      getGlossaryTermByNameSchema, getGlossaryTermByName, createGlossaryTermSchema, createGlossaryTerm,
      updateGlossaryTermSchema, updateGlossaryTerm, deleteGlossaryTermSchema, deleteGlossaryTerm,
    } from "./tools/glossary.js";
Behavior2/5

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

No annotations are supplied, and the description is minimal ('Get glossary term by fully qualified name'). It does not disclose behavioral traits such as whether the tool is read-only, what permissions are needed, rate limits, or any side effects. The description carries the full burden for transparency and fails to provide meaningful 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence with no wasted words. It conveys the core purpose efficiently. It is appropriately sized for a simple retrieval tool, demonstrating conciseness without sacrificing clarity.

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 tool's simplicity (one required parameter, no output schema), the description is minimal but lacks completeness. It does not hint at the return value, differentiate from siblings, or provide any behavioral context. For a basic get-by-name tool, this is adequate but not thorough, earning a middle score.

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 description coverage is 67% (2 of 3 parameters have descriptions). The description adds no new semantic value beyond the schema; it simply aligns with the 'fqn' parameter. The 'fields' parameter lacks description in both schema and description. Overall, the description does not compensate for missing schema details, landing at the baseline for moderate coverage.

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 clearly states the verb 'Get' and the resource 'glossary term' with the qualifier 'by fully qualified name'. It is specific but does not explicitly differentiate from the sibling tool 'get-glossary-term', which likely uses an ID. The name itself provides some distinction, so clarity is high but not maximized.

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 versus alternatives like 'get-glossary-term' or other get-* tools. There is no mention of prerequisites, such as having the FQN ready, or scenarios where this tool is preferred. The description offers no context for usage decisions.

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