Skip to main content
Glama
gabrielmahia

church-mcp

by gabrielmahia
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

Server Quality Checklist

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

  • Latest release: v0.1.4

  • Disambiguation5/5

    With only one tool, there is no risk of confusion or overlap. The single tool is clearly distinct by default.

    Naming Consistency5/5

    A single tool makes naming consistency trivial. The name 'community_welfare_guide' follows a clear noun_noun pattern, but there is no inconsistency to evaluate.

    Tool Count2/5

    A server named 'church-mcp' with only one tool is far too few for the implied scope of church-related operations. Even as a DEMO, it feels thin and incomplete.

    Completeness1/5

    The tool is a single guide about welfare programs. For a church server, obvious gaps exist (e.g., events, donations, memberships, prayer requests). The 'DEMO' label reinforces the lack of completeness.

  • Average 2.8/5 across 1 of 1 tools scored.

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

    • No community issues in the last 6 months
    • 35 commits in the last 12 weeks
    • Last stable release on
    • No critical vulnerability alerts
    • No high-severity vulnerability alerts
    • No code scanning findings
    • CI is passing

  • 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.

Tool Scores

  • Behavior2/5

    Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

    The annotations already declare readOnlyHint=true, indicating a safe read operation. The description adds no behavioral details beyond the title and does not disclose any side effects, permissions, or return behavior. The 'DEMO' tag may hint at non-production data, but it is not a sufficient behavioral disclosure. With annotations present, the description contributes minimal extra value.

    Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

    Conciseness3/5

    Is the description appropriately sized, front-loaded, and free of redundancy?

    The description is extremely concise, consisting of a single sentence. However, the inclusion of 'DEMO' is extraneous and does not serve the agent's understanding. While front-loaded with the core purpose, the brevity sacrifices completeness and leaves out useful details. Not every part earns its place.

    Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

    Completeness2/5

    Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

    Given the tool's simplicity (one optional parameter, no siblings, output schema exists), the description is still incomplete. It does not explain how the results are structured, what 'accessing programs' means operationally, or the range of possible values for 'need.' The output schema may fill some gaps, but the description itself lacks sufficient context.

    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?

    The input schema has 100% description coverage for the single parameter 'need,' which is well-documented in the schema. The tool description does not mention the parameter or provide additional context beyond the schema. Per the guidelines, the baseline is 3 when schema coverage is high, and no extra meaning is added.

    Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

    Purpose4/5

    Does the description clearly state what the tool does and how it differs from similar tools?

    The description clearly states the tool's purpose: 'How to access Kenya religious community welfare programs.' It specifies the verb 'access' and the resource 'Kenya religious community welfare programs,' making the action and target unambiguous. However, the addition of 'DEMO' introduces slight ambiguity about the tool's production readiness.

    Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

    Usage Guidelines2/5

    Does the description explain when to use this tool, when not to, or what alternatives exist?

    The description provides no explicit guidance on when to use this tool versus alternatives. There are no sibling tools, so differentiation is not required, but the description does not explain typical use cases or prerequisites for using the guide. The lack of usage context limits the agent's ability to decide when to invoke this tool.

    Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

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

church-mcp MCP server

Copy to your README.md:

Score Badge

church-mcp 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/gabrielmahia/church-mcp'

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