Skip to main content
Glama

Besorah — the Bible in Hebrew, Greek, Aramaic and English

Compare two books' vocabulary

compare_books
Read-onlyIdempotent

Compares two books' vocabularies: the word counts of each, how many words they share, the rare words they share (most of whose uses are in these two books), and the words only one uses, 15 of each by default (limit 1-40). Same language only: two Hebrew books, two Greek ones, or a Septuagint book (editionA: septuagint) against a New Testament book. Use when the user asks how the vocabularies of two books compare.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "a": "<a>",
      "b": "<b>"
    },
    "name": "compare_books"
  }
}

Input Schema

NameRequiredDescriptionDefault
aYese.g. Isaiah
bYese.g. Matthew
limitNohow many results to return (1-40, default 15)
formatNooptional: json (default) or markdown (compact, readable)
editionANoedition of the first book, e.g. septuagint
editionBNoedition of the second book, e.g. hebrew-nt
max_charsNooptional: cap the answer at about this many characters (lists are shortened and marked truncated; use offset/nextOffset to get the rest)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / limit / description
      Previous value: -"how many to return"New value: +"how many results to return (1-40, default 15)"
  2. Changed2 schema fields changed
    • addedInput schema / properties / editionA / description
      Added value: +"edition of the first book, e.g. septuagint"
    • addedInput schema / properties / editionB / description
      Added value: +"edition of the second book, e.g. hebrew-nt"
  3. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world behavior, so the description adds the operational constraints that matter: both books must be in the same language, with a documented exception pairing a Septuagint edition against a New Testament book. It also defines what makes a word "rare" (most uses confined to the two books) and the default result size, which annotations cannot convey.

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?

Two sentences, front-loaded with the result categories and followed by the invocation condition. Slight redundancy in repeating "15 of each by default (limit 1-40)" that the schema already states, but nothing is padded or wasted.

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?

With seven parameters and no output schema, the description does the important work of telling the agent what the response contains (counts, overlap, rare overlap, exclusive words) and what constraints apply. The max_chars truncation/offset mechanics live only in the schema, which is acceptable but a small gap for a tool with this many optional controls.

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 every parameter is already documented, and the description largely restates the limit default and range. It does add genuine meaning for editionA by explaining the Septuagint-vs-New-Testament pairing, which the schema's bare "e.g. septuagint" does not, but format and max_chars get no treatment in the description.

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?

Names a specific verb and resource ("Compares two books' vocabularies") and enumerates the four result categories: counts per book, shared words, shared rare words, and words unique to one book. This clearly separates it from single-book siblings like get_vocabulary.

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

Usage Guidelines4/5

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

"Use when the user asks how the vocabularies of two books compare" gives an explicit trigger, and the same-language-only rule plus the editionA: septuagint vs. New Testament pairing spells out a hard precondition for invocation. It stops short of naming an alternative for single-book vocabulary queries, but the intended use case is unambiguous.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources