Model Context Protocol (MCP) server for OpenMetadata
Server has 10 tools with explicit schemas and descriptions, but quality is inconsistent. Tool names follow verb_noun convention (list_, get_, create_, update_, delete_) which is good. However, descriptions are minimal (10-50 chars), parameter descriptions lack detail about constraints and formats, and output schemas are completely undocumented. The 'table_data' parameter in create_table and update_table is typed as generic 'object' with no schema specification, forcing LLMs to guess valid structure. No error handling guidance, no pagination documentation despite list tools, and no indication of what fields are returned. Composition is reasonable (separate tools for CRUD), but parameter naming could be more explicit (e.g., 'table_id' is good, but 'fields' lacks format guidance).
Create a new table
Delete a table
Get details of a specific glossary by fully qualified name
Get details of a specific glossary term by fully qualified name.
Get details of a specific table by ID
Get details of a specific table by fully qualified name
List glossaries from OpenMetadata
create_table and update_table accept 'table_data' as untyped object with no schema. LLMs cannot determine required fields, valid structure, or nested properties. Forces trial-and-error API calls.
No output schemas documented for any tool. LLMs cannot plan downstream calls or extract required fields (e.g., table_id from create_table response). Breaks tool chaining.
Descriptions are 10-40 characters, below the 50-200 char baseline for LLM-optimized descriptions. 'List tables from OpenMetadata' lacks context on when to use it, what it returns, or pagination behavior.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 50 | 2026-07-28+ | v2 |
List glossary terms from OpenMetadata, optionally filtered by glossary FQN.
List tables from OpenMetadata
Update an existing table
'fields' parameter in get_table, get_table_by_name, get_glossary_by_name lacks description of valid field names, format, or constraints. Example values in schema are not actionable guidance.
No error handling guidance. Destructive tool (delete_table) has no confirmation step or dry-run option. No recovery hints for common failures (table not found, permission denied).