A
license-
qualityF
maintenanceRead-only MCP server for SQL databases (SQL Server, Postgres, SQLite) with multi-server support and three-layer safety using AST validation and linting.
MIT
holydb-mcp
by com.holydb
Server Details
Read-only MCP server for HolyDB: find Catholic parish Mass times by location and time.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
MCP client
Glama
MCP server
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
100% free. Your data is private.
Tool Definition Quality
A4.2/5.0
Tool DescriptionsA
Average 4.3/5 across 1 of 1 tools scored.
Server CoherenceA
Disambiguation5/5
Only one tool exists, so there is no possibility of confusion with other tools. The tool's purpose is clearly defined and unambiguous.
Naming Consistency5/5
The single tool name 'find_mass_times' follows a clear verb_noun pattern, which is consistent and readable. No other tools to compare against, but the naming is appropriate.
Tool Count4/5
For a highly specialized domain (Catholic Mass/Confession times in NYC), a single tool can be acceptable. However, the server name 'holydb' suggests a broader scope, so one tool feels slightly under-scoped.
Completeness2/5
The server is named 'holydb' but only offers one tool for Mass/Confession times in NYC. Missing features like searching other religious events, other locations, or different date ranges make the surface severely incomplete for the implied domain.
Available Tools
1 toolfind_mass_timesFind Mass timesARead-onlyInspect
Find every Catholic Mass and Confession within a day + time window at churches near a place in New York City. Takes a place name, neighborhood, or address (e.g. 'Park Slope', 'Times Square', '86th St and Lexington') — not coordinates. Requires a day of the week and a from/to time window (24-hour HH:MM); returns every matching Mass and Confession at each church in that window, bounded by an adjustable radius.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| day | Yes | Day of the week to look for. | |
| toTime | Yes | End of the time window, 24-hour HH:MM (e.g. '12:00'). | |
| fromTime | Yes | Start of the time window, 24-hour HH:MM (e.g. '09:00'). | |
| location | Yes | A place, neighborhood, landmark, or address in New York City. | |
| radiusKm | No | Search radius in kilometers. Defaults to 2km. |
Tool Definition Quality
A4.3/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations indicate readOnlyHint=true, signaling a safe read operation. The description adds behavioral context: it searches within an adjustable radius and returns every matching Mass and Confession at each church. No contradictions, and the description enriches the annotation with search scope and result detail, though it omits sort order or pagination.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two concise sentences. The first sentence states the core purpose, and the second adds essential usage details (location format, required day and time window, radius). No redundant or fluff content.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness5/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With 5 parameters, no output schema, and no siblings, the description covers all necessary context: tool purpose, valid inputs (location, day, time window), and optional radius. It is self-contained for an agent to use correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters3/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, so the schema already documents all parameters. The description adds minimal value beyond the schema: it clarifies that location should be a place name, not coordinates, and that radiusKm defaults to 2km. This slight enhancement does not significantly compensate beyond baseline 3.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool finds Catholic Mass and Confession times within a day and time window at churches near a place in NYC. It specifies the resource (Mass and Confession), location scope (NYC), and time constraints. No siblings exist, so differentiation is not needed.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines4/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides clear usage context: it requires a place name (not coordinates), a day of the week, and a time window. It gives examples of valid locations. However, it does not explicitly state when not to use the tool or mention alternatives, which is acceptable given no siblings.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!
Related MCP Servers
- Flicense-qualityAmaintenanceAn MCP server for Christian scholarship and research, providing read-only access to a SQLite corpus of 66-book BSB and 83-book WEB Bibles, original-language Greek/Hebrew word studies with Strong's and morphology, cross-references, patristic citations (Irenaeus, Justin Martyr, Apostolic Fathers), verse alignments, semantic and hybrid search over ~55,800 embeddings, and multi-work passage retrieval, interlinear lookup, and research-brief synthesis prompts.2
- Alicense-qualityAmaintenanceUniversal MCP server for readonly-first access to Oracle, SQL Server, PostgreSQL, MySQL/MariaDB, SQLite, MongoDB, and Qdrant vector search.7691MIT
- AlicenseAqualityAmaintenanceFree, no-key MCP server for reading scripture from 35+ public-domain translations in 8 languages. Lets users fetch verses, chapters, and passages via natural language from any MCP client.7MIT