Skip to main content
Glama
Sign In
iranketab-mcp

iranketab-mcp

by sepehr071
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Curated lists and awards

ik_lists
Read-onlyIdempotent

Lists literary prizes, best-of lists, book series, countries, genres and movements with their IDs so you can browse winners and volumes by category.

Instructions

List Iranketab's literary prizes, best-of lists, book series, countries, genres or literary movements with ids.

Every id is a category for ik_browse (winners, volumes). Single novel series (Harry Potter) are not listed: use ik_search(kind='category'). Discounted winners: ik_browse(325, filters=['15=']).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "ik_lists"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNoawards = literary prizes; best_lists; series = collections; countries = literature by country; genres; movements = literary schools.awards

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world behavior, so the bar is lower. The description still adds value by disclosing that the output is id-bearing and that those ids are category keys consumed by ik_browse, and by flagging the coverage gap for single-novel series. It omits any note on result size, ordering, or pagination.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, front-loaded with what is listed and immediately followed by the sibling routing. The trailing "ik_browse(325, filters=['15=<award id>'])" is compressed to the point of being cryptic, since the magic category 325 and filter id 15 are never explained, which slightly undercuts readability.

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 one-parameter lookup tool with no output schema, the description covers what is returned (ids), what those ids are for (ik_browse), and the main exclusion case. The only shortfall is the unexplained hard-coded 325/filter 15 example, which an agent cannot generalize from without extra knowledge.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with a documented enum, so a 3 would be the baseline. The description earns above baseline by mirroring the enum values in its opening sentence and by clarifying the "series" value in a way the schema does not: anthologies and collections are listed, single-novel series are excluded.

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?

It states a specific verb ("List") and enumerates the six concrete resource types (prizes, best-of lists, series, countries, genres, movements) plus what each entry yields (ids). It also distinguishes itself from ik_search and ik_browse by naming those siblings and the conditions that select them.

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

Usage Guidelines5/5

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

Explicit routing: "Single novel series (Harry Potter) are not listed: use ik_search(kind='category')" tells the agent when not to use this tool, while "Every id is a category for ik_browse" tells it the follow-up step. The discounted-winners example adds a concrete call pattern, even if the literal 325 is opaque.

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