Skip to main content
Glama
us-all

openmetadata-mcp-server

list-glossary-terms

Retrieve glossary terms with pagination and filter by glossary name, parent term, or deleted status.

Instructions

List glossary terms with pagination and glossary filtering

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fieldsNoFields (e.g. 'owners,tags,relatedTerms')
limitNo
beforeNo
afterNo
glossaryNoFilter by glossary name
parentNoFilter by parent glossary term FQN
includeNonon-deleted
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.
Behavior2/5

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

No annotations provided. Description does not mention pagination limits, default behavior for include parameter, or potential side effects. Lacks details on ordering or performance.

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?

Single, concise sentence with no redundancy. Front-loaded with action and resource.

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?

With 8 parameters and no output schema, description is too minimal. Lacks details on pagination flow, result structure, or filtered behaviors.

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 50%; description adds only 'pagination and glossary filtering' which hints at limit/before/after and glossary parameters. Does not elaborate on fields, parent, or include.

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 'List glossary terms with pagination and glossary filtering', specifying verb and resource. It differentiates from siblings like list-glossaries and get-glossary-term.

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 explicit guidance on when to use this tool vs alternatives like get-glossary-term or list-glossaries. Does not mention exclusions or specific contexts.

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