Semantic Mapping #24
Description
Currently, my MCP server can only query the Oracle database when the exact technical names of tables or columns are provided and my production DB is full of coded name.
This is not user-friendly, since end users typically expect to interact with semantic / human-readable names.
Without semantic mapping, the AI agent cannot interpret queries in natural language and fails unless the precise schema names are used.
Is it possible to introduce a semantic mapping layer that connects human-friendly terms with their underlying Oracle schema objects?
I know that I can operate at database level but I want to keep it as it is and use MCP in readonly.
some benefits:
Improves usability by allowing natural language queries.
Supports multi-language synonyms.
Reduces user errors due to case sensitivity or technical naming conventions.
Makes the system more intuitive and aligned with business terminology.
Possible workflow:
Add the initial semantic mapping configuration (JSON/DB table).
Extend the AI Agent to read and apply mappings at query time.
Document how developers and admins can add/update mappings over time.