Skip to main content
Glama
kristianedlund

hardcover-mcp

by kristianedlund
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

search_books

Search Hardcover by title, author, ISBN, or query to find books, authors, series, lists, and users. Refine with filters and sorting.

Instructions

Search Hardcover by title, author, or ISBN. Supports multiple entity types: books (default), authors, series, lists, users, publishers, characters, and prompts.

Input Schema

TableJSON 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

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden, and it discloses little: no return format, no pagination behavior (page/per_page live only in the schema), no ranking or rate-limit notes. The one behavioral claim, multi-entity support, largely repeats the enum already present in the schema.

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 tight sentences with the core capability front-loaded and the entity-type scope second. Nothing is padded or redundant, though the second sentence is essentially a summary of the query_type enum.

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?

With no annotations and no output schema, the description should do more to explain what a search returns and how results differ per entity type. Parameter documentation is covered by the schema, but the absence of any behavioral or result-shape context leaves a moderate gap for a 6-parameter search tool.

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%, so the schema already documents query, page, per_page, sort, filter_by, and the query_type enum. The description only restates the query target (title/author/ISBN) and the entity types, adding no syntax or format detail beyond the schema, so the baseline of 3 applies.

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?

States a specific verb and resource with scope: searching Hardcover by title, author, or ISBN. It also names the supported entity types, so the agent can distinguish a free-text search from the get_* siblings that fetch a single entity. It stops short of explicitly contrasting itself with those getters.

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

Usage Guidelines2/5

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

No when-to-use or when-not-to-use guidance is given. It never says to prefer this over get_book/get_author when you have an ID rather than a query string, nor does it mention any prerequisites. The entity-type list hints at scope but is not framed as usage advice.

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