Skip to main content
Glama

library_full_dataset

The whole Law of One library in one JSON: all 7 collections, 356 concepts, 738 glossary terms, 130 journeys (licence included). Price: $5.00 USDC per call (x402).

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": "library_full_dataset"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoLanguage of the core texts (default it)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose two behavioral facts an agent would otherwise miss: the call costs $5.00 USDC via x402 and the licence is included. It also gives the payload's scope via concrete counts. It stops short of describing response shape beyond 'one JSON' or what happens if payment fails.

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?

A single sentence that front-loads the payload scope, then the concrete counts, then the licence and price. Every clause carries information an agent needs before invoking a paid bulk export; nothing is redundant.

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 no-parameter bulk export with no output schema, the description adequately covers contents, licence and cost. The main residual gap is return format detail (size, structure, error/payment-failure behavior), but contents and pricing — the decision-critical facts — are present.

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?

There is one optional parameter (lang) with 100% schema description coverage and an enum, so the schema already fully documents it. The description adds no meaning about language selection or its default, leaving it at the baseline for high coverage.

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 action and resource: returns the entire Law of One library as a single JSON payload, enumerated as 7 collections, 356 concepts, 738 glossary terms and 130 journeys. This clearly distinguishes it from per-entity siblings such as library_collection_dataset and library_concepts, though it never names those alternatives directly.

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 only implied: 'the whole library in one JSON' tells an agent this is the bulk-fetch option, and the explicit price hints that it is the expensive path versus smaller siblings. There is no explicit statement of when to prefer this over library_collection_dataset or the individual lookup tools.

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.

Resources