Loading ToolBench
Model Context Protocol server providing structured, type-safe access to the Legacy Standard Bible (LSB) with tools for verse/passage/chapter retrieval and full-text search
LSBible MCP server demonstrates solid definition quality with clear naming conventions, reasonable descriptions, and structured schemas. All 4 tools follow verb_noun naming patterns (get_verse, get_passage, get_chapter, search_bible). Descriptions are present and contextual (average ~60-90 chars, within rubric p10-p90 range). Input schemas use proper JSON Schema with types and descriptions for all parameters. However, there are notable gaps: output schemas are not visibly documented in the provided source code excerpt, error handling guidance is absent, and parameter descriptions lack constraint details (min/max values, pattern requirements). The tools are read-only (low risk) and well-scoped for a domain library, but fall short of A-grade production standards in output documentation and error guidance patterns.
Fetch an entire chapter
Fetch a range of verses (single or multi-chapter)
Fetch a single Bible verse by book, chapter, and verse
Full-text search across the entire Bible
Output schemas not documented. Tool definitions show input schemas but no visible documentation of what each tool returns. LLMs cannot plan downstream tool calls or extract structured data without knowing the output schema.
Parameter descriptions lack constraint details. 'Chapter number' and 'Verse number' lack min/max bounds. 'Search query text' lacks length limits. Descriptions should state ranges and patterns explicitly (e.g., 'positive integer, typically 1 - 150').
No error handling or recovery guidance. No indication of what happens when a book/chapter/verse combination does not exist, or when a search returns no results. Error responses should guide the LLM on next steps (pattern:recovery-guide).
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-21 | C | 64 | 2026-07-28+ | v2 |
| 2026-03-09 | C | 65 | - | v1 |
No pagination documented for search_bible. Full-text search could return hundreds of results. Tool should accept limit and offset/cursor parameters and document result capping behavior.
BookName enum values not enumerated in source excerpt. Parameter shows enum: '[BookName enum values]' but actual enum list is not visible. Cannot verify if enum is comprehensive or properly documented.