Skip to main content
Glama
Sign In
iranketab-mcp

iranketab-mcp

by sepehr071
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Book details

ik_book
Read-onlyIdempotent

Retrieve a book's title, authors, categories, introduction, review count, and a short list of editions with ratings, prices, and stock to compare translations and publishers.

Instructions

Read one book (a work): title, authors, categories, introduction, review count and a short list of every edition.

Editions are the translations/publishers of the work, each with rating, votes, price, stock. Use ik_editions to compare them in full.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "book": "<book>"
    },
    "name": "ik_book"
  }
}

Input Schema

NameRequiredDescriptionDefault
bookYesBook id (e.g. 858) or iranketab.ir/book/ URL.
summary_charsNoIntroduction length (0 = none).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so safety need not be restated. The description adds genuinely new behavior: the edition list is deliberately short, and full edition detail lives in another tool. It stops short of stating error behavior for bad ids or the cost of the introduction text.

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?

Two short sentences, front-loaded with the return payload and followed by the domain gloss on 'editions' plus the routing pointer. Every clause carries information; nothing restates the title or the annotations.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description does the work of describing the response shape field by field, and it flags that editions are summarized rather than complete. Missing only edge-case behavior (invalid id, empty results) for full completeness on a read 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 coverage is 100%, so both the id/URL form and summary_chars (default 800, max 4000) are already documented in the schema. The description only implies that 'introduction' is the affected field and adds no format or truncation detail beyond the schema, so baseline 3 applies.

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?

States a specific verb and resource ('Read one book (a work)') and enumerates the returned fields (title, authors, categories, introduction, review count, edition list), which lets an agent distinguish it from ik_search and ik_reviews without opening the schema.

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?

Explicitly routes the edition-comparison case to ik_editions ('Use ik_editions to compare them in full'), giving a clear when-to-use-elsewhere rule. It does not mention other near neighbors such as ik_book_extras or ik_reviews, so the routing coverage is partial rather than exhaustive.

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