Skip to main content
Glama

library_search

Search all Law of One collections (accent-insensitive, word stems); ranked results with snippets. Price: $0.005 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": {
      "q": "<q>"
    },
    "name": "library_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYesWords to search (Italian)
langNoLanguage of the core texts (default it)
limitNo
collectionNoOptional, comma-separated: the-answer, lumen, adeptus, arcana, octava, somnia, viridis

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations provided, the description usefully discloses that search is accent-insensitive, uses word stems, returns ranked results with snippets, and costs $0.005 USDC per call. It still omits details like pagination behavior, default limit effects, or which fields are searched.

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?

The description is two compact sentences with the search scope and behavior front-loaded. The price sentence is also relevant and clearly separated, with no wasted wording.

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 four-parameter search tool with no output schema, the description covers the important behavioral traits, return shape, and pricing. It is slightly incomplete on sibling routing and limit semantics, but sufficient to call the tool correctly.

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 75%, and the schema already explains q, lang, and collection. The description adds little parameter-specific meaning beyond implying that search spans all collections, and it does not clarify the limit parameter.

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?

The description states a specific verb and resource: searching all Law of One collections, with ranking and snippets. It is clear what the tool does, but it does not explicitly distinguish itself from sibling search or collection tools.

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 explicit guidance on when to use this tool versus alternatives such as catalog_search, library_concepts, or library_collections. The search purpose is implied, but there are no exclusions or routing cues for choosing collection or language parameters.

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