Skip to main content
Glama

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

Look up a word

get_word
Read-onlyIdempotent

Returns one Strong's entry (Hebrew H… or Greek G…): lemma, transliteration, definition, KJV renderings, occurrence count and verses per book. For Hebrew it adds the Brown–Driver–Briggs entry and, for a name, how it is built from its parts; it also gives the Septuagint renderings of a Hebrew word, or the Hebrew words a Greek word renders. Use when the user asks what a Hebrew or Greek word means, given its Strong's number.

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": {
      "strongs": "<strongs>"
    },
    "name": "get_word"
  }
}

Input Schema

NameRequiredDescriptionDefault
formatNooptional: json (default) or markdown (compact, readable)
strongsYese.g. H430 or G26
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. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already cover read-only, idempotent, closed-world behavior, so the bar is lower. The description adds real value by disclosing language-dependent enrichment (BDB for Hebrew, name-part derivation, LXX/Hebrew cross-renderings), but it says nothing about response size, truncation, or pagination behavior that the schema hints at with max_chars and offset/nextOffset.

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 return payload and followed by the usage condition. Dense but every clause carries information; the middle sentence is long and could be split, but nothing is filler.

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?

There is no output schema, so the description must convey return shape, and it does so thoroughly for both languages. The main residual gap is truncation and offset/nextOffset behavior, which lives only in the schema rather than being surfaced as 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 coverage is 100%, so format, strongs, and max_chars are already documented. The description only reinforces the strongs format ('H… or G…'), which the schema already states, so baseline 3 applies since it adds no new parameter meaning.

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 ('Returns one Strong's entry') and enumerates exactly what the record contains (lemma, transliteration, definition, KJV renderings, occurrence count, verses per book), which cleanly separates it from the list-oriented sibling get_word_occurrences.

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?

Explicitly states the triggering condition: 'Use when the user asks what a Hebrew or Greek word means, given its Strong's number.' That is a clear usage context, but it gives no exclusions or named alternatives for adjacent tasks such as listing where a word occurs or finding collocations.

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