Skip to main content
Glama

library_journeys

Guided reading journeys of a collection, each answering one question (free). Free.

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

Input Schema

NameRequiredDescriptionDefault
colYesCollection id
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?

No annotations exist, so the description carries the full burden. It states that the journeys are free, but does not disclose whether this returns a list, whether results are paginated, how many journeys a collection typically has, or whether any auth/quota applies. For a zero-annotation tool this is thin behavioral coverage, with the cost note restated rather than expanded.

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 short, but the '(free). Free.' duplication wastes a third of the text, and the single sentence is not front-loaded with a clear action. Nothing here is padded beyond that, but the redundancy signals low editorial care.

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?

This is a simple read operation with two fully enumerated parameters and no output schema, so the bar is modest. Still, an agent cannot tell whether the response is a list of journeys, a single journey index, or narrative content, and the absence of annotations leaves safety and cost behavior only partly described.

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 both parameters have enum values with their own descriptions ('Collection id', 'Language of the core texts (default it)'), so the schema does the work. The description only implies the collection parameter via 'of a collection' and says nothing about the language option or what the seven collection ids represent. Baseline 3 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 phrase 'guided reading journeys of a collection' identifies the resource and its scoping, but there is no verb (list? fetch? generate?) and no differentiation from the sibling 'library_journey' singular, which an agent cannot distinguish from this tool by name alone. 'Each answering one question' hints at content shape but not at what the call returns.

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 when-to-use guidance, no prerequisites, and no mention of when to prefer 'library_journey' or 'library_collections' instead. The only conditional signal offered is '(free)', which speaks to cost rather than to usage selection.

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