Skip to main content
Glama

library_collection_dataset

Full dataset of one Law of One collection (JSON): all concepts with deep dives, subtopics, links, glossary and journeys (licence included). Price: $1.50 USDC per call (x402).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "col": "<col>"
    },
    "name": "library_collection_dataset"
  }
}

Input Schema

NameRequiredDescriptionDefault
colYesCollection id
langNoLanguage of the core texts (default it)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden; it does disclose two valuable non-obvious traits: the payload is JSON, and the call costs $1.50 USDC via x402. It does not state whether the response is paginated, how large it is, whether billing is charged on failure, or whether repeated calls are cached.

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?

A single dense sentence with the resource and payload listed first and the critical pricing/licence note appended. Slightly crammed by the parenthetical licence and price clause, but nothing is wasted and it is well front-loaded.

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 two-parameter read that returns a large fixed JSON payload, the description adequately covers scope, contents, and the pay-per-call cost. Its main omission is comparative guidance against the granular library_* siblings and library_full_dataset, which matters given the price per call.

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 coverage is 100% with both parameters fully described and enumerated, so the schema already does the work. The description adds only that the dataset is scoped to 'one' collection and that core texts have a language, aligning with the col and lang params but adding no syntax or default detail beyond the schema.

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-like action (retrieves the full dataset) for a specific resource (one Law of One collection), and enumerates the payload contents: concepts with deep dives, subtopics, links, glossary, journeys, plus licence. This distinguishes it from granular siblings like library_concept or library_glossary, though it never explicitly names library_full_dataset as the all-collections alternative.

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

Usage Guidelines2/5

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

No explicit when-to-use or when-not-to-use guidance beyond the implicit signal that this is the whole-collection dump. It does not tell the agent to prefer library_concepts or library_search when only a few items are needed, nor does it differentiate itself from library_full_dataset across all collections.

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