Knowledge Base Database
The Knowledge Base Database defines how information sources are structured and managed for MOOD MNKY agents. It provides a standardized approach for organizing, retrieving, and updating the knowledge that powers agent interactions.Purpose and Role
The Knowledge Base Database defines “what” agents know, ensuring they have access to accurate, relevant, and up-to-date information.
- Information sources and their characteristics
- Categorization and tagging of knowledge
- Retrieval mechanisms and access patterns
- Update and maintenance processes
- Knowledge relationships and dependencies
- Validation and verification procedures
Schema and Structure
- Database Schema
- Example Entry
Field Descriptions
knowledge_id
knowledge_id
A unique identifier for the knowledge item.
title
title
The name of the knowledge item in human-readable form.
description
description
A detailed description of what the knowledge contains.
content_type
content_type
The type of content (document, FAQ, product data, etc.).
source
source
The location or origin of the knowledge.
tags
tags
created_at
created_at
When the knowledge item was first added.
updated_at
updated_at
When the knowledge item was last modified.
status
status
Current status (active, deprecated, draft, etc.).
access_level
access_level
Visibility and access restrictions.
related_knowledge
related_knowledge
vector_embedding
vector_embedding
Whether the content has vector embeddings for semantic search.
embedding_model
embedding_model
The model used to generate vector embeddings.
retrieval_priority
retrieval_priority
A value from 0-1 indicating retrieval priority when multiple items match.
Knowledge Types
The MOOD MNKY knowledge base supports various types of information:Product Information
- Product catalogs and specifications
- Fragrance notes and compositions
- Usage instructions and care guidelines
- Product compatibility and combinations
- Seasonal offerings and limited editions
Brand Knowledge
- Brand values and mission
- Brand voice and tone guidelines
- Brand history and milestones
- Visual identity standards
- Messaging frameworks
Support Content
- Frequently asked questions
- Troubleshooting guides
- Return and exchange policies
- Shipping information
- Care and maintenance instructions
Educational Resources
- Fragrance education materials
- Self-care guides and tutorials
- Wellness principles and practices
- Ingredient information and benefits
- Historical and cultural context
Retrieval Mechanisms
Vector Search Implementation
MCP Server for Knowledge Retrieval
Integration with OpenAI Agents SDK
The Knowledge Base Database integrates with the OpenAI Agents SDK in several ways:As Agent Instructions
As Tool Data Source
As Dynamic Context
Retrieval Strategies
Semantic Search
Vector embeddings enable semantic similarity searches beyond keyword matching, finding contextually relevant information even when terminology differs.
Hybrid Search
Combines vector search with traditional keyword matching for optimal results, balancing semantic understanding with exact match precision.
Filtered Retrieval
Applies metadata filters by content type, tags, or status to narrow searches and improve relevance for specific query domains.
Chunked Retrieval
Breaks large documents into smaller chunks with their own embeddings, enabling more precise retrieval of specific information.
Best Practices for Knowledge Management
Content Organization
- Atomic Knowledge Units: Design knowledge entries to be self-contained and focused
- Clear Hierarchy: Establish relationships between knowledge items
- Consistent Tagging: Develop and maintain a consistent taxonomy
- Metadata Enrichment: Include comprehensive metadata for better retrieval
- Content Validation: Implement review processes for accuracy
Vector Database Management
- Optimal Chunk Size: Find the right balance for chunking documents (typically 256-1024 tokens)
- Regular Reindexing: Update embeddings when models improve
- Embedding Consistency: Use the same embedding model across the knowledge base
- Query-Document Alignment: Align embedding processes for queries and documents
- Dimension Optimization: Choose appropriate vector dimensions for your use case
Knowledge Lifecycle
- Freshness Monitoring: Track content age and relevance
- Update Triggers: Define events that necessitate knowledge updates
- Version Control: Maintain history of knowledge changes
- Deprecation Process: Properly handle outdated information
- Knowledge Gaps Analysis: Regularly identify missing information