SoapBox Faith

score_doctrinal_fit

Read-only

Assess how well a statement aligns with a named Christian tradition's historic doctrinal positions (e.g. Reformed, Roman Catholic, Pentecostal, Eastern Orthodox). Returns an impartial alignment rating, score, summary, and the relevant doctrinal loci. Analytical, not proselytizing. No key required.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`statement`	Yes	The theological statement or claim to assess.
`tradition`	Yes	The Christian tradition or denomination to assess alignment against.

TDQS

A4.2/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 beyond this: it returns an impartial rating, score, summary, and doctrinal loci, and explicitly states it is analytical and not proselytizing. These details clarify the tool's tone and output, going beyond the structured 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 concise, consisting of two focused sentences. The first states the core purpose, and the second covers output, impartiality, and access requirements. Every sentence contributes meaningful information without 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?

Despite having no output schema, the description clearly enumerates the return values (rating, score, summary, loci) and notes the impartial, analytical nature. It does not mention potential errors or limitations, but for a read-only, non-destructive tool, the description is sufficiently complete for an agent to use it effectively.

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%, with both parameters fully described and examples provided. The description does not add additional parameter-specific semantics beyond what the schema already offers, so it relies on the schema to carry the 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 description clearly states the tool assesses doctrinal alignment with named Christian traditions, using specific verbs and resources. It distinguishes itself from siblings like verify_scripture by focusing on tradition-based evaluation rather than scriptural verification.

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 provides clear context on the tool's appropriate use: it's analytical, not proselytizing, and requires no key, implying open access. However, it does not explicitly mention when not to use it or mention sibling alternatives, falling slightly short of full guidance.

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?