Skip to main content
Glama

Get a series reading order

get_reading_order
Read-onlyIdempotent

Get the reading order of one book series, looked up by series name. Returns the best match only.

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": {
      "series": "<series>"
    },
    "name": "get_reading_order"
  }
}

Input Schema

NameRequiredDescriptionDefault
seriesYes3 to 200 characters, with at least 3 letters or digits.

Output Schema

NameRequiredDescriptionDefault
moreAtYesWhere to keep browsing on listofbooks.net.
resultsYesMatching catalog entries. Each links to its page.
withheldYesMatches left out because the daily limit of distinct pages was reached.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedOutput schema / properties / results / items / properties / books / items / properties / number
      Added value: +{
      +  "anyOf": [
      +    {
      +      "exclusiveMinimum": 0,
      +      "maximum": 9007199254740991,
      +      "type": "integer"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ]
      +}
    • addedOutput schema / properties / results / items / properties / books / items / properties / role
      Added value: +{
      +  "enum": [
      +    "core",
      +    "novella",
      +    "short_story",
      +    "side_story",
      +    "play",
      +    "draft",
      +    "collection",
      +    "companion"
      +  ],
      +  "type": "string"
      +}
    • changedOutput schema / properties / results / items / properties / books / items / required
      Previous value: -[
      -  "position",
      -  "title",
      -  "year"
      -]New value: +[
      +  "position",
      +  "number",
      +  "role",
      +  "title",
      +  "year"
      +]
  2. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and openWorldHint=false, so the safety profile is covered. The description adds the useful caveat that only the best match is returned, which sets expectations about result cardinality, but it says nothing about fuzzy matching behavior or failure modes on ambiguous names.

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?

Two short sentences, front-loaded with the action and followed by the result-cardinality caveat. No wasted wording, though it is minimal enough that a touch more routing detail could have been added without bloat.

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?

An output schema exists, so return values need no explanation, and the single parameter is fully documented. What remains missing is guidance on ambiguity and no-match cases, which matters for a tool that silently picks one best match.

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% and the single 'series' parameter is fully described in-schema (length bounds, alphanumeric requirement). The description's phrase 'looked up by series name' adds only modest framing beyond that, so the baseline 3 applies.

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?

Specific verb and resource: 'Get the reading order of one book series, looked up by series name.' An agent knows exactly what it retrieves and how it is keyed. It does not explicitly differentiate itself from siblings like get_author_series or search_series, which keeps it below a 5.

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?

The description implies usage via 'looked up by series name' and 'Returns the best match only,' which tells the agent this is a resolution-style lookup rather than a broad search. However, it never states when to prefer this over search_series or find_series_for_book, nor what to do when no match is found.

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