Skip to main content
Glama
Sign In

Urantia Papers

by dev.urantia
OverviewDiscussionsAdmin

Get Paper Sections

papers.sections
Read-onlyIdempotent

Get all sections within a paper, ordered by section number. Useful for understanding paper structure before reading specific sections.

Input Schema

NameRequiredDescriptionDefault
langNoLanguage of the text and titles. "es" gives the Spanish translation (an AI translation, CC0); each paragraph then has `language` and a `translation` label. Default "eng".eng
paper_idYesPaper ID (0-196). Example: '1'

Output Schema

NameRequiredDescriptionDefault
sectionsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / lang / description
      Previous value: -"Language of the text and titles. \"es\" gives the Spanish translation (a machine translation, CC0); each paragraph then has `language` and a `translation` label. Default \"eng\"."New value: +"Language of the text and titles. \"es\" gives the Spanish translation (an AI translation, CC0); each paragraph then has `language` and a `translation` label. Default \"eng\"."
  2. Changed1 schema field changed
    • addedInput schema / properties / lang
      Added value: +{
+  "default": "eng",
+  "description": "Language of the text and titles. \"es\" gives the Spanish translation (a machine translation, CC0); each paragraph then has `language` and a `translation` label. Default \"eng\".",
+  "enum": [
+    "eng",
+    "es"
+  ],
+  "type": "string"
+}
  3. First observed

TDQS

A3.8/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 one genuine behavioral fact beyond that — results come back sorted by section number — but reveals nothing about scope limits or whether content is included.

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 short sentences, zero filler, with the core retrieval behavior front-loaded and the rationale second. Every clause earns its place.

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 and full parameter documentation, the description need not explain return shapes; annotations carry the safety profile. The only ambiguity is whether 'all sections' means section listings/metadata or full section bodies, which would help an agent choose between this and paragraphs.get.

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%, with paper_id's format/example and lang's enum semantics fully documented in the schema itself. The description adds no parameter-level meaning (e.g. how lang affects section titles), 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 sections within a paper') plus a scope qualifier ('ordered by section number'). It is clearly distinguishable from papers.get and paragraphs.get by name and content, but it does not explicitly name or contrast with any sibling.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'Useful for understanding paper structure before reading specific sections' gives a concrete workflow context for when to reach for this tool. It stops short of naming the alternative tool (e.g. paragraphs.get) for reading actual section content, so no exclusions are 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 toolsInspect
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.

Resources