Skip to main content
Glama
Sign In
hardcover-mcp

hardcover-mcp

by kristianedlund
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

search_books

Read-only

Full-text search across Hardcover's catalog by title, author, ISBN, or keyword; set query_type to search authors, series, lists, users, publishers, characters, or prompts instead of books. Read-only.

Instructions

Full-text search across Hardcover's catalog by title, author, ISBN, or keyword; set query_type to search authors, series, lists, users, publishers, characters, or prompts instead of books. Read-only. Returns {total, returned, page, } (e.g. 'books', 'authors') with compact hits (book hits: book_id, title, authors, series; others: id, name, slug, plus type-specific fields) ranked by relevance unless 'sort' is given. Use it to discover ids, then call get_book, get_author, get_series, etc. for full details. If you already have an id, slug, or ISBN, call the matching get_* tool directly.

Input Schema

NameRequiredDescriptionDefault
pageNoPage number (default 1).
sortNoTypesense sort expression, e.g. 'rating:desc' or 'users_count:desc' for most popular first.
queryYesSearch query (title, author name, ISBN, etc.).
per_pageNoResults per page (default 10, max 25).
filter_byNoTypesense filter expression, e.g. 'release_year:>2020' or 'release_year:[2020..2024]'.
query_typeNoEntity type to search (default: 'Book').

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.7.1
    • addedInput schema / properties / filter_by
      Added value: +{
+  "description": "Typesense filter expression, e.g. 'release_year:>2020' or 'release_year:[2020..2024]'.",
+  "type": "string"
+}
    • addedInput schema / properties / sort
      Added value: +{
+  "description": "Typesense sort expression, e.g. 'rating:desc' or 'users_count:desc' for most popular first.",
+  "type": "string"
+}
  2. First observedv0.4.0

TDQS

A4.7/5.0
Behavior4/5

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

Annotations cover readOnlyHint and openWorldHint, and the description's 'Read-only' only restates them. However it adds real behavioral context beyond annotations: the default relevance ranking, the effect of supplying 'sort', paging behavior via {total, returned, page}, and the compact hit shape per entity type. It stops short of describing rate limits or errors, so a 4 rather than 5.

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?

A single dense paragraph with the core purpose front-loaded, followed by entity-type scope, return shape, and a routing rule. Every sentence carries distinct information and nothing is padded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, and the description compensates by specifying the return envelope ({total, returned, page, <type>}) and the per-hit fields. For a 6-parameter read-only search tool, an agent has everything needed to call it and interpret results.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is 3. The description adds meaning on top: it explains that query_type selects alternate entity types rather than books, and that results are relevance-ranked unless 'sort' is provided. It doesn't clarify filter_by/per_page interactions, so not a 5.

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 specific verb ('full-text search') and resource ('Hardcover's catalog'), plus the searchable fields (title, author, ISBN, keyword) and the query_type expansion to other entities. It is clearly distinguishable from the get_* siblings it names.

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

Usage Guidelines5/5

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

Explicitly says to use it to discover ids and then call get_book/get_author/etc., and gives a concrete exclusion: if you already have an id, slug, or ISBN, call the matching get_* tool directly. This is textbook when/when-not/alternative guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools