Skip to main content
Glama
us-all

openmetadata-mcp-server

by us-all

create-glossary

Create a new glossary to organize and define business terms with a name and description.

Instructions

Create a new glossary for business terms

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesGlossary name
displayNameNo
descriptionYesGlossary description
mutuallyExclusiveNoTerms mutually exclusive
ownersNo
reviewersNo
tagsNo

Implementation Reference

  • The handler function that executes the create-glossary tool logic. It calls assertWriteAllowed() then POSTs to /glossaries endpoint.
    export async function createGlossary(params: z.infer<typeof createGlossarySchema>) {
      assertWriteAllowed();
      return omClient.post("/glossaries", params);
    }
  • Input schema for create-glossary: defines name (required), displayName (optional), description (required), mutuallyExclusive (optional, default false), owners/reviewers/tags (optional arrays of records).
    export const createGlossarySchema = z.object({
      name: z.string().describe("Glossary name"),
      displayName: z.string().optional(),
      description: z.string().describe("Glossary description"),
      mutuallyExclusive: z.boolean().optional().default(false).describe("Terms mutually exclusive"),
      owners: z.array(z.record(z.string(), z.any())).optional(),
      reviewers: z.array(z.record(z.string(), z.any())).optional(),
      tags: z.array(z.record(z.string(), z.any())).optional(),
    });
  • src/index.ts:249-249 (registration)
    Registers the create-glossary tool with the MCP server, binding createGlossarySchema.shape and wrapToolHandler(createGlossary).
    tool("create-glossary", "Create a new glossary for business terms", createGlossarySchema.shape, wrapToolHandler(createGlossary));
  • Import of createGlossarySchema and createGlossary from the glossary module.
    listGlossariesSchema, listGlossaries, getGlossarySchema, getGlossary,
    getGlossaryByNameSchema, getGlossaryByName, createGlossarySchema, createGlossary,
    updateGlossarySchema, updateGlossary, deleteGlossarySchema, deleteGlossary,
Behavior2/5

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

No annotations provided; description only says 'Create' implying mutation. No disclosure of side effects, permissions, or constraints beyond that.

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?

Single sentence, concise but lacks structure. Could be expanded with purpose or constraints without becoming verbose.

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?

No output schema; complex nested parameters not explained. Description insufficient for agent to understand return value or full scope of operation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema has 7 parameters with 43% description coverage. Tool description adds no parameter-level meaning. Owners, reviewers, tags remain opaque.

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?

Description clearly states 'Create a new glossary for business terms', specifying the action and resource. It distinguishes from sibling like create-glossary-term but lacks deeper specificity.

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 update-glossary or other create tools. No mention of prerequisites or context.

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