Skip to main content
Glama

SoapBox Faith

by io.github.alansafahi
OverviewDiscussionsAdmin

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 buy with purchase_sermon. Optional church_id and text filter. No key required.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qNoOptional case-insensitive text filter matched against product titles.
limitNoMaximum number of products to return.
church_idNoOptional SoapBox community id to scope the catalog to a single church.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changed
    • 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"
+]
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds valuable context: 'No key required' (auth needs), 'currently consented sermons; reading-plan and devotional bundles coming' (scope/currency), and the exact return fields (id, title, church, price). This enriches beyond the annotations without contradiction.

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 concise sentences: what it does, what it returns, and a purchase pointer. Every sentence adds value, and the structure is front-loaded with the tool's purpose. No fluff or redundant detail beyond the schema.

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

Completeness5/5

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

For a simple list/browse tool, the description is complete: it states the products available, return fields, an optional filter, and the follow-up purchase action. With no output schema, the return fields are explicitly listed. OpenWorldHint is covered by annotations, and the 'No key required' note resolves auth concerns.

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 schema covers 100% of parameters with descriptions and examples. The description merely mentions 'Optional church_id and text filter', adding no new meaning beyond what the schema already provides. Given the high schema coverage, the baseline of 3 is appropriate.

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 ('Browse') with a clear resource ('purchasable faith-content products on SoapBox') and explicitly distinguishes from the purchase step ('Then buy with purchase_sermon'). It also clarifies current scope, making it distinct from sibling tools like search_sermons.

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

Usage Guidelines4/5

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

The description implies a workflow: use browse_catalog to discover products, then purchase with purchase_sermon. It notes the current content scope ('currently consented sermons'), hinting at when this tool is appropriate. However, it does not explicitly state when not to use it or mention alternatives like search_sermons.

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

All SoapBox Faith toolsInspect
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