Skip to main content
Glama
Sign In
iranketab-mcp

iranketab-mcp

by sepehr071
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Categories and filters

ik_categories
Read-onlyIdempotent

Lists Iranketab menu categories or a category's filter groups, and shows all options in a chosen filter group for browsing book editions.

Instructions

List Iranketab's menu categories, or the sub-category filter groups of one category.

No arguments: the main menu (id, name). With a category: its filter groups for ik_browse filters (a few options each); group lists one group fully.

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

Input Schema

NameRequiredDescriptionDefault
groupNoList all options of this filter group.
categoryNoShow its filter groups; omit for the main menu.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.9/5.0
Behavior3/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 safety profile is covered. The description adds useful return-shape context ('id, name' for the main menu, 'a few options each' for filter groups) which is meaningful given there is no output schema, but it does not explain whether category identifiers are names or slugs, or what happens with an invalid category.

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, front-loaded statements organized by argument case; every sentence carries distinct information and nothing is redundant with the schema.

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 two-optional-parameter read tool with no output schema, the description covers both modes and their return shape adequately. The only gap is identifier format and error behavior for unknown categories/groups.

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%, so the baseline is 3, but the description genuinely adds semantics: it clarifies the interplay of the two optional parameters and discloses that group listings are abbreviated ('a few options each') unless you pass `group` to list one fully. That truncation behavior is not evident from the schema alone.

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 ('List Iranketab's menu categories') and names the two modes it supports, including the tie-in to ik_browse filters. An agent can tell this is a taxonomy/navigation tool rather than a search tool, though the distinction from ik_browse itself is only implied.

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?

Gives clear conditional usage for each argument combination: no args for the main menu, a category for its filter groups, and `group` to expand one group. It lacks an explicit 'when not to use' or a direct routing statement versus ik_browse, which keeps it below 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