Skip to main content
Glama

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

Find a Hebrew or Greek word

search_words
Read-onlyIdempotent

Finds Hebrew and Greek words (Strong's entries) from an English word, a transliteration ('shalom', 'agape') or the original word. Returns the best matches first (10 by default, up to 25), each with its Strong's id, lemma, definition, occurrence count and link; 'more' says how many further matches exist. Use when the user asks which Hebrew or Greek word lies behind an English word or transliteration.

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": {
      "query": "<query>"
    },
    "name": "search_words"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNohow many results to return (1-25, default 10)
queryYesan English word, a transliteration (shalom, agape) or the Hebrew or Greek word itself
formatNooptional: json (default) or markdown (compact, readable)
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: -"1-25, default 10"New value: +"how many results to return (1-25, default 10)"
  2. Changed1 schema field changed
    • addedInput schema / properties / query / description
      Added value: +"an English word, a transliteration (shalom, agape) or the Hebrew or Greek word itself"
  3. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world and non-destructive, so the bar is lower. The description still adds real behavior: results are ranked 'best matches first', default 10 with a 25 ceiling, each result carries Strong's id, lemma, definition, occurrence count and link, and a 'more' count reports remaining matches.

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?

Front-loaded with what is found, then what is returned, then when to use it. Dense but free of filler, though the single run-on structure could be split for faster scanning of the usage clause.

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?

No output schema exists, yet the description covers the return shape (fields, ranking, 'more' count) and pagination signal, which is what an agent needs. Minor gaps remain around format choice and interaction with max_chars/offset truncation, which only the schema addresses.

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 query, limit, format and max_chars, including ranges and defaults. The description only reinforces the limit default/ceiling and adds the ranking notion, which is modest added meaning over structured fields; baseline 3 is appropriate.

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?

States a specific verb and resource: 'Finds Hebrew and Greek words (Strong's entries)' and enumerates the three accepted query forms. It is easy to tell apart from id-fetching siblings like get_word, though no sibling is named explicitly for contrast.

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 which Hebrew or Greek word lies behind an English word or transliteration' gives a clear triggering condition. No when-not guidance or named alternatives (e.g., fetching a known Strong's entry directly) are provided, keeping it below a 5.

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