Skip to main content
Glama

orthotomeo

by io.github.jrainsberger

Get passage text

get_passage
Read-only

Returns get_verse's result for every canonical verse in a contiguous, single-book range, in order - verse boundaries preserved, never concatenated into one blob.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bookYesUSFM book code (e.g. GEN, PSA, MAT, REV) or the full English book name, any case (e.g. Genesis, matthew)
editionsYesverse-text editions to fetch verbatim text from: KJV, ASV, WEB, BSB, Brenton
end_verseYeslast verse of the range, inclusive
end_chapterYeslast chapter of the range, inclusive
start_verseYesfirst verse of the range, inclusive
start_chapterYesfirst chapter of the range, inclusive

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
engineYes
sourcesNo
citationsYes

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, so no safety concerns. The description adds behavioral details: verse boundaries preserved, returned in order, never concatenated. This exceeds what annotations provide.

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

Conciseness5/5

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

Single sentence, no wasted words. Key behaviors (range, order, boundaries) are front-loaded.

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 output schema present and clear annotations, the description covers essential behavior. It could mention edge cases (e.g., two-book ranges not allowed) but is sufficient for core use.

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% and each parameter is described. The description adds minor context (single-book range, contiguous), but the schema already carries the primary 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?

The description states it returns get_verse's result for a contiguous range, preserving verse boundaries. It clearly distinguishes from get_verse (single verse) and other siblings.

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 description implies when to use: for a contiguous, single-book range. It does not explicitly state when not to use or mention alternatives, but the sibling context makes it clear that get_verse is for single verses.

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

All orthotomeo toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.2/5.0
Disambiguation5/5

Each tool targets a distinct operation or output type. Even closely related tools like concord_lemma, concord_phrase, and count have clear differences in what they return (full concordance vs. phrase match vs. tally), and tools like interlinear, parse, and lexicon_lookup are well-differentiated by their descriptions.

Naming Consistency3/5

Tool names follow multiple patterns: some are single-word verbs (cite, count, parse), others are compound nouns (attestation, interlinear), and some use underscores in verb_noun or noun_noun form (concord_lemma, get_passage, lexicon_lookup). While each name is descriptive, the lack of a uniform convention reduces consistency.

Tool Count5/5

12 tools effectively cover the domain of biblical text analysis: retrieval, concordance, parsing, lexical lookup, attestation, and citation. This count is neither too sparse nor overwhelming, and each tool serves a clear purpose within the workflow.

Completeness4/5

The tool surface covers core operations for biblical study (verse retrieval, morphological analysis, lexicon lookup, concordance, citation). Minor gaps exist, such as the lack of tools for searching by English word or for handling Hebrew texts beyond limited lexicon lookup, but these do not severely hinder typical workflows.

Resources