PyScrappy

Overview Schema Related Servers Score Discussions

search_books

Find books by title, author, or keywords via Open Library. Get matching records with authors, publication year, edition count, and work key.

Instructions

Search books by title, author, or free text via the Open Library search API and return a list of matching book records.

Queries Open Library over the network (no browser or authentication required). Returns a list of dicts, each typically containing: title (str), author_names (list of str), first_publish_year (int or None), edition_count (int), and the Open Library work key (str, e.g. "/works/OL45804W"). Fields missing upstream are omitted or None. Returns an empty list when the query matches nothing. Read-only: no local files or state are modified.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`query`	Yes	Title, author, or free-text search string. Type: string. Example: "the hobbit tolkien". Required, no default.
`max_results`	No	Maximum number of books to return. Type: integer. Example: 10. Default: 20. Allowed: any positive integer.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`data`	No
`count`	No
`errors`	No
`scraper`	No
`source_urls`	No

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed2 schema fields changedJul 31, 2026

changedInput schema / properties / max_results / description

Previous value: -"Max books to return (default 20)."New value: +"Maximum number of books to return. Type: integer. Example: 10. Default: 20. Allowed: any positive integer."

changedInput schema / properties / query / description

Previous value: -"Title, author, or free-text search."New value: +"Title, author, or free-text search string. Type: string. Example: \"the hobbit tolkien\". Required, no default."

Changed18 schema fields changedv1.3.3Jul 31, 2026

addedInput schema / additionalProperties
```
Added value: +false
```
addedInput schema / properties / max_results / description
```
Added value: +"Max books to return (default 20)."
```
removedInput schema / properties / max_results / title
```
Removed value: -"Max Results"
```

addedInput schema / properties / query / description

Added value: +"Title, author, or free-text search."

removedInput schema / properties / query / title
```
Removed value: -"Query"
```
removedInput schema / title
```
Removed value: -"search_booksArguments"
```

removedOutput schema / $defs

Removed value: -{
-  "ToolError": {
-    "description": "A non-fatal problem encountered while scraping.",
-    "properties": {
-      "message": {
-        "title": "Message",
-        "type": "string"
-      },
-      "url": {
-        "title": "Url",
-        "type": "string"
-      }
-    },
-    "required": [
-      "url",
-      "message"
-    ],
-    "title": "ToolError",
-    "type": "object"
-  }
-}

removedOutput schema / properties / count / title
```
Removed value: -"Count"
```
removedOutput schema / properties / data / title
```
Removed value: -"Data"
```
removedOutput schema / properties / errors / items / $ref
```
Removed value: -"#/$defs/ToolError"
```

addedOutput schema / properties / errors / items / description

Added value: +"A non-fatal problem encountered while scraping."

addedOutput schema / properties / errors / items / properties

Added value: +{
+  "message": {
+    "type": "string"
+  },
+  "url": {
+    "type": "string"
+  }
+}

addedOutput schema / properties / errors / items / required
```
Added value: +[
+  "url",
+  "message"
+]
```
addedOutput schema / properties / errors / items / type
```
Added value: +"object"
```
removedOutput schema / properties / errors / title
```
Removed value: -"Errors"
```
removedOutput schema / properties / scraper / title
```
Removed value: -"Scraper"
```
removedOutput schema / properties / source_urls / title
```
Removed value: -"Source Urls"
```
removedOutput schema / title
```
Removed value: -"ScrapeToolResult"
```

AddedJul 26, 2026

TDQS

A4.5/5.0

Behavior5/5

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

With no annotations, the description carries full burden. It discloses read-only behavior, no file/state modification, network access, return format, and empty-list behavior. This is excellent transparency.

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?

Concise and front-loaded. The first sentence captures purpose, subsequent sentences add valuable behavioral details without redundancy. Every sentence earns its place.

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?

Covers purpose, network/auth requirements, return shape, empty results, and side effects. Output schema exists, but the description enriches context further. Complete for a 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%, fully explaining query and max_results. The description adds no new param semantics beyond aligning with the search scope. Baseline 3 is appropriate.

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?

The description clearly states the tool searches books by title, author, or free text via the Open Library API, with a specific verb and resource. This distinguishes it from sibling search/scrape tools.

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

Usage Guidelines4/5

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

It provides clear context: network-based, no authentication required. It does not explicitly exclude alternatives, but the book-specific scope implies when to use. No explicit when-not or alternative tool references.

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

Latest Blog Posts

Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)
By Om-Shree-0709 on July 25, 2026.
mcp
Agent Identity
OAuth 2.1
Your AI Chatbot Just Exposed Your CEO's Salary to an Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/mldsveda/PyScrappy'

If you have feedback or need assistance with the MCP directory API, please join our Discord server