Skip to main content
Glama

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

A book's vocabulary

get_vocabulary
Read-onlyIdempotent

Returns a book's vocabulary. view=summary (default) gives its size, distinct words, hapax legomena (words used once in the whole text), words found only in that book, and its most frequent and most characteristic words; view=hapax, unique or words lists those words (25 per page by default, limit 1-100, and nextOffset continues). Use when the user asks about one book's vocabulary, rare words or words unique to it.

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": {
      "book": "<book>"
    },
    "name": "get_vocabulary"
  }
}

Input Schema

NameRequiredDescriptionDefault
bookYesthe book, e.g. Ruth
viewNosummary, hapax, unique or words
limitNohow many results to return (1-100, default 25)
formatNooptional: json (default) or markdown (compact, readable)
offsetNohow many results to skip; the previous answer's nextOffset is where its page ended
editionNohebrew | greek | septuagint
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-100, default 25)"
  2. Changed3 schema fields changed
    • addedInput schema / properties / book / description
      Added value: +"the book, e.g. Ruth"
    • addedInput schema / properties / offset / description
      Added value: +"how many results to skip; the previous answer's nextOffset is where its page ended"
    • addedInput schema / properties / view / description
      Added value: +"summary, hapax, unique or words"
  3. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile needs no repetition. The description does add genuine behavioral detail beyond that: default view, 25-per-page paging, limit 1-100, and that nextOffset continues the sequence. It omits the max_chars truncation behavior and the edition/format handling, which are meaningful for this tool.

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 purpose and default view are front-loaded, and every clause carries information about views, paging, or the use case. The dense semicolon-chained middle sentence is harder to scan than a short bulleted breakdown would be, but nothing is 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?

For a seven-parameter, no-output-schema read tool, the description covers the dominant concerns: what each view returns and how paging works. The remaining parameters are fully documented in the schema, so the only real gaps are the max_chars truncation contract and the edition switching 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 all seven parameters are already documented; the baseline of 3 applies. The description does add value by defining hapax legomena and by tying offset to the previous answer's nextOffset, but it says nothing about edition, format, or max_chars beyond the schema.

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?

"Returns a book's vocabulary" is a specific verb+resource, and the description enumerates what the summary contains (size, distinct words, hapax legomena, unique words, frequency/characteristic words). It implicitly scopes itself to a single book versus corpus-wide siblings like query_words or search_words, but never names an alternative explicitly.

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?

The closing sentence gives a clear when-to-use trigger: a user asking about one book's vocabulary, rare words, or words unique to it. Each view value is tied to a concrete intent, so view selection is unambiguous. No when-not guidance or named sibling alternative is provided.

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