Skip to main content
Glama

Publisher books

ik_publisher_books
Read-onlyIdempotent

Fetch one publisher’s book list from Iranketab, best sellers first by default; search within the list, switch sort order, and paginate results.

Instructions

List the books of one publisher (انتشارات) on Iranketab, best sellers first by default.

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": {
      "publisher": "<publisher>"
    },
    "name": "ik_publisher_books"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo24 books per page (18 for publishers).
sortNonewest = site order.bestselling
termNoSearch inside the list.
publisherYesPublisher id from ik_search(kind='publisher') or an edition, or iranketab.ir/publisher/ URL.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and non-destructive behavior, so the safety profile is covered. The description adds one useful behavioral fact — default ordering is best sellers first — but says nothing about pagination limits, total result counts, or empty-result 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?

One sentence, front-loaded with the resource and scope, with the default ordering appended as the only qualifier. Nothing is redundant and nothing essential is buried.

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 simple read-only list tool with fully documented parameters and strong annotations, this is nearly complete. The only gap is that with no output schema the description could hint at what a returned book record contains (e.g. title, author, price), leaving the agent to discover the payload shape by calling.

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%, so publisher id sourcing, page size, sort enum values and the term filter are already documented in the schema. The description only echoes the default sort ('best sellers first') and adds no new meaning, which is the baseline for full schema coverage.

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 gives a specific verb and resource ("List the books of one publisher") plus the platform scope (Iranketab), so an agent knows exactly what is returned. It stops short of naming a sibling such as ik_search or ik_browse to contrast against, so differentiation is left to the tool name.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: the agent infers it should call this when it has a publisher and wants that publisher's catalogue. There is no explicit when-not guidance or pointer to alternatives like ik_search for cross-publisher queries or ik_editions for a single book's editions.

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