Skip to main content
Glama

getWorkbookLinks

Retrieve available weekly CLM meeting workbook titles and RTF download links from JW.org, automatically using current month/year for the issue.

Instructions

STEP 1: Get JW.org "Our Christian Life and Ministry" (CLM) meeting workbook weeks. When a user asks for CLM workbook content, use this tool FIRST to show them available weeks. Returns weekly titles like "May 5-11 (Proverbs 12)" with their RTF download URLs. Automatically uses current month/year for the issue.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pubNoPublication code: "mwb" for Meeting Workbook (CLM workbook)mwb
langwrittenNoLanguage code: "E" for English, "S" for Spanish, etc.E
issueNoIssue in YYYYMM00 format. Leave empty to use current month/year automatically (e.g., "20250500" for May 2025)
fileformatNoFile format: "RTF" for Rich Text FormatRTF

Implementation Reference

  • The core handler function that fetches workbook data via fetchPublicationData, processes the file list to extract individual week RTF links (skipping ZIP), and returns structured metadata including publication name, date, issue, language, and array of weekFiles with title, URL, size, etc.
    export async function getWorkbookLinks(pub = 'mwb', langwritten = 'E', issue = null, fileformat = 'RTF') {
      try {
        const { files, pubName, formattedDate, language } = await fetchPublicationData(pub, langwritten, issue, fileformat);
        
        // Skip the first item (ZIP file) and return the individual week files
        const weekFiles = files.slice(1).map((file, index) => ({
          title: file.title,
          url: file.file.url,
          filesize: file.filesize,
          track: file.track,
          modifiedDatetime: file.file.modifiedDatetime,
          checksum: file.file.checksum
        }));
    
        return {
          pubName,
          formattedDate,
          issue: issue || getCurrentIssue(),
          language,
          weekFiles
        };
    
      } catch (error) {
        throw new Error(`Failed to fetch workbook links: ${error.message}`);
      }
    }
  • MCP tool registration definition including name, detailed usage description, and inputSchema with optional parameters (pub, langwritten, issue, fileformat) and defaults.
    {
      name: 'getWorkbookLinks',
      description: 'STEP 1: Get JW.org "Our Christian Life and Ministry" (CLM) meeting workbook weeks. When a user asks for CLM workbook content, use this tool FIRST to show them available weeks. Returns weekly titles like "May 5-11 (Proverbs 12)" with their RTF download URLs. Automatically uses current month/year for the issue.',
      inputSchema: {
        type: 'object',
        properties: {
          pub: {
            type: 'string',
            description: 'Publication code: "mwb" for Meeting Workbook (CLM workbook)',
            default: 'mwb'
          },
          langwritten: {
            type: 'string', 
            description: 'Language code: "E" for English, "S" for Spanish, etc.',
            default: 'E'
          },
          issue: {
            type: 'string',
            description: 'Issue in YYYYMM00 format. Leave empty to use current month/year automatically (e.g., "20250500" for May 2025)'
          },
          fileformat: {
            type: 'string',
            description: 'File format: "RTF" for Rich Text Format',
            default: 'RTF'
          }
        },
        required: []
      }
    },
  • Input schema for the getWorkbookLinks tool, defining object with properties pub (string, default 'mwb'), langwritten (string, default 'E'), issue (string, optional), fileformat (string, default 'RTF'), no required fields.
    inputSchema: {
      type: 'object',
      properties: {
        pub: {
          type: 'string',
          description: 'Publication code: "mwb" for Meeting Workbook (CLM workbook)',
          default: 'mwb'
        },
        langwritten: {
          type: 'string', 
          description: 'Language code: "E" for English, "S" for Spanish, etc.',
          default: 'E'
        },
        issue: {
          type: 'string',
          description: 'Issue in YYYYMM00 format. Leave empty to use current month/year automatically (e.g., "20250500" for May 2025)'
        },
        fileformat: {
          type: 'string',
          description: 'File format: "RTF" for Rich Text Format',
          default: 'RTF'
        }
      },
      required: []
    }
  • Dispatcher helper in handleWorkbookTools function that matches tool name, extracts arguments from MCP request.params.arguments, calls getWorkbookLinks, returns JSON stringified result as text content or error response.
    // Handle getWorkbookLinks tool
    if (request.params.name === 'getWorkbookLinks') {
      try {
        const { pub, langwritten, issue, fileformat } = request.params.arguments || {};
        const result = await getWorkbookLinks(pub, langwritten, issue, fileformat);
        
        return {
          content: [
            {
              type: 'text',
              text: JSON.stringify(result, null, 2),
            },
          ],
        };
      } catch (error) {
        return {
          content: [
            {
              type: 'text',
              text: `Error: ${error.message}`,
            },
          ],
          isError: true,
        };
      }
    }
Behavior3/5

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

With no annotations provided, the description carries full burden. It discloses the automatic current month/year behavior and RTF format focus, which are useful behavioral traits. However, it doesn't mention potential rate limits, authentication needs, error conditions, or pagination behavior for the returned list of weeks.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is appropriately sized and front-loaded with the core purpose. The 'STEP 1' framing and automatic behavior explanation are useful. However, the phrasing could be slightly more concise by integrating the RTF and automatic behavior into the main purpose statement rather than as separate sentences.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with 4 parameters, 100% schema coverage, but no annotations or output schema, the description provides adequate context about when to use it and the automatic behavior. However, it doesn't describe the structure of returned data (beyond mentioning titles and URLs) or potential limitations, leaving some gaps for an agent to understand the complete tool behavior.

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 fully documents all 4 parameters. The description adds minimal parameter semantics beyond the schema - it mentions 'RTF download URLs' which aligns with the fileformat parameter, and 'current month/year' which relates to the issue parameter. Baseline 3 is appropriate when schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose: 'Get JW.org "Our Christian Life and Ministry" (CLM) meeting workbook weeks' and specifies it returns weekly titles with RTF download URLs. It distinguishes from sibling 'getWorkbookContent' by indicating this tool shows available weeks first, but doesn't explicitly contrast with other workbook-related tools like 'getWatchtowerLinks'.

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 provides explicit usage guidance: 'When a user asks for CLM workbook content, use this tool FIRST to show them available weeks.' This clearly indicates when to use this tool versus alternatives like 'getWorkbookContent' for actual content, and specifies the automatic current month/year behavior.

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