Urantia Papers

Get Entity Paragraphs

entities.paragraphs

Read-onlyIdempotent

Get all paragraphs that mention a specific entity, ordered by position in the text. Useful for studying everything said about a particular being, place, or concept.

Input Schema

Name	Required	Description
`page`	No	Page number (0-indexed)
`limit`	No	Results per page (1-100)
`entity_id`	Yes	Entity slug ID. Example: "god-the-father"

Output Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 23, 2026

addedOutput schema / properties / data / items / properties / language
```
Added value: +{
+  "type": "string"
+}
```

addedOutput schema / properties / data / items / properties / translation

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"
+}

Changed3 schema fields changedOct 3, 2026

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"
-]New value: +[
+  "id",
+  "standardReferenceId",
+  "sortId",
+  "paperId",
+  "sectionId",
+  "partId",
+  "paperTitle",
+  "sectionTitle",
+  "paragraphId",
+  "text",
+  "labels"
+]

Changed2 schema fields changedMay 8, 2026

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 readOnly, idempotent, non-destructive and closed-world, so the safety profile is fully covered. The description adds the useful ordering trait ('ordered by position in the text') but says nothing about pagination behavior or result volume, which matters for a tool returning 'all' paragraphs.

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?

Two sentences, zero waste, with the core operation and its ordering guarantee front-loaded. Nothing is repeated from the title or schema.

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, complete parameter descriptions, and rich annotations, the description only needs to convey the operation and ordering, which it does. Minor gap: it does not hint at result size or pagination expectations for a potentially large result set.

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%: entity_id slug format with an example, page and limit with defaults and bounds are all documented in the schema. The description adds no parameter detail beyond that, so the baseline of 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 and resource ('Get all paragraphs that mention a specific entity') plus the ordering guarantee, so the agent knows exactly what it retrieves. It stops short of naming how it differs from near siblings like paragraphs.context or paragraphs.get, leaving the distinction to inference.

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 'Useful for studying everything said about a particular being, place, or concept' implies a use case but gives no when-not conditions and names no alternative tool. An agent must guess whether to prefer this over paragraphs.context or search.fulltext.

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.