SoapBox Faith

browse_catalog

Read-only

Browse purchasable faith-content products on SoapBox (currently consented sermons; reading-plan and devotional bundles coming). Returns products with id, title, church, and price. Then pay for one with pay_with_x402 (USDC on Base). Optional church_id and text filter. No key required.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "browse_catalog"
  }
}

Input Schema

Name	Required	Description
`q`	No	Optional case-insensitive text filter matched against product titles.
`limit`	No	Maximum number of products to return.
`church_id`	No	Optional SoapBox community id to scope the catalog to a single church.

Schema Changelog

Changes observed during successful MCP inspections.

Changed9 schema fields changedJul 20, 2026

changedInput schema / properties / church_id / description

Previous value: -"Optional SoapBox community id to scope to one church."New value: +"Optional SoapBox community id to scope the catalog to a single church."

addedInput schema / properties / church_id / examples

Added value: +[
+  "b3095717-5cc0-4213-8964-a01a5ee6b250"
+]

addedInput schema / properties / church_id / format
```
Added value: +"uuid"
```
addedInput schema / properties / limit / default
```
Added value: +25
```

changedInput schema / properties / limit / description

Previous value: -"Max products (1-100, default 25)."New value: +"Maximum number of products to return."

addedInput schema / properties / limit / maximum
```
Added value: +100
```
addedInput schema / properties / limit / minimum
```
Added value: +1
```

changedInput schema / properties / q / description

Previous value: -"Optional text filter on product title."New value: +"Optional case-insensitive text filter matched against product titles."

addedInput schema / properties / q / examples

Added value: +[
+  "romans",
+  "advent"
+]

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 readOnlyHint=true and destructiveHint=false, so the safety profile is clear. The description adds value beyond annotations by stating the return shape ('id, title, church, and price'), the pre-payment role ('Then pay for one with pay_with_x402'), 'No key required', and the open-ended future catalog expansion.

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?

Three short sentences front-load purpose, then return fields, then the payment next step, filters, and auth requirement. Every sentence earns its place and there is no repetition of the title or obvious filler.

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 correctly states the key return fields, which is essential. It also covers auth, filter options, and the payment hand-off. It does not discuss empty results or pagination behavior, but limit is already in the schema, so this is sufficient for a low-complexity read tool.

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 description coverage is 100%, so the baseline is 3. The description only gestures at 'Optional church_id and text filter,' restating q and church_id without adding format, sort, or interaction semantics beyond the schema. It provides no meaningful extra parameter 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 verb 'Browse' plus resource 'purchasable faith-content products on SoapBox' states exactly what the tool does. Mentioning the returned fields and the current scope ('currently consented sermons') separates it from search/get-sermon siblings. The purpose is unambiguous even without explicit sibling contrast.

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 the use case—browse the catalog, then pay with pay_with_x402—but gives no explicit when-to-use or when-not-to-use guidance versus search_sermons or get_sermon. It provides useful context ('currently consented sermons; bundles coming') but no exclusion criteria. Adequate but relies on inference.

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?