Skip to main content
Glama

get_bible_verse

Retrieve plain Bible verse text from JW.org by specifying book, chapter, and verse numbers. Returns only the verse content without study notes or additional commentary.

Instructions

Get plain Bible verse text from wol.jw.org. Returns just the verse text without study notes or additional content. For comprehensive study content including notes and cross-references, use get_verse_with_study instead.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bookYesBible book number (1-66). Examples: Genesis=1, Matthew=40, John=43, Revelation=66. Use search_bible_books to find book numbers.
chapterYesChapter number within the book
verseYesVerse number within the chapter

Implementation Reference

  • The core handler function that validates the Bible reference, fetches the verse text using the wol-scraper, formats the response as JSON, and handles errors.
    export async function getBibleVerseImplementation(book, chapter, verse) {
      try {
        // Validate inputs
        const validation = validateReference(book, chapter, verse);
        if (!validation.valid) {
          return {
            content: [{
              type: 'text',
              text: `Validation error: ${validation.error}`
            }],
            isError: true
          };
        }
    
        // Fetch verse
        const verseData = await scraper.getSingleVerse(book, chapter, verse);
    
        // Format reference
        const reference = formatReference(book, chapter, verse);
    
        return {
          content: [{
            type: 'text',
            text: JSON.stringify({
              reference: reference,
              book_number: verseData.book_num,
              book_name: verseData.book_name,
              chapter: verseData.chapter,
              verse: verseData.verse_num,
              text: verseData.verse_text
            }, null, 2)
          }]
        };
    
      } catch (error) {
        return {
          content: [{
            type: 'text',
            text: `Error fetching verse: ${error.message}`
          }],
          isError: true
        };
      }
    }
  • The tool schema definition, including name, description, and input validation schema requiring book, chapter, and verse numbers.
    export const getBibleVerseTool = {
      name: 'get_bible_verse',
      description: 'Get plain Bible verse text from wol.jw.org. Returns just the verse text without study notes or additional content. For comprehensive study content including notes and cross-references, use get_verse_with_study instead.',
      inputSchema: {
        type: 'object',
        properties: {
          book: {
            type: 'number',
            description: 'Bible book number (1-66). Examples: Genesis=1, Matthew=40, John=43, Revelation=66. Use search_bible_books to find book numbers.'
          },
          chapter: {
            type: 'number',
            description: 'Chapter number within the book'
          },
          verse: {
            type: 'number',
            description: 'Verse number within the chapter'
          }
        },
        required: ['book', 'chapter', 'verse']
      }
    };
  • src/index.js:52-56 (registration)
    MCP server registration for ListToolsRequestSchema, which returns the allTools array containing getBibleVerseTool.
    server.setRequestHandler(ListToolsRequestSchema, async () => {
      return {
        tools: allTools,
      };
    });
  • Switch case in the handleScriptureTools dispatcher that routes calls to the getBibleVerseImplementation handler.
    case 'get_bible_verse':
      return await getBibleVerseImplementation(
        args.book,
        args.chapter,
        args.verse
      );
  • src/index.js:33-40 (registration)
    The allTools array that collects and registers getBibleVerseTool for use in the MCP server.
    const allTools = [
      captionsTool,
      ...workbookTools,
      ...watchtowerTools,
      searchBibleBooksTool,
      getBibleVerseTool,
      getVerseWithStudyTool,
      getBibleVerseURLTool
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden. It discloses the return format ('just the verse text without study notes or additional content'), which is valuable behavioral context. However, it doesn't mention potential limitations like rate limits, authentication needs, or error conditions, leaving some behavioral aspects unspecified.

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 two sentences with zero waste: the first sentence states the purpose and output, and the second provides usage guidance. It's front-loaded with essential information and appropriately sized for the tool's complexity.

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?

Given the tool's moderate complexity (3 required parameters, no output schema, no annotations), the description is mostly complete: it clarifies the purpose, distinguishes from siblings, and describes the return format. However, it could benefit from mentioning potential errors or limitations to be fully comprehensive.

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%, so the schema already documents all three parameters thoroughly. The description doesn't add any parameter-specific information beyond what's in the schema, which is acceptable given the high coverage, resulting in the baseline score of 3.

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 specific action ('Get plain Bible verse text') and resource ('from wol.jw.org'), distinguishing it from sibling tools like 'get_verse_with_study' by specifying it returns 'just the verse text without study notes or additional content'. This provides precise differentiation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly states when to use this tool ('for plain Bible verse text') and when to use an alternative ('For comprehensive study content including notes and cross-references, use get_verse_with_study instead'), providing clear guidance on tool selection.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/advenimus/jw-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server