Skip to main content
Glama
Sign In
iranketab-mcp

iranketab-mcp

by sepehr071
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Book extras

ik_book_extras
Read-onlyIdempotent

Retrieve a book's awards, series, praise quotes, excerpts, author bio, related books, and articles using its Iranketab ID or URL.

Instructions

Read what else a book page offers: awards, series, praise quotes, excerpts, author bio, related books and articles.

For prizes, series, critics, "what next". Award and series ids work in ik_browse; article slugs in ik_article.

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_extras"
  }
}

Input Schema

NameRequiredDescriptionDefault
bookYesBook id (e.g. 858) or iranketab.ir/book/ URL.
bio_charsNoAuthor bio length (0 = none).
excerpt_charsNoCut each excerpt at this length.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. Beyond that, the description only enumerates section names, saying nothing about how absent sections are represented or how the sections are structured — useful behavior it could disclose since no output schema exists, but the section list does give partial payload expectations.

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 with no filler; the payload contents come first and the cross-tool routing second. Every phrase in the description earns its place.

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?

For a read-only, fully documented three-parameter tool with no output schema, listing the returned sections is the essential completion and it is done well. The remaining gap is behavioral: no statement on response shape when some extras are missing, or whether it is expensive/slow for a full extras pull.

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%, including the accepted book id/URL forms and the truncation semantics of bio_chars and excerpt_chars, so the schema carries the parameter burden. The description adds only indirect value by revealing that returned award/series ids can feed ik_browse and article slugs ik_article, which is about outputs rather than input meaning.

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?

A specific verb ('Read') plus an explicit enumeration of exactly what the tool returns: awards, series, praise quotes, excerpts, author bio, related books and articles. This clearly separates it from ik_book (core book data) and from ik_reviews or ik_articles, so an agent can identify it 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?

The second sentence gives the trigger contexts ('For prizes, series, critics, "what next"') and routes follow-up work precisely: award/series ids go to ik_browse, article slugs to ik_article. There is no explicit when-not-use statement or note that it should be called after ik_book, so it stops short of a 5.

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