Skip to main content
Glama
us-all

openmetadata-mcp-server

by us-all

get-glossary-by-name

Retrieve a glossary's full details, including terms and metadata, by providing its unique qualified name.

Instructions

Get glossary details by name

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fqnYesGlossary name
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 get-glossary-by-name tool logic. It takes params with 'fqn' (fully qualified name), makes a GET request to /glossaries/name/{fqn} via omClient.
    export async function getGlossaryByName(params: z.infer<typeof getGlossaryByNameSchema>) {
      const { fqn, ...query } = params;
      return omClient.get(`/glossaries/name/${encodeURIComponent(fqn)}`, query);
    }
  • Zod schema for getGlossaryByName input validation. Defines 'fqn' (string), optional 'fields', and optional 'extractFields'.
    export const getGlossaryByNameSchema = z.object({
      fqn: z.string().describe("Glossary name"),
      fields: z.string().optional(),
      extractFields: ef,
    });
  • src/index.ts:248-248 (registration)
    Registration of the 'get-glossary-by-name' tool using the MCP tool() function, with description and wrapped handler.
    tool("get-glossary-by-name", "Get glossary details by name", getGlossaryByNameSchema.shape, wrapToolHandler(getGlossaryByName));
  • Import of getGlossaryByNameSchema and getGlossaryByName from src/tools/glossary.ts into the main index file.
    import {
      listGlossariesSchema, listGlossaries, getGlossarySchema, getGlossary,
      getGlossaryByNameSchema, getGlossaryByName, createGlossarySchema, createGlossary,
      updateGlossarySchema, updateGlossary, deleteGlossarySchema, deleteGlossary,
      listGlossaryTermsSchema, listGlossaryTerms, getGlossaryTermSchema, getGlossaryTerm,
Behavior2/5

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

No annotations provided; the description does not disclose behaviors like read-only nature, error handling (e.g., what happens if glossary not found), or performance implications. The bare phrase 'get details' implies a safe read, but the agent is left guessing about side effects or requirements.

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 sentence with no extraneous words. It is appropriately concise but could include slightly more detail without sacrificing brevity, such as the expected output format.

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 no output schema and no annotations, the description is insufficient. It does not cover response structure, error states, or any constraints (e.g., uniqueness of names). A tool with 3 parameters should provide more behavioral context.

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% (fqn and extractFields described, fields not). The description does not add any meaning beyond the schema; it merely repeats the schema's 'fqn' as 'Glossary name'. No extra context on parameter usage or relationships.

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 glossary details by name' clearly states the action (get) and resource (glossary details) and distinguishes from siblings like get-glossary (likely by ID) and get-glossary-term-by-name. It is clear but lacks specificity on what 'details' include.

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 such as get-glossary or list-glossaries. No context on prerequisites or exclusions. The description implies retrieval by name but does not clarify if it is the preferred method over ID-based lookup.

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