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. The ranking is over the closest-matching passages this search found, so fewer churches may come back than you ask for.
`denomination`	No	Optional case-insensitive denomination filter.
`radius_miles`	No	Search radius in miles.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 27, 2026

changedInput schema / properties / limit / description

Previous value: -"Maximum number of churches to return."New value: +"Maximum number of churches to return. The ranking is over the closest-matching passages this search found, so fewer churches may come back than you ask for."

Changed18 schema fields changedJul 20, 2026
- changedInput schema / properties / denomination / description
```
Previous value: -"Optional denomination filter, e.g. 'Baptist'."New value: +"Optional case-insensitive denomination filter."
```
- addedInput schema / properties / denomination / examples
```
Added value: +[
+  "Baptist",
+  "Catholic",
+  "Non-denominational"
+]
```
- changedInput schema / properties / lat / description
```
Previous value: -"Latitude of the search center."New value: +"Latitude of the search center, in decimal degrees."
```
- addedInput schema / properties / lat / examples
```
Added value: +[
+  34.0522
+]
```
- addedInput schema / properties / lat / maximum
```
Added value: +90
```
- addedInput schema / properties / lat / minimum
```
Added value: +-90
```
- addedInput schema / properties / limit / default
```
Added value: +10
```
- changedInput schema / properties / limit / description
```
Previous value: -"Max results (default 10, max 25)."New value: +"Maximum number of churches to return."
```
- addedInput schema / properties / limit / maximum
```
Added value: +25
```
- addedInput schema / properties / limit / minimum
```
Added value: +1
```
- changedInput schema / properties / lng / description
```
Previous value: -"Longitude of the search center."New value: +"Longitude of the search center, in decimal degrees."
```
- addedInput schema / properties / lng / examples
```
Added value: +[
+  -118.2437
+]
```
- addedInput schema / properties / lng / maximum
```
Added value: +180
```
- addedInput schema / properties / lng / minimum
```
Added value: +-180
```
- addedInput schema / properties / radius_miles / default
```
Added value: +25
```
- changedInput schema / properties / radius_miles / description
```
Previous value: -"Search radius in miles (default 25, max 100)."New value: +"Search radius in miles."
```
- addedInput schema / properties / radius_miles / maximum
```
Added value: +100
```
- addedInput schema / properties / radius_miles / minimum
```
Added value: +1
```
First observedJun 14, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already mark this as read-only and non-destructive. The description adds valuable context: it specifies that only public directory data is used, excludes personal contact info, and details the return fields (name, denomination, location, website, distance, SoapBox membership with community id). This goes 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?

Two sentences with zero filler. The first sentence states the purpose, and the second lists return fields and data scope. The description is front-loaded and every word earns its place.

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?

For a tool with 5 parameters and no output schema, the description compensates by listing return fields and clarifying data scope (public, no personal info). It doesn't explain the limit ranking or radius default, but those are in the schema. It is complete enough for an agent to invoke 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 baseline is 3. The description mentions 'optional radius, denomination filter' but does not add meaning beyond what the schema already documents for each parameter. It adds no extra semantics like units or formatting that aren't already in the schema.

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 states a specific verb (Find) and resource (churches near a location from SoapBox's public directory), which clearly differentiates it from sibling tools like find_churches_preaching_on or search_sermons. It immediately conveys the tool's unique function.

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 by stating the task ('Find churches near a location') but does not explicitly mention when to prefer it over siblings or provide exclusions. It lacks direct guidance on alternatives, so the agent must infer from the purpose.

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

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?