orthotomeo

Get verse text

get_verse

Read-only

Returns verbatim verse text with provenance for one canonical reference, one Citation per requested edition (KJV, ASV, WEB, BSB, Brenton).

Input Schema

TableJSON Schema

Name	Required	Description
`book`	Yes	USFM book code (e.g. GEN, PSA, MAT, REV) or the full English book name, any case (e.g. Genesis, matthew)
`verse`	Yes	verse number
`chapter`	Yes	chapter number
`editions`	Yes	verse-text editions to fetch verbatim text from: KJV, ASV, WEB, BSB, Brenton

Output Schema

TableJSON Schema

Name	Required	Description	Default
`engine`	Yes
`sources`	No
`citations`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedJul 25, 2026
- addedOutput schema / properties / sources / additionalProperties / properties / name
```
Added value: +{
+  "type": "string"
+}
```
- changedOutput schema / properties / sources / additionalProperties / required
```
Previous value: -[
-  "file",
-  "license"
-]New value: +[
+  "name",
+  "file",
+  "license"
+]
```

Changed3 schema fields changedJul 25, 2026

changedInput schema / properties / editions / description

Previous value: -"verse-text editions to fetch verbatim text from: KJV, ASV, WEB, Brenton"New value: +"verse-text editions to fetch verbatim text from: KJV, ASV, WEB, BSB, Brenton"

addedOutput schema / properties / engine
```
Added value: +{
+  "type": "string"
+}
```

changedOutput schema / required

Previous value: -[
-  "citations"
-]New value: +[
+  "citations",
+  "engine"
+]

First observedJul 17, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, so the description's confirmation of returning verbatim text with provenance adds little beyond that. No additional behavioral details (e.g., error handling, rate limits) are disclosed. No contradiction.

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, front-loaded with core action and resource, no extraneous words. Every word earns its place.

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 simple read tool with output schema, the description adequately specifies what is returned (verbatim text, provenance, one citation per edition). It does not cover edge cases or error handling, but this is acceptable given the tool's simplicity and annotation support.

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% with clear descriptions for all 4 parameters. The tool description does not add further semantic meaning beyond the schema, so baseline score of 3 applies.

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?

Description clearly states verb 'Returns', resource 'verse text', scope 'one canonical reference, one Citation per requested edition', and lists specific editions. This distinguishes it from sibling tools like get_passage.

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

Usage Guidelines3/5

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

Description implies usage for single verse lookup across multiple editions but does not explicitly explain when to use versus alternatives like get_passage, concord_*, or interlinear. No when-not or alternative guidance provided.

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

All orthotomeo tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.