Urantia Papers

Search the Works

works.search

Read-onlyIdempotent

Keyword search across the Bible and the other works, or one work with work. A reference such as "John 3:16", "Jn 3:16-18", "Dhp 183", or "BG 2.47" gives those units first. Otherwise the exact phrase first, then every word, then (when few) a typo fix in meta.didYouMean. Each result has match, url, and its nearest Urantia paragraphs (semantic parallels, not curated ones).

Input Schema

Name	Required	Description
`q`	No	Alias for `query` (REST compatibility).
`page`	No	Page number (0-indexed)
`work`	No	One work only: "bible" or a work id from works.list, such as "dhammapada".
`limit`	No	Results per page (1-100)
`query`	No	Search query. Example: "love your enemies"
`urantia_parallel_limit`	No	How many Urantia paragraphs to attach to each result (0-10, default 3).

Output Schema

Name	Required	Description	Default
`data`	Yes
`meta`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 25, 2026

addedOutput schema / properties / data / items / properties / work / properties / catalogTranslation

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "license": {
+      "const": "CC0-1.0",
+      "type": "string"
+    },
+    "method": {
+      "const": "machine",
+      "type": "string"
+    },
+    "review": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    }
+  },
+  "required": [
+    "method",
+    "license",
+    "review"
+  ],
+  "type": "object"
+}

addedOutput schema / properties / data / items / properties / work / properties / textLanguage
```
Added value: +{
+  "const": "eng",
+  "type": "string"
+}
```

changedOutput schema / properties / data / items / properties / work / required

Previous value: -[
-  "id",
-  "title",
-  "tradition"
-]New value: +[
+  "id",
+  "title",
+  "tradition",
+  "textLanguage"
+]

Changed2 schema fields changedOct 19, 2026
- addedOutput schema / properties / data / items / properties / work / properties / tradition
```
Added value: +{
+  "type": "string"
+}
```
- changedOutput schema / properties / data / items / properties / work / required
```
Previous value: -[
-  "id",
-  "title"
-]New value: +[
+  "id",
+  "title",
+  "tradition"
+]
```
AddedOct 18, 2026

TDQS

A4.3/5.0

Behavior5/5

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

Annotations already declare a read-only, idempotent, closed-world search; the description adds real behavior beyond that: the ranking order (reference units, then exact phrase, then every word, then typo correction surfaced in `meta.didYouMean`) and the caveat that attached Urantia paragraphs are semantic parallels, not curated ones.

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-loads scope and the reference-match behavior in the first two sentences, with no filler. The dense backticks and quoted examples are efficient but make it slightly harder to scan than a cleaner layout would.

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?

With a full input schema, an output schema, and rich annotations, the description still covers ranking semantics, result fields (`match`, `url`, paragraphs), and the semantic-parallel caveat. Nothing an agent needs to call or interpret it is missing.

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 description coverage is 100%, so the baseline is 3; the description adds meaning by explaining that `work` narrows to one work and that results carry nearest Urantia paragraphs, tying to `urantia_parallel_limit`. It does not clarify the `q` alias or page/limit behavior beyond the schema.

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 ('Keyword search across the Bible and the other works') plus the scoping variant via `work`, which distinguishes it from the semantic siblings. It never names those siblings (works.search.semantic, search.fulltext) explicitly, so differentiation rests on the word 'keyword' alone.

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?

Gives clear usage contexts: pass a reference like 'John 3:16' to get those units first, otherwise it runs phrase then all-words matching, and `work` restricts to a single work. No explicit when-not guidance or pointer to the semantic variants for conceptual queries, so it lacks full routing clarity.

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

All Urantia Papers 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.