The Bible MCP server has 1 implemented tool (getEnglishText) with basic structure, but significant quality gaps. The tool has a functional name and description, but the schema is incomplete: the input schema in server.ts declares 'reference' as a string but lacks formal type and required array wrapper (should be {"type":"object","properties":{...},"required":["reference"]}). The tool registration uses Zod for schema definition, which is good practice, but the schema returned in capabilities declaration is malformed, it lists properties directly without the JSON Schema wrapper. No output schema is documented anywhere, forcing the LLM to infer response structure. Parameter description exists but is minimal (58 chars). Error handling returns helpful text ('Invalid Bible reference...') but lacks structured error categorization and recovery guidance. The commented-out searchText tool suggests planned features but cannot be scored. No security considerations are visible (no input validation beyond reference parsing, no rate limiting, no audit logging). The tool is marked READ_ONLY, which is accurate, but no explicit tool annotations (readOnlyHint, idempotentHint) are used in the schema.

• Fix the input schema in capabilities declaration: wrap 'reference' in a proper JSON Schema object with type, properties, and required array: {"type":"object","properties":{"reference":{"type":"string",...}},"required":["reference"]}
• Document the output schema explicitly. Add a comment or field describing that the tool returns {content: [{type: string, text: string}], examples?: [...]}, so LLMs know what to expect.
• Improve the 'reference' parameter description: change from 'Bible verse reference (e.g., ...)' to 'Bible verse reference in the format "<Book> <chapter>:<verse>" or "<Abbreviation> <chapter>:<verse>". Examples: John 3:16, Gen 1:1, Rom 8:28. Abbreviations are case-insensitive.'
• Enhance error responses to categorize and guide recovery. When reference parsing fails, return: {type: 'text', text: 'Invalid reference format: "...". Expected format: "<Book> <chapter>:<verse>" or "<Abbreviation> <chapter>:<verse>". Try "John 3:16" or "Genesis 1:1".'}
• When no text is found for a valid reference, check if it's a data availability issue (book exists but chapter/verse out of range) vs. a typo in the book name. Return relevant recovery hints or suggestions for similar book names.
• Add a readOnlyHint annotation to the tool schema to declare its side-effect-free nature: readOnlyHint: true (when using tool registration patterns that support annotations).
• Consider adding a searchText tool (currently commented out) to complement getEnglishText. This expands utility and gives users two clear pathways: retrieve a known verse or find verses containing a keyword.