Urantia Papers

Full-Text Search

search.fulltext

Read-onlyIdempotent

Full-text search across all paragraphs of the Urantia Papers. Supports three modes: "and" (all words must appear, default), "or" (any word), "phrase" (exact phrase). Results ranked by relevance.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`q`	No	Alias for `query` (REST compatibility).
`page`	No	Page number (0-indexed)
`type`	No	Search mode: phrase, and, or	and
`limit`	No	Results per page (1-100)
`query`	No	Search query. Example: "nature of God"
`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",
-  "rank"
-]New value: +[
+  "id",
+  "standardReferenceId",
+  "sortId",
+  "paperId",
+  "sectionId",
+  "partId",
+  "paperTitle",
+  "sectionTitle",
+  "paragraphId",
+  "text",
+  "labels",
+  "rank"
+]

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.8/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds behavior beyond that: the mode semantics (all/any/exact) and that results are ranked by relevance, which is useful context the annotations do not carry.

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 tight sentences: scope first, then modes with the default called out, then ranking behavior. No filler and everything is front-loaded.

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 a full output schema, return values need no explanation, and annotations cover safety. The description covers scope, modes, and ranking adequately for a 10-parameter search tool, though it never touches the filter or include_* flags that materially change results.

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% across all 10 parameters, so the schema already documents q/query aliasing, pagination, filters, and the include_* flags. The description only echoes the type enum values, adding little beyond what the schema provides; baseline 3 applies.

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 (full-text search across all paragraphs of the Urantia Papers), which is clear and concrete. However, it does not differentiate from the sibling search.semantic, leaving the agent to infer which search to pick.

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?

It explains the three modes and marks 'and' as the default, which is implied usage guidance for mode selection. But there is no when-to-use vs when-not guidance, and notably no routing advice against the sibling search.semantic tool.

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.