Skip to main content
Glama

Urantia Papers

Full-Text Search

search.fulltext
Read-onlyIdempotent

Keyword search across all paragraphs of the Urantia Papers. Mode "auto" (default): a reference such as "68:6.3", "103:2", "Paper 68", or a bare number such as "68" (0 to 196) gives those paragraphs; otherwise the exact phrase first, then every word, then (when few) typo fixes and most of the words. Each result has match (reference, exact, all, near, most); meta.didYouMean gives the fixed query and meta.see names another work the query names. Other modes: "and" (all words), "or" (any word), "phrase" (exact phrase).

Input Schema

NameRequiredDescriptionDefault
qNoAlias for `query` (REST compatibility).
langNoLanguage to search. "es" searches the Spanish text (words match with or without accents; "documento 1" is a reference) and gives Spanish rows. Default "eng".eng
pageNoPage number (0-indexed)
typeNoSearch mode: auto, phrase, and, orauto
limitNoResults per page (1-100)
queryNoSearch query. Example: "nature of God"
part_idNoFilter to a specific part ID (1-4)
paper_idNoFilter to a specific paper ID
include_entitiesNoInclude entity mentions
include_bible_parallelsNoInclude the top-10 Bible verses semantically nearest to each result (Urantia → Bible).
include_urantia_parallelsNoInclude the top-10 most-similar OTHER Urantia paragraphs for each result.

Output Schema

NameRequiredDescriptionDefault
dataYes
metaYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / lang
      Added value: +{
      +  "default": "eng",
      +  "description": "Language to search. \"es\" searches the Spanish text (words match with or without accents; \"documento 1\" is a reference) and gives Spanish rows. Default \"eng\".",
      +  "enum": [
      +    "eng",
      +    "es"
      +  ],
      +  "type": "string"
      +}
  2. Changed2 schema fields changed
    • 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"
      +}
  3. Changed9 schema fields changed
    • addedInput schema / properties / q / maxLength
      Added value: +500
    • addedInput schema / properties / query / maxLength
      Added value: +500
    • changedInput schema / properties / type / default
      Previous value: -"and"New value: +"auto"
    • changedInput schema / properties / type / description
      Previous value: -"Search mode: phrase, and, or"New value: +"Search mode: auto, phrase, and, or"
    • changedInput schema / properties / type / enum
      Previous value: -[
      -  "phrase",
      -  "and",
      -  "or"
      -]New value: +[
      +  "auto",
      +  "phrase",
      +  "and",
      +  "or"
      +]
    • addedOutput schema / properties / data / items / properties / match
      Added value: +{
      +  "enum": [
      +    "reference",
      +    "exact",
      +    "all",
      +    "near",
      +    "most"
      +  ],
      +  "type": "string"
      +}
    • changedOutput schema / properties / data / items / required
      Previous value: -[
      -  "id",
      -  "standardReferenceId",
      -  "sortId",
      -  "paperId",
      -  "sectionId",
      -  "partId",
      -  "paperTitle",
      -  "sectionTitle",
      -  "paragraphId",
      -  "text",
      -  "labels",
      -  "rank"
      -]New value: +[
      +  "id",
      +  "standardReferenceId",
      +  "sortId",
      +  "paperId",
      +  "sectionId",
      +  "partId",
      +  "paperTitle",
      +  "sectionTitle",
      +  "paragraphId",
      +  "text",
      +  "labels",
      +  "rank",
      +  "match"
      +]
    • addedOutput schema / properties / meta / properties / didYouMean
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / properties / meta / properties / see
      Added value: +{
      +  "additionalProperties": false,
      +  "properties": {
      +    "title": {
      +      "type": "string"
      +    },
      +    "work": {
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "work",
      +    "title"
      +  ],
      +  "type": "object"
      +}
  4. Changed4 schema fields changed
    • 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"
      +]
  5. Changed4 schema fields changed
    • 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"
      +}
  6. First observed

TDQS

A4/5.0
Behavior5/5

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

Annotations already cover readOnly/idempotent/non-destructive, yet the description still discloses substantive behavior: the auto-mode fallback ladder (reference → exact phrase → every word → typo fixes → most words) and the set of possible `match` values plus `meta.didYouMean` and `meta.see` signals. That tells an agent how aggressively results were relaxed and how to interpret a partial match.

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?

Purpose is front-loaded in the first clause, followed by mode semantics in a compact two-sentence block; nothing is filler. It is dense with inline code identifiers and quoted examples, which slows scanning slightly for an 11-parameter tool.

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, the description need not enumerate return values, and it covers the hardest part (mode semantics and match relaxation). It is silent on the include_* enrichment flags and the part_id/paper_id filters, but those are self-documenting in the schema and not essential to correct invocation.

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 coverage is 100%, so the baseline is 3; the description earns more by explaining what `type: auto` actually resolves to and by showing that the query accepts structured references ("68:6.3", "103:2", "Paper 68", bare "68") alongside free text. The schema's own mode description is just a bare enum list, so this adds real meaning.

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 all paragraphs of the Urantia Papers"), which implicitly separates it from the sibling search.semantic tool. It never names the sibling explicitly, so the keyword-vs-semantic distinction is left 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 description gives strong guidance on how to pick a mode (auto/and/or/phrase) and what auto does, but says nothing about when to use this tool rather than search.semantic or works.search. Usage relative to alternatives is only implied by the word "keyword".

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.