jd-church-website-audit
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| JOURNEY_DIGITAL_AUDIT_BASE_URL | No | Set this to use another origin for the Journey Digital audit service. | https://journeydigital.ai |
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| audit_church_websiteA | Audits one church homepage for mobile fit, speed, SEO basics, and first-time-guest findability, and returns Journey Digital's report unchanged. Use it when the user gives one church website address. Do not use it to crawl a site, to promise a search ranking, or when no address was given. Sends that address to journeydigital.ai, which fetches the page, and the speed check to Google PageSpeed. No API key. Plugin audits store an anonymous count, so repeating the call records another count, and the church website itself is not modified. If the service is unreachable, rate-limited, or the report is malformed, the result is an error and includes no checks. Privacy: https://journeydigital.ai/privacy Terms: https://journeydigital.ai/terms |
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 1 tool
There is only one tool, and its purpose is explicitly narrow: audit one church homepage. There are no sibling tools with overlapping scope, so misselection is not a concern.
The single tool follows a clear verb_noun pattern: audit_church_website. With only one tool, there is no inconsistency across the set.
The server is deliberately scoped to a single audit operation, so one tool is reasonable rather than incomplete. It is slightly thin compared with multi-operation servers, but it matches the stated narrow purpose.
The tool covers the stated audit dimensions: mobile fit, speed, SEO basics, and first-time-guest findability. Minor gaps exist around batch or multi-page auditing, but the description explicitly excludes crawling, so the surface is coherent for its intended use.