Skip to main content
Glama
us-all

openmetadata-mcp-server

by us-all

search-metadata

Search OpenMetadata entities such as tables, topics, and dashboards by keyword. Supports filtering by entity index, pagination, sorting, and soft-deleted entities.

Instructions

Search OpenMetadata entities (tables, topics, dashboards, pipelines, glossary terms, etc.) by keyword

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qYesSearch query
indexNoRestrict search to a specific entity index
fromNoPagination offset
sizeNoNumber of results to return (max 100)
deletedNoInclude soft-deleted entities
trackTotalHitsNoTrack exact total hit count
queryFilterNoElasticSearch query filter (JSON)
sortFieldNoSort field (e.g. 'updatedAt')
sortOrderNoSort order
includeSourceFieldsNoSource fields to include
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?

With no annotations, the description carries full burden but only states a basic operation. It lacks disclosure of traits like pagination limits, result format, or handling of deleted entities.

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?

A single concise sentence that front-loads the purpose and includes useful examples without any waste.

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 the tool's complexity (11 parameters) and lack of output schema, the description is too minimal. It omits important context like pagination limits, query syntax, and results structure.

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 100%, so baseline is 3. The description adds no extra meaning beyond listing entity types; it does not clarify parameter interactions or query syntax.

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 'Search' and the resource 'OpenMetadata entities' with explicit examples (tables, topics, dashboards, etc.), distinguishing it from sibling tools like list-tables or get-table.

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 semantic-search or search-tools, nor any conditions for use or exclusion criteria.

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