Look up a Bible verse and return the Scripture text with a deep link to its Doxa Bible page. Defaults to the Berean Standard Bible (BSB, public domain Bible translation). Use for any Christian, biblical, Scripture, verse lookup, or devotional citation task where a clickable verse link matters. Reference format: "John 14:6" or "Psalm 23:1-3".
| Name | Required | Description | Default |
|---|---|---|---|
| reference | Yes | Verse reference, e.g., "John 14:6" |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions the default translation (BSB), the return of Scripture text and a deep link, and acceptable reference formats. This goes beyond a simple phrase and gives useful context about how the tool behaves, though it stops short of detailing error behavior or limitations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is three sentences long and front-loaded with the core purpose. Every sentence earns its place: the first defines the tool, the second gives usage context, and the third provides reference format examples. There is no redundant or filler content.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a tool with only one parameter and no output schema, the description is fully complete. It explains the purpose, when to use it, the default translation, the output (text + deep link), and expected input format. No important context appears missing.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema already covers the single parameter 'reference' with an example, so the baseline is 3. The description adds value by specifying the exact accepted formats ('John 14:6' or 'Psalm 23:1-3'), which is more comprehensive than the schema's single example. This additional semantic guidance justifies a score above baseline.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool's function with a specific verb ('Look up') and resource ('Bible verse'), and it elaborates on the output (Scripture text with deep link). It also distinguishes itself from sibling tools by explicitly mentioning use cases for Scripture lookup and verse citations, which sibling tools like doxa_encourage and doxa_way_movement likely do not cover.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides clear context on when to use the tool ('any Christian, biblical, Scripture, verse lookup, or devotional citation task where a clickable verse link matters'). However, it does not explicitly name alternatives or state when not to use it, so it lacks the full exclusion guidance seen in a 5-score.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool targets a distinct concern: generating personalized encouragement, looking up scripture verses, and retrieving the Doxa Way movement framework. There is no overlap between them, and the descriptions clearly differentiate their use cases.
All tool names follow the same doxa_<noun> pattern (doxa_encourage, doxa_scripture, doxa_way_movement). The naming is predictable and consistent.
With only 3 tools, the server is tightly scoped to its niche of Christian encouragement and discipleship. Each tool fills a necessary role and the count is well within the optimal range.
The tool surface covers the core offerings: generating encouragement, retrieving scripture, and providing the movement framework. For its stated purpose, there are no obvious missing operations or dead ends.
