Skip to main content
Glama
Sign In
iranketab-mcp

iranketab-mcp

by sepehr071
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Search Iranketab

ik_search
Read-onlyIdempotent

Find books, authors, translators, publishers, or categories on Iranketab by name and return matching IDs for follow-up lookups.

Instructions

Search Iranketab by name and return matching books, authors/translators, publishers or categories with their ids.

Use first to turn a title or name into an id. Books are listed once per work (it groups all editions); at most 100 hits, site relevance order.

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": {
      "query": "<query>"
    },
    "name": "ik_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNoprofile = author or translator; category = tag/series.book
limitNoMost results to return.
queryYesName or topic, Persian (Latin for foreign names).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, open-world, non-destructive behavior, so the bar is lower. The description adds real context beyond them: results are ordered by site relevance, books are deduplicated per work across editions, and hits cap at 100 — the last point mildly conflicts with the schema's limit maximum of 50 and could have been reconciled.

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?

Three short sentences, front-loaded with what the tool does, then the sequencing hint, then the two behavioral caveats (dedupe, 100-hit cap). No filler or repeated schema content.

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 necessary work of telling the agent that results carry ids and span four entity types, which is what makes the tool usable as an id resolver. It could note pagination or what to do when a name is ambiguous, but for a 3-parameter search tool it is largely sufficient.

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 query, kind, and limit are already documented including the enum meanings and the Persian/Latin naming convention. The description only reinforces that search is by name and that result volume is capped, which is a baseline-level contribution rather than added semantic depth.

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?

States a specific verb and resource ('Search Iranketab by name') and enumerates what the results can be (books, authors/translators, publishers, categories) with ids. It does not name a sibling explicitly, but 'Use first to turn a title or name into an id' implicitly separates it from id-based fetchers like ik_book and ik_profile.

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 line 'Use first to turn a title or name into an id' gives clear ordering guidance that routes the agent to this tool before id-based siblings. It stops short of stating when not to use it (e.g. browsing without a query term, which ik_browse presumably covers).

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