Skip to main content
Glama
srgsanky

Personal Library MCP Server

by srgsanky

search_books

Search for books by title or ISBN to find and manage reading materials in your personal library database.

Instructions

Searches for books by name or ISBN.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The `search_books` tool handler implements a database search functionality using SQL 'LIKE' queries on both the book 'name' and 'isbn' columns. It is decorated with `@mcp.tool()` which handles the registration with the MCP framework.
    @mcp.tool()
    def search_books(query: str) -> str:
        """Searches for books by name or ISBN."""
        conn = get_db_connection()
        cursor = conn.cursor()
        cursor.execute("SELECT isbn, name FROM books WHERE name LIKE ? OR isbn LIKE ?", (f"%{query}%", f"%{query}%"))
        results = [dict(row) for row in cursor.fetchall()]
        conn.close()
        
        if results:
            return json.dumps(results, indent=2)
        return "No matches found."
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the search functionality but omits critical details such as whether this is a read-only operation, how results are returned (e.g., pagination, sorting), error handling, or performance characteristics. This leaves significant gaps in understanding the tool's behavior.

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?

The description is a single, efficient sentence with no wasted words. It front-loads the core functionality ('Searches for books') and adds necessary detail ('by name or ISBN') without redundancy, making it easy to parse quickly.

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?

Given the tool's moderate complexity (a search function with one parameter) and the presence of an output schema (which likely covers return values), the description is minimally adequate. However, with no annotations and incomplete parameter guidance, it lacks sufficient context for optimal agent use, such as error conditions or search scope limitations.

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?

The input schema has 0% description coverage, but the description adds meaning by specifying that the 'query' parameter searches 'by name or ISBN'. This clarifies the parameter's purpose beyond the schema's basic type definition. However, it doesn't detail syntax, format constraints, or examples, so it only partially compensates for the schema gap.

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 clearly states the action ('Searches for') and resource ('books'), and specifies the search criteria ('by name or ISBN'). It distinguishes from siblings like 'list_books' by implying a query-based search rather than listing all books. However, it doesn't explicitly contrast with 'add_book' or 'delete_book', keeping it at a 4 rather than a 5.

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?

The description provides no guidance on when to use this tool versus alternatives like 'list_books' (for browsing all books) or other siblings. It lacks explicit instructions on use cases, prerequisites, or exclusions, leaving the agent to infer usage from the tool name and context alone.

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

Install Server

Other Tools

Latest Blog Posts

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/srgsanky/mcp-demo'

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