Skip to main content
Glama

SoapBox Faith

by io.github.alansafahi
OverviewDiscussionsAdmin

get_faith_context

Read-only

Read a user's portable 'faith context' to personalize your responses — their denomination, preferred language, faith journey, and ministry interests — shared WITH THE USER'S EXPLICIT CONSENT. Requires the user's consent_token with the 'context:read' scope (bound to this agent). Use it to tailor tone, tradition, and language. It returns only the user's declared profile (never their private prayers or journal).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
consent_tokenYesOpaque SoapBox consent token with the 'context:read' scope. The user generates it in the SoapBox app (Settings › AI Agents). The first agent key to use a token is bound to it; a token no agent uses within 24 hours of being created stops working. Returns only the user's declared profile (denomination, preferred language, faith journey, ministry interests) — never their private prayers or journal. An invalid, expired, or wrong-scope token returns an authorization error.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / consent_token / description
      Previous value: -"Opaque SoapBox consent token with the 'context:read' scope, bound to your agent key. The user generates it in the SoapBox app. Returns only the user's declared profile (denomination, preferred language, faith journey, ministry interests) — never their private prayers or journal. An invalid, expired, or wrong-scope token returns an authorization error."New value: +"Opaque SoapBox consent token with the 'context:read' scope. The user generates it in the SoapBox app (Settings › AI Agents). The first agent key to use a token is bound to it; a token no agent uses within 24 hours of being created stops working. Returns only the user's declared profile (denomination, preferred language, faith journey, ministry interests) — never their private prayers or journal. An invalid, expired, or wrong-scope token returns an authorization error."
    • changedInput schema / properties / consent_token / examples
      Previous value: -[
-  "sbxctx_9f3a2b7c4d5e6f7a…"
-]New value: +[
+  "sbxc_9f3a2b7c4d5e6f7a…"
+]
  2. Changed3 schema fields changed
    • changedInput schema / properties / consent_token / description
      Previous value: -"The user's SoapBox consent token (scope context:read, bound to this agent)."New value: +"Opaque SoapBox consent token with the 'context:read' scope, bound to your agent key. The user generates it in the SoapBox app. Returns only the user's declared profile (denomination, preferred language, faith journey, ministry interests) — never their private prayers or journal. An invalid, expired, or wrong-scope token returns an authorization error."
    • addedInput schema / properties / consent_token / examples
      Added value: +[
+  "sbxctx_9f3a2b7c4d5e6f7a…"
+]
    • addedInput schema / properties / consent_token / minLength
      Added value: +16
  3. First observed

TDQS

A4.8/5.0
Behavior5/5

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

The annotations declare readOnlyHint=true and destructiveHint=false, but the description goes beyond by detailing the consent requirement, the token binding to the agent, the 24-hour token lifecycle, and the explicit exclusion of private prayers/journal. It also warns about authorization errors. This is rich behavioral context that annotations alone do not provide.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured, with the main purpose front-loaded, followed by consent requirements and privacy scoping. While the parameter description is comprehensive, it is slightly lengthy but still focused. Every sentence serves a clear purpose, balancing conciseness and necessary detail.

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?

Given it has a single parameter with high schema coverage and no output schema, the description fully compensates by explaining the exact data returned and the authorization failure case. There is no ambiguity about what the tool does, what inputs it needs, and what the agent should expect.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema already describes the consent_token with examples and scope, but the description adds value by embedding the full token lifecycle and privacy guarantees. It reinforces what the token is and its constraints, complementing 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 clearly states the tool's purpose: to read a user's portable faith context for personalization, with explicit consent. It distinguishes this from siblings like get_verse or get_sermon by focusing on the user's profile data. The description also specifies what is included (denomination, language, journey, interests) and what is excluded (praises, journal).

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

Usage Guidelines5/5

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

It explicitly states when to use it: to tailor tone, tradition, and language. It also provides clear constraints: requires the user's consent_token with specific scope, and clarifies that it returns only declared profile, not private data. This gives the agent precise conditions for invocation and what to expect.

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