Skip to main content
Glama

library_collections

The 7 Law of One collections (The Answer encyclopedia and its themed apps) with counts (free). Free.

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_collections"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoLanguage of the core texts (default it)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.6/5.0
Behavior2/5

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

With no annotations, the description carries the full burden. It hints that results include counts and are 'free' (repeated as a fragment), but does not explain what a collection contains, what the counts count, or how access works beyond the vague 'free'.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is very short, but the trailing '(free). Free.' is redundant and reads as fragments rather than a front-loaded purpose statement. Brevity here comes at the cost of clarity rather than from efficiency.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple, one-optional-parameter listing tool with no output schema, the description is minimally adequate but leaves the term 'collections' and the returned counts unexplained. It does not fully leverage the space available to disambiguate from sibling tools.

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 a single optional 'lang' parameter with full enum and description coverage in the schema. The description adds nothing about the language parameter, so the baseline of 3 for high schema coverage applies.

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

Purpose3/5

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

The description names the resource ('The 7 Law of One collections') and mentions it returns counts, but the verb is implicit and the parenthetical ('The Answer encyclopedia and its themed apps') is ambiguous about whether those are the collections themselves or examples. It does not clearly differentiate the tool from siblings like library_collection_dataset or library_full_dataset.

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?

There is no guidance on when to use this tool versus the many library_* siblings (collection_dataset, full_dataset, concepts, glossary, journeys). An agent can only infer that this is a list/overview call; no exclusions or conditions are stated.

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