SolaGuard MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SOLAGUARD_LOG_LEVEL | No | Optional configuration for log level. | INFO |
| SOLAGUARD_RATE_LIMIT | No | Optional configuration for the rate limit (e.g. 20/minute). | 20/minute |
| SOLAGUARD_DATABASE_PATH | No | Optional configuration for the path to the SQLite database file. | /app/data/bible.db |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
No tools | |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
Each tool has a clearly distinct purpose with minimal overlap. get_verse retrieves specific verses, get_verse_context adds surrounding context, get_book_info provides metadata, get_cross_references finds related passages, get_strongs handles word studies, search_by_topic searches semantically, and search_scripture performs full-text search. The boundaries between tools are well-defined and unlikely to cause confusion.
All tools follow a consistent verb_noun naming pattern with 'get_' or 'search_' prefixes. The naming is uniform throughout (get_book_info, get_cross_references, get_strongs, get_verse, get_verse_context, search_by_topic, search_scripture), making it easy to predict tool functions and maintain readability.
With 7 tools, this server is well-scoped for biblical study and analysis. Each tool serves a distinct and necessary function in the domain, covering verse retrieval, context, metadata, cross-references, word studies, and search capabilities. The count is neither too sparse nor bloated.
The toolset provides comprehensive coverage for core biblical study workflows, including retrieval, search, and analysis. Minor gaps exist, such as no explicit tools for comparing translations or handling user annotations, but agents can work around these using the available tools without significant hindrance to the server's purpose.