MCP server for OpenMetadata that exposes tools to interact with OpenMetadata metadata catalog
This server has a single tool 'dummy_tool' that is explicitly marked as 'Ignore' in its description. The tool is non-functional, it returns an empty string and has no meaningful input schema (empty object {}). The tool definition exists but is a placeholder stub with no real business logic, making it unsuitable for production use. The OpenMetadata integration is configured in AppConfig.java (OpenMetadata client, JWT authentication setup) but no actual tools expose this functionality. The tool service extends an abstract class but provides only a dummy implementation.
Ignore
Tool marked as 'Ignore', non-functional placeholder stub. Description is 6 characters, far below the minimum 20-character baseline for actionable descriptions.
No input schema present. Tool accepts empty object {} with no parameters, description, or constraints. Violates requirement that every parameter must have a description explaining what it controls.
No output schema documented. Tool returns String but LLM has no guidance on what the string contains, when it is populated, or how to use it downstream.
OpenMetadata integration configured but not exposed. AppConfig.java sets up OpenMetadata client with JWT auth, but no tools call it. All functional capability is dead code.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-22 | F | 22 | 2026-07-28+ | v2 |
| 2026-03-09 | F | 8 | - | v1 |
No error handling. Tool returns empty string with no error messages, validation, recovery guidance, or user-friendly output.
Tool naming lacks action verb. 'dummy_tool' does not convey what the tool does (get, create, search, etc.).