Skip to main content
Glama

Urantia Papers

List Papers

papers.list
Read-onlyIdempotent

List all 197 papers of the Urantia Papers with their metadata (id, title, partId, labels), as a flat list.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "papers.list"
  }
}

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

Output Schema

NameRequiredDescriptionDefault
papersYes

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 readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is fully covered. The description adds that the result is a flat, complete set of 197 items with metadata only (no paragraph text), which is useful context, but it says nothing about how the lang parameter changes titles/labels or about ordering/pagination.

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?

One sentence, front-loaded with the action and scope, with the returned fields enumerated inline. No filler or restatement of the title.

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?

For a single-optional-parameter read tool with an output schema, the description covers scope, count, and returned fields adequately. The only small gap is not noting that lang switches titles/paragraph labels, which the schema does cover.

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% and the single lang parameter's enum is thoroughly documented in the schema, including the Spanish translation caveat. The description does not mention lang at all, so it adds nothing beyond the schema; baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (List) and resource (all 197 papers of the Urantia Papers), and enumerates the returned metadata (id, title, partId, labels). The phrase 'as a flat list' implicitly contrasts with the hierarchical papers.sections and the single-item papers.get, so an agent can distinguish it without opening the schema.

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?

Usage is implied — use it to enumerate the paper index — but there is no explicit statement of when to prefer it over papers.get, papers.sections, toc.get, or search.fulltext. No prerequisites or exclusions are given.

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.