Skip to main content
Glama
jissac

SolaGuard MCP Server

by jissac
OverviewSchemaRelated ServersScoreDiscussions
Python
Hybrid

Server Quality Checklist

58%
Profile completionA complete profile improves this server's visibility in search results.

  • Latest release: v0.1.0

  • Disambiguation5/5

    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.

    Naming Consistency5/5

    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.

    Tool Count5/5

    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.

    Completeness4/5

    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.

  • Average 3.6/5 across 7 of 7 tools scored.

    See the Tool Scores section below for per-tool breakdowns.

    • No community issues in the last 6 months
    • 0 commits in the last 12 weeks
    • No stable releases found
    • No critical vulnerability alerts
    • No high-severity vulnerability alerts
    • No code scanning findings
    • CI status not available

  • This repository is licensed under MIT License.

  • This repository includes a README.md file.

  • No tool usage detected in the last 30 days. Usage tracking helps demonstrate server value.

    Tip: use the "Try in Browser" feature on the server page to seed initial usage.

  • Add a glama.json file to provide metadata about your server.

  • If you are the author, simply .

    If the server belongs to an organization, first add glama.json to the root of your repository:

    {
  "$schema": "https://glama.ai/mcp/schemas/server.json",
  "maintainers": [
    "your-github-username"
  ]
}

    Then . Browse examples.

  • Add related servers to improve discoverability.

How to sync the server with GitHub?

Servers are automatically synced at least once per day, but you can also sync manually at any time to instantly update the server profile.

To manually sync the server, click the "Sync Server" button in the MCP server admin interface.

How is the quality score calculated?

The overall quality score combines two components: Tool Definition Quality (70%) and Server Coherence (30%).

Tool Definition Quality measures how well each tool describes itself to AI agents. Every tool is scored 1–5 across six dimensions: Purpose Clarity (25%), Usage Guidelines (20%), Behavioral Transparency (20%), Parameter Semantics (15%), Conciseness & Structure (10%), and Contextual Completeness (10%). The server-level definition quality score is calculated as 60% mean TDQS + 40% minimum TDQS, so a single poorly described tool pulls the score down.

Server Coherence evaluates how well the tools work together as a set, scoring four dimensions equally: Disambiguation (can agents tell tools apart?), Naming Consistency, Tool Count Appropriateness, and Completeness (are there gaps in the tool surface?).

Tiers are derived from the overall score: A (≥3.5), B (≥3.0), C (≥2.0), D (≥1.0), F (<1.0). B and above is considered passing.

GitHub Badge

Glama performs regular codebase and documentation scans to:

  • Confirm that the MCP server is working as expected.
  • Confirm that there are no obvious security issues.
  • Evaluate tool definition quality.

Our badge communicates server capabilities, safety, and installation instructions.

Card Badge

solaguard-mcp-server MCP server

Copy to your README.md:

Score Badge

solaguard-mcp-server MCP server

Copy to your README.md:

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/jissac/solaguard-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server