Skip to main content
Glama

Gutendex Search Books

gutendex_search_books
Read-onlyIdempotent

Search for books by title or author name. Returns book IDs, titles, authors, and download counts.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "Jane Austen"
    },
    "name": "gutendex_search_books"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesTitle or author name to search for.

Output Schema

NameRequiredDescriptionDefault
booksYesList of books matching the search query
countYesTotal number of books matching the search query

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is fully covered by structured data. The description's added behavioral value is limited to naming returned fields, with nothing said about result caps, pagination, or ranking behavior for a broad open-world search.

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 search action and followed by the return summary; nothing is padded. The return-field sentence is mildly redundant given an output schema exists, which keeps it from a top score.

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-only search with full schema coverage, rich annotations, and an output schema, the description covers what an agent needs to select and call it. The remaining gap is the absence of any routing hint toward the ID-based or browse siblings.

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 documented with examples, so the schema carries parameter meaning. The description's "by title or author name" merely restates that constraint without adding syntax, matching, or format detail.

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 states a specific verb and resource ("Search for books") and narrows the matching key to title or author name, which implicitly separates it from ID-based retrieval and topic/browse siblings. It never names an alternative tool, so the differentiation is inferable rather than explicit.

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 only implied: an agent can reason that this is the entry point when it has a free-text title or author rather than an ID. There is no statement of when not to use it, no mention of the sibling lookup tool, and no guidance on result limits or empty-result handling.

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.