Urantia Papers

Semantic Search

search.semantic

Read-onlyIdempotent

Search the Urantia Papers using semantic similarity (vector embeddings). Returns conceptually related results even without exact keyword matches.

Input Schema

TableJSON Schema

Name	Required	Description
`q`	No	Alias for `query` (REST compatibility).
`page`	No	Page number (0-indexed)
`limit`	No	Results per page (1-100)
`query`	No	Natural language query. Example: "What is the meaning of life?"
`part_id`	No	Filter to a specific part ID (1-4)
`paper_id`	No	Filter to a specific paper ID
`include_entities`	No	Include entity mentions
`include_bible_parallels`	No	Include the top-10 Bible verses semantically nearest to each result (Urantia → Bible).
`include_urantia_parallels`	No	Include the top-10 most-similar OTHER Urantia paragraphs for each result.

Output Schema

TableJSON Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedOct 3, 2026

changedInput schema / properties / include_bible_parallels / description

Previous value: -"Include the top-10 Bible verses semantically nearest to each result (UB → Bible)."New value: +"Include the top-10 Bible verses semantically nearest to each result (Urantia → Bible)."

removedOutput schema / properties / data / items / properties / audio
```
Removed value: -{}
```
removedOutput schema / properties / data / items / properties / htmlText
```
Removed value: -{
-  "type": "string"
-}
```

changedOutput schema / properties / data / items / required

Previous value: -[
-  "id",
-  "standardReferenceId",
-  "sortId",
-  "paperId",
-  "sectionId",
-  "partId",
-  "paperTitle",
-  "sectionTitle",
-  "paragraphId",
-  "text",
-  "htmlText",
-  "labels",
-  "audio",
-  "similarity"
-]New value: +[
+  "id",
+  "standardReferenceId",
+  "sortId",
+  "paperId",
+  "sectionId",
+  "partId",
+  "paperTitle",
+  "sectionTitle",
+  "paragraphId",
+  "text",
+  "labels",
+  "similarity"
+]

Changed4 schema fields changedMay 8, 2026

addedInput schema / properties / include_bible_parallels

Added value: +{
+  "default": false,
+  "description": "Include the top-10 Bible verses semantically nearest to each result (UB → Bible).",
+  "type": "boolean"
+}

addedInput schema / properties / include_urantia_parallels

Added value: +{
+  "default": false,
+  "description": "Include the top-10 most-similar OTHER Urantia paragraphs for each result.",
+  "type": "boolean"
+}

addedOutput schema / properties / data / items / properties / bibleParallels

Added value: +{
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "bookCode": {
+        "type": "string"
+      },
+      "chapter": {
+        "maximum": 9007199254740991,
+        "minimum": -9007199254740991,
+        "type": "integer"
+      },
+      "chunkId": {
+        "type": "string"
+      },
+      "embeddingModel": {
+        "type": "string"
+      },
+      "rank": {
+        "maximum": 9007199254740991,
+        "minimum": -9007199254740991,
+        "type": "integer"
+      },
+      "reference": {
+        "type": "string"
+      },
+      "similarity": {
+        "type": "number"
+      },
+      "source": {
+        "type": "string"
+      },
+      "text": {
+        "type": "string"
+      },
+      "verseEnd": {
+        "maximum": 9007199254740991,
+        "minimum": -9007199254740991,
+        "type": "integer"
+      },
+      "verseStart": {
+        "maximum": 9007199254740991,
+        "minimum": -9007199254740991,
+        "type": "integer"
+      }
+    },
+    "required": [
+      "chunkId",
+      "reference",
+      "bookCode",
+      "chapter",
+      "verseStart",
+      "verseEnd",
+      "text",
+      "similarity",
+      "rank",
+      "source",
+      "embeddingModel"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

addedOutput schema / properties / data / items / properties / urantiaParallels

Added value: +{
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "embeddingModel": {
+        "type": "string"
+      },
+      "id": {
+        "type": "string"
+      },
+      "paperId": {
+        "type": "string"
+      },
+      "paperTitle": {
+        "type": "string"
+      },
+      "rank": {
+        "maximum": 9007199254740991,
+        "minimum": -9007199254740991,
+        "type": "integer"
+      },
+      "sectionTitle": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "similarity": {
+        "type": "number"
+      },
+      "source": {
+        "type": "string"
+      },
+      "standardReferenceId": {
+        "type": "string"
+      },
+      "text": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "id",
+      "standardReferenceId",
+      "paperId",
+      "paperTitle",
+      "sectionTitle",
+      "text",
+      "similarity",
+      "rank",
+      "source",
+      "embeddingModel"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

First observedMay 3, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds the behavioral note that semantic matching can return results with no literal term overlap, but says nothing about pagination defaults, result volume, or cost/latency of embedding search.

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?

Two sentences, front-loaded with purpose, no filler. It is efficient, though notably terse given a nine-parameter tool with rich optional enrichment flags.

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

Completeness3/5

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

An output schema and full annotations exist, so return values and safety need no explanation here. However, with zero required parameters yet a query string effectively needed to get results, and with two overlapping query parameters (q vs. query), the description does nothing to head off an empty or ambiguous call.

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 description coverage is 100%, so all nine parameters (including the q/query alias, filters such as paper_id/part_id, and the include_* enrichment flags) are already documented in the schema. The description adds no parameter-level meaning, so the baseline 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?

States a specific verb and resource ('Search the Urantia Papers') plus the mechanism ('semantic similarity (vector embeddings)'), which implicitly distinguishes it from the keyword-based sibling search.fulltext and from bible.search.semantic's different corpus. An agent can tell what it does and why it differs from full-text search without opening the schema.

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?

The clause 'Returns conceptually related results even without exact keyword matches' implies when this tool beats a keyword search, but the description never names search.fulltext or search.semantic alternatives, states no exclusions, and gives no guidance on the optional filters or parallel-enrichment flags. Usage is inferable but not stated.

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

Context All Your Agents Can ShareAgents share what they learn, hand off work, and hold it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.