Skip to main content
Glama

Urantia Papers

by dev.urantia

Full-Text Search

search.fulltext
Read-onlyIdempotent

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qNoAlias for `query` (REST compatibility).
pageNoPage number (0-indexed)
typeNoSearch mode: phrase, and, orand
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 (UB → Bible).
include_urantia_parallelsNoInclude the top-10 most-similar OTHER Urantia paragraphs for each result.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataYes
metaYes

TDQS

A3.9/5.0
Behavior4/5

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

Beyond the read-only annotations, the description explains the behavioral differences between 'and', 'or', and 'phrase' modes and states that results are ranked by relevance. This adds useful context about search semantics and result ordering.

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 with no fluff. The description leads with the tool's purpose, then covers modes and result ranking, earning every word.

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?

The description is complete for a search tool: scope, modes, and ranking are specified. Optional filters (part_id, paper_id, include_* flags) are documented in the schema, and the output schema exists, so the description does not need to repeat them. It does not mention pagination behavior, but the page and limit parameters cover that.

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?

The schema already documents all 10 parameters at 100% coverage. The description adds meaning by explicitly defining the 'type' parameter's modes ('and' = all words, 'or' = any word, 'phrase' = exact phrase), which the schema only labels as 'Search mode'. This extra semantic value elevates it above the baseline.

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?

The description clearly states the tool performs full-text search across all Urantia Book paragraphs and lists three search modes. It does not explicitly distinguish itself from sibling search.semantic, so it misses the top score.

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 implies keyword-based search with exact-phrase or word-matching semantics, which differentiates it from semantic search. However, it does not explicitly instruct when to use this tool versus alternatives like search.semantic.

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

All Urantia Papers toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.4/5.0
Disambiguation5/5

Each tool targets a distinct resource and action (e.g., audio.get vs bible.book vs entities.list). There is no overlap, and even similar tools like search.fulltext and search.semantic are clearly differentiated by mode.

Naming Consistency5/5

All tools follow a consistent 'domain.action' pattern using lowercase and dots. Underscores within domain names (e.g., urantia_parallels) are uniform. No mixing of camelCase or irregular verbs.

Tool Count5/5

19 tools is well-scoped for a server covering the Urantia Book and Bible integration. Each tool serves a distinct purpose without bloat or insufficiency.

Completeness5/5

The surface covers all core operations: browsing (list/get for papers, entities, paragraphs), searching (fulltext and semantic), structured navigation (toc.get, papers.sections), audio, and Bible parallels. No obvious gaps.

Resources