Skip to main content
Glama

Search book series

search_series
Read-onlyIdempotent

Find book series by name. Returns up to 5 matches, each linking to its reading-order page.

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": {
      "query": "<query>"
    },
    "name": "search_series"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYes3 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

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and a closed-world scope, so safety is covered. The description adds genuinely behavioral information beyond that: a hard cap of 5 matches (meaning results can be truncated and a broader query may be needed) and the fact that each hit links to a reading-order page, which points at the follow-up tool.

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, both earning their place: the first states purpose, the second states result cardinality and shape. No filler, no restatement of the title.

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 search with an output schema and full annotations, this covers what an agent needs to call it correctly. The remaining gap is minor: no mention of empty-result behavior or whether the cap of 5 is a truncation the agent should retry against.

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 the single query parameter is fully constrained (3–200 chars, at least 3 alphanumerics), so the schema does the heavy lifting. The description adds nothing about matching semantics — substring vs. exact, case sensitivity, or what happens on zero results — so it sits at the baseline.

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 opens with a specific verb+resource combination, 'Find book series by name,' which is unambiguous. It does not, however, contrast itself with the sibling find_series_for_book, which is the reverse lookup (book → series) and the most likely confusion point.

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 'by name' — an agent can infer this is the right tool when it has a series title rather than a book title — but there is no explicit when-to-use statement, no exclusions, and no routing to find_series_for_book or get_reading_order.

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