Skip to main content
Glama
srgsanky

Personal Library MCP Server

by srgsanky

delete_book

Remove books from your personal library by ISBN to manage your reading list and keep your collection current.

Instructions

Removes a book from the library.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
isbnYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • Implementation of the 'delete_book' tool which removes a book record from the database.
    @mcp.tool()
    def delete_book(isbn: str) -> str:
        """Removes a book from the library."""
        conn = get_db_connection()
        cursor = conn.cursor()
        cursor.execute("DELETE FROM books WHERE isbn = ?", (isbn,))
        conn.commit()
        changes = conn.total_changes
        conn.close()
        
        if changes > 0:
            return f"Success: Book {isbn} deleted."
        return f"Error: No book found with ISBN {isbn}."
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 action is destructive ('Removes'), but lacks details on permissions needed, whether deletion is permanent or reversible, error handling, or rate limits. This is inadequate for a mutation tool with zero annotation coverage.

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's front-loaded with the core action, making it easy to scan and understand 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 complexity (a destructive operation with no annotations) and the presence of an output schema (which reduces the need to describe return values), the description is minimally adequate. However, it lacks critical details like behavioral traits and parameter context, making it incomplete for safe and effective use.

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 schema description coverage is 0%, so the description must compensate. It doesn't mention the 'isbn' parameter at all, failing to add meaning beyond the schema. However, with only one parameter, the baseline is higher, but the description doesn't explain what the ISBN is or how it's used, leaving a 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 ('Removes') and resource ('a book from the library'), making the purpose unambiguous. However, it doesn't explicitly differentiate from sibling tools like 'update_book_status' which might also affect book availability, missing full sibling distinction.

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 guidance is provided on when to use this tool versus alternatives. For example, it doesn't mention prerequisites (e.g., the book must exist), when not to use it (e.g., for temporary removal), or refer to siblings like 'update_book_status' for non-destructive changes.

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