orthotomeo

List lemmas

lemmatize

Read-only

Returns the ordered lemma list for a verse (words with no lemma are omitted, not fabricated).

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
`corpus`	Yes	word-tagged corpus: TAGNT, TAHOT, Swete, OSS-LXX-lemma
`chapter`	Yes	chapter number

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"
+]
```

Changed2 schema fields changedJul 25, 2026

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

Behavior4/5

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

The description adds value beyond the readOnlyHint annotation by clarifying that words without lemmas are omitted rather than fabricated. However, it does not explain the ordering criteria (e.g., word order) or provide details about response structure, though the output schema covers that.

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?

The description is a single sentence that immediately conveys the core functionality. Every word is meaningful, with no redundancy or unnecessary content.

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?

Given that an output schema exists, the description does not need to explain return values. It covers the main use case and an important edge case (missing lemmas). However, it does not specify behavior for empty results or invalid inputs, which could be slightly improved.

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?

All four parameters are fully described in the input schema (100% coverage), so the description does not need to add parameter details. The description adds no extra semantic value beyond what the schema already provides.

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 clearly states the action (returns ordered lemma list) and the target resource (a verse). It specifies that words without lemmas are omitted and not fabricated, which differentiates it from potential misinterpretations. This distinguishes it from sibling tools like parse or concord_lemma.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives like parse or concord_lemma. The description does not mention prerequisites, limitations, or scenarios where other tools would be more appropriate.

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.