Skip to main content
Glama
us-all

openmetadata-mcp-server

by us-all

get-glossary

Retrieve glossary details by providing its UUID. Access terms, definitions, and related metadata.

Instructions

Get glossary details by UUID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesGlossary UUID
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 handler function for the get-glossary tool. It extracts the 'id' from params, constructs a GET request to /glossaries/{id}, and passes remaining fields as query parameters.
    export async function getGlossary(params: z.infer<typeof getGlossarySchema>) {
      const { id, ...query } = params;
      return omClient.get(`/glossaries/${id}`, query);
    }
  • The Zod schema for the get-glossary tool, defining input parameters: id (string, required), fields (string, optional), and extractFields (string, optional).
    export const getGlossarySchema = z.object({
      id: z.string().describe("Glossary UUID"),
      fields: z.string().optional(),
      extractFields: ef,
    });
  • src/index.ts:247-247 (registration)
    Registration of the get-glossary tool with its name, description, schema shape, and wrapped handler function.
    tool("get-glossary", "Get glossary details by UUID", getGlossarySchema.shape, wrapToolHandler(getGlossary));
  • The omClient is used by the handler to make the HTTP GET request to the API.
    import { assertWriteAllowed } from "./utils.js";
Behavior1/5

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

No annotations are provided, and the description does not disclose any behavioral traits (e.g., idempotency, permissions, side effects). It simply restates the tool's purpose without depth.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

One sentence with no wasted words, but it is too minimal for a tool with 3 parameters; could be more informative while remaining concise.

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 does not explain what 'details' are returned or any constraints. It is incomplete for an agent to use effectively.

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%, with descriptions for 'id' and 'extractFields' but not 'fields'. The description adds no extra meaning beyond the schema, so baseline score of 3 is appropriate.

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), resource (glossary details), and method (by UUID), distinguishing it from siblings like get-glossary-by-name and list-glossaries.

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-glossary-by-name or list-glossaries. The description does not mention scenarios 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