Skip to main content
Glama

List an author's series

get_author_series
Read-onlyIdempotent

Given an author name, return the best-matching author and the titles of the book series they wrote (up to 25). Use get_reading_order with a title for its books.

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": {
      "author": "<author>"
    },
    "name": "get_author_series"
  }
}

Input Schema

NameRequiredDescriptionDefault
authorYes3 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. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnly=true, idempotent=true, and closed-world, so the safety profile is fully covered. The description adds one useful behavioral fact beyond them — results are truncated to 25 series and the author match is best-effort rather than exact. It does not discuss what happens when nothing matches or how the cap is signalled.

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?

Two sentences, zero filler: the first states the operation, the output, and its cap; the second routes to the follow-up tool. Front-loaded and easy to scan.

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 one-parameter read tool with an output schema and full annotation coverage, this is nearly complete — the cap of 25 and the follow-up path are both stated. A brief note on no-match behavior would close the remaining gap, but nothing essential is missing.

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 'author' parameter's length and content constraints are fully documented there. The description contributes only the semantic nuance that the value is matched fuzzily against known authors ('best-matching'), which is a modest addition over the schema baseline.

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

Purpose5/5

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

States a concrete verb and resource: given an author name, return the best-matching author plus the titles of series they wrote, capped at 25. The fuzzy 'best-matching' framing and the series focus distinguish it from search_authors and search_series without needing to open any schema.

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

Usage Guidelines4/5

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

Provides clear entry conditions (you have an author name) and an explicit next step: 'Use get_reading_order with a title for its books.' It does not, however, say when to prefer this over search_authors or search_series, so the alternative-selection guidance is only partial.

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