iranketab-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_booksA | Search iranketab.ir for books by title, author or keyword (Persian or English). Returns works with their author line and the edition ids the search matched. Search cards carry no price - call book_details for prices, translators and stock. The site caps search at 100 hits. |
| find_author_publisher_or_tagA | Resolve a name to its iranketab id: kind=person for authors AND translators, kind=publisher for publishers, kind=tag for categories/genres (e.g. |
| book_detailsA | Everything about one book (work): description, highlights, categories, a vote-weighted rating across all editions, and an editions summary - how many translations/publishers exist, how many are buyable, the cheapest available and the most-rated edition - plus a compact list of editions. Use book_editions for full per-edition data and filters. |
| book_editionsA | All editions of one book with full data per edition: translators and publisher (with ids), price and discount in Toman, stock state, earliest delivery, rating, ISBN, format (قطع), cover (نوع جلد), pages, publication year and print run (سری چاپ - a high number means a long-lived, popular edition). Answers 'which translation is best / cheapest / available?'. |
| book_commentsA | Reader comments on a book, newest first, 20 per page. Each comment names the edition (publisher) it was left on, so opinions about a specific translation can be told apart. Pass edition_id to keep only comments on that edition (filters the fetched page). |
| similar_booksA | Books iranketab recommends alongside a given book (its own 'related' shelf). |
| browse_tagA | Books in one iranketab category/genre/list (e.g. 152 = Russian literature, 328 = bestsellers). Tag ids come from book_details tags or find_author_publisher_or_tag. Entries are editions with price in Toman and discount. |
| person_booksA | Every edition an author wrote OR a translator translated (iranketab keeps both as one profile). Entries are editions with price in Toman and discount. |
| publisher_booksA | The catalogue of one publisher (انتشارات). Entries are editions with price in Toman and discount. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 9 tools
Each tool targets a distinct entity or action: search, name resolution, book-level details, edition-level data, comments, related books, and tag/person/publisher listings. The only potentially adjacent pair is book_details and book_editions, but their descriptions clearly separate summary-level from per-edition data.
Names are uniformly lowercase snake_case and mostly resource-focused (book_details, book_editions, person_books, publisher_books). A few action-led names like search_books, browse_tag, and find_author_publisher_or_tag break the strict noun-first pattern, but the inconsistency is minor and does not hurt readability.
Nine tools is an appropriate size for a bookstore catalogue server: search, discovery, and entity-specific lookups are each represented without redundant clutter. It stays comfortably within the ideal 3-15 tool range.
The tool surface covers the main discovery workflow: search and tag/person/publisher browsing, book-level details, edition comparison, and comments. Minor gaps exist, such as no search pagination, no direct list of all tags, and no separate author/publisher profile info, but agents can work around them.