Urantia Papers

Semantic Search of the Works

works.search.semantic

Read-onlyIdempotent

Natural-language search across the Bible and the other works, or one work with work. The list holds the 100 nearest chunks (a few verses each); each has similarity and strength (strong, related, weak), and meta.total is the length of that list, and meta.related counts the related or better. Each result has 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

A3.7/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/openWorld/non-destructive, so the safety profile is covered; the description instead adds behavioral detail the annotations cannot: the result list is capped at 100 nearest chunks, similarity is graded as strong/related/weak, and `meta.total`/`meta.related` measure the list versus the strong matches. The caveat that attached Urantia paragraphs are 'semantic parallels, not curated ones' is a genuinely useful disclosure an agent could otherwise misread as editorial cross-references.

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?

Three sentences, front-loaded with scope, and every sentence carries information. Slightly over-packed with backticked field names and the 'and ... and ...' chain, but there is no filler.

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 an output schema present and full parameter documentation, the description need not restate return values, and it is complete enough on scope and result semantics. The one gap is pagination: it says the list holds 100 nearest chunks while the schema exposes `page` and a default `limit` of 20, leaving the total-versus-page relationship mildly ambiguous.

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%, so the baseline is 3; the schema already explains `work`, `limit`, `page`, and `urantia_parallel_limit`. The description reinforces `work` scoping and implies the Urantia-paragraph attachment (urantia_parallel_limit), but adds no syntax or interaction detail (e.g., paging versus the 100-chunk cap) 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+resource (natural-language/semantic search over the Bible and other works) plus the scoping option via `work`. An agent can tell it is the semantic variant rather than keyword search, though it never names the sibling it supersedes (works.search, bible.search.semantic) to make the distinction airtight.

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?

Usage is only implied: 'across the Bible and the other works, or one work with `work`' tells the agent it may scope results, but there is no explicit when-to-use versus works.search or bible.search.semantic, and no prerequisites or exclusions. Adequate but leaves selection between siblings to inference.

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.