Skip to main content
Glama

Find the series a book belongs to

find_series_for_book
Read-onlyIdempotent

Given a book's title and author, return the series it belongs to, its position, and the series order.

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

Input Schema

NameRequiredDescriptionDefault
titleYes1 to 200 characters, with at least one letter or digit.
authorYes1 to 200 characters, with at least one letter or digit.

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",
      -  "isCurrent"
      -]New value: +[
      +  "position",
      +  "number",
      +  "role",
      +  "title",
      +  "year",
      +  "isCurrent"
      +]
  2. First observed

TDQS

B3.4/5.0
Behavior3/5

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

The annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, so the safety profile needs no repeating, and the description does not contradict them. It adds only the returned fields, which the output schema already carries, and says nothing about behavior when no series is found or when the title/author match is ambiguous.

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?

One front-loaded sentence with zero filler, and the input condition precedes the return list. It is efficient, though so terse that it leaves potential clarifications unstated.

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 two-parameter read tool with a documented schema and an output schema, so the return format need not be re-explained. The main remaining gap is the no-match or ambiguous-match case, which matters for a title/author lookup but is unaddressed.

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% for both parameters, including length and character constraints, so the schema does the heavy lifting. The description only restates that a title and an author are required, adding no disambiguation advice such as how to handle subtitles or co-authors.

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 gives a concrete verb-plus-resource: given a title and author, it returns the series, the book's position in it, and the series order. That is specific enough to distinguish lookup-by-book from siblings like get_author_series or search_series, although no sibling is named explicitly.

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?

Usage is implied by the input pair ('given a book's title and author'), so an agent can infer it applies when a specific book is known. There is no explicit when-not guidance pointing at get_author_series for author-level browsing or search_series for fuzzy lookups, leaving the agent to work out the routing.

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