resolve_referenceNormalize any Bible reference into canonical form. Accepts abbreviations and loose formats ("Rom 8:28", "1 Cor 13", "Jn 3.16", "Psalm 23:1-4") and returns the canonical book name, chapter, verse range, OSIS id, and the verse text. Deterministic — no AI generation.
| Name | Required | Description | Default |
|---|---|---|---|
| reference | Yes | Any form, e.g. "Rom 8:28" | |
| translation | No | default: kjv |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries full burden. It discloses 'Deterministic — no AI generation' and lists output fields, but doesn't mention error handling, network dependence, or permission requirements. Some behavioral context is provided, but gaps remain.
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 two sentences, front-loads the purpose, uses concrete examples, and includes return values and determinism note. Every sentence contributes value.
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 no output schema and no annotations, the description explains return fields and determinism, but lacks explicit disambiguation from siblings and error behavior. Given the moderate complexity, it is mostly complete.
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 input schema already describes both parameters with examples, and the description repeats similar info. Schema coverage is 100%, so the description adds no significant extra meaning beyond the schema.
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 uses the specific verb 'normalize' with resource 'Bible reference', states it returns canonical form, and contrasts with siblings like get_verse_text by focusing on reference resolution rather than text retrieval.
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?
It implies usage for converting arbitrary user references to canonical form, but does not explicitly name alternatives or state when not to use it. The context is clear, but no exclusions or sibling comparisons are provided.
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.
Most tools have distinct purposes, but get_verse_text and resolve_reference overlap by both returning verse text, making it unclear when to use one over the other. The other three tools are clearly differentiated by their focus on study pages, AI-powered study, and fact-checking.
All tool names follow a consistent snake_case verb_noun pattern: find_verse_study_page, get_verse_text, resolve_reference, study_bible_passage, verify_scripture_quote. No mixed conventions or vague verbs.
Five tools is well-scoped for a Bible study copilot, covering retrieval, reference resolution, AI-assisted study, and quote verification without unnecessary bloat. Each tool has a clear role, and the count is within the ideal range.
The core workflow is covered: resolving references, fetching text, checking for study pages, asking AI questions, and verifying quotes. A minor gap is the lack of a dedicated search tool for finding verses by keyword, and the overlap between get_verse_text and resolve_reference slightly reduces efficiency, but the surface is largely complete.