orthotomeo

Search concordance (lemma)

concord_lemma

Read-only

Complete-or-fail concordance: every words row in corpus whose lemma, dStrong, or (with by="surface") exact inflected surface form matches query. Route lemma/Strong's-number/surface-word lookups here, never by writing SQL or guessing occurrences from memory. This deployment caps one concordance result at 2000 occurrences and refuses anything broader, reporting the exact match count in the error. Call count first when a query might be broad - count is never capped.

Input Schema

TableJSON Schema

Name	Required	Description
`by`	No	optional match column override: lemma, dstrong, or surface. Omit for auto-detect (dStrong shape, else lemma) - surface must always be requested explicitly, it is never guessed
`query`	Yes	a lemma (e.g. ἄφεσις), a disambiguated Strong's number (e.g. G0859, H7225G), or (with by="surface") the exact inflected word as it appears in the verse
`corpus`	Yes	word-tagged corpus to search: TAGNT (Greek NT), TAHOT (Hebrew OT), Swete (LXX surface), OSS-LXX-lemma (LXX lemma)

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

A4.9/5.0

Behavior5/5

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

Discloses behavioral traits beyond annotations: caps at 2000 occurrences, refuses broader queries, reports exact match count in error. readOnlyHint already indicates non-destructive, but description adds critical constraints.

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?

Three sentences, each meaningful. Front-loaded with 'Complete-or-fail concordance'. No superfluous text every sentence earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity (parameter options, multiple corpora, limits) and existence of output schema, the description is fully complete: covers purpose, usage, parameters, behavior, and provides guidance on alternatives.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, baseline is 3. Description adds value by explaining the 'by' parameter (auto-detect vs explicitly request surface), and clarifies query format (lemma, Strong's number, surface). Slightly above baseline.

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?

Clearly states the tool searches concordance by lemma, dStrong, or surface form. Distinguishes from sibling tools like 'count' and 'concord_phrase' by directing lemma/Strong's-number/surface-word lookups here.

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

Usage Guidelines5/5

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

Explicitly advises to route lookups here instead of writing SQL or guessing from memory, and recommends calling 'count' first when a query might be broad. Provides clear when-to-use and when-not-to-use guidance.

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.