SoapBox Faith

find_churches

Read-only

Find churches near a location from SoapBox's public church directory. Given latitude/longitude (and optional radius, denomination filter), returns nearby churches with name, denomination, city/state/country, website, distance in miles, and whether the church is on SoapBox (with its community id for deep-linking). Public directory data only — no personal contact info.

Input Schema

TableJSON Schema

Name	Required	Description
`lat`	Yes	Latitude of the search center, in decimal degrees.
`lng`	Yes	Longitude of the search center, in decimal degrees.
`limit`	No	Maximum number of churches to return.
`denomination`	No	Optional case-insensitive denomination filter.
`radius_miles`	No	Search radius in miles.

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare read-only and non-destructive. The description adds context about the public directory scope, absence of personal contact info, and the specific return fields including distance and SoapBox status, going beyond the annotations.

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 sentences, front-loaded with the main action, and every phrase adds value. No filler or redundancy.

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

Completeness4/5

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

With no output schema, the description enumerates the return fields and the data scope, which is essential. It does not cover edge cases or error behavior but is sufficient for a straightforward lookup tool with strong annotations.

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% with descriptions for all five parameters including types, ranges, and defaults. The description only mentions 'optional radius, denomination filter', which duplicates the schema, adding no new meaning.

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 uses a specific verb 'Find' with a clear resource 'churches near a location' and details what is returned. It distinguishes itself from sibling tools like browse_catalog by focusing on church location search.

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

Usage Guidelines3/5

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

The description implies usage when needing nearby churches but does not explicitly state when not to use it or mention alternatives. The note about public data is a constraint, not a comparative guideline.

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

All SoapBox Faith tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.2/5.0

Disambiguation5/5

Every tool targets a distinct action and resource: ask_ora is for Q&A, get_verse for exact verse lookup, verify_scripture for quote checking, lookup_strongs for lexicon entries, and so on. Any potential overlap (e.g., ask_ora vs get_verse) is explicitly addressed in the descriptions.

Naming Consistency5/5

All tool names consistently use a verb_noun or verb_prep_noun pattern (e.g., get_verse, search_sermons, submit_prayer_request, pay_with_x402). No mixing of casing or verb styles is present.

Tool Count3/5

At 19 tools, the set feels heavy. While each tool has a distinct purpose, the breadth spans scripture, sermons, prayers, giving, churches, user context, and audio synthesis. Some functions could be consolidated (e.g., purchase_sermon and purchase_bundle into a single purchase action) or split into separate services.

Completeness4/5

Core workflows are well-covered: discovery, purchase, prayer submission/status, giving, church lookup, and Bible study. However, there are minor gaps such as no way to update or delete prayer requests, no list of previously purchased items, and no general user profile beyond faith context. These are workable but prevent full lifecycle management.

Resources

Need Help?