holydb-mcp
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.
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.
Tool Definition Quality
Average 5/5 across 1 of 1 tools scored.
With only one tool, there is no possibility of confusion between tools. The single tool has a clear, distinct purpose.
The tool name 'find_mass_times' follows a clear verb_noun pattern, and with only one tool, there are no inconsistencies to evaluate.
A single tool for a very specific domain (finding mass and confession times in NYC) is borderline acceptable. It feels thin but not unreasonable for a focused utility.
The tool only covers one operation (finding times), lacking any CRUD or lifecycle support for churches or events. Significant functionality like getting church details or adding events is missing.
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.
| 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
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations declare readOnlyHint=true, which the description aligns with ('Find'). The description adds behavioral details beyond annotations: it describes the return as 'every matching Mass and Confession at each church', explains input constraints (no coordinates, 24-hour time), and mentions radius bounding. This helps an agent understand side effects and response structure.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single clear paragraph of three sentences. It front-loads the purpose and then adds constraints. While it could be slightly more structured (e.g., bullet points for parameters), it is sufficiently concise and readable.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool has 5 parameters, no output schema, and moderate complexity, the description adequately covers inputs (with examples) and output (returns matching Masses/Confessions). It explains the time window and radius. It could mention potential limitations (e.g., API performance), but for the scope, it is fairly complete.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, but the description adds value by explaining the 'location' parameter (not coordinates, with examples), reiterating the time format, and noting the default radius. This contextual information helps an agent use parameters correctly beyond the schema's descriptions.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the verb 'Find', the resource 'every Catholic Mass and Confession', and the scope: 'within a day + time window at churches near a place in New York City.' It precisely defines the tool's function and leaves no ambiguity about what it does.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides detailed usage context: it specifies input types (place name, not coordinates), required parameters (day, from/to time), and optional radius. It explains the time format and gives examples. However, it does not explicitly mention when not to use or list alternatives, but with no siblings, this is acceptable.
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!