Skip to main content
Glama
Sign In
iranketab-mcp

iranketab-mcp

by sepehr071
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Articles

ik_articles
Read-onlyIdempotent

Search Iranketab's blog by title or browse newest articles to find book reviews, author profiles, and reading lists.

Instructions

Find articles on Iranketab's blog (book reviews, author profiles, reading lists), by search or newest first.

query searches titles (max 100 hits, no paging); without it, newest first. Read one with ik_article.

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

Input Schema

NameRequiredDescriptionDefault
pageNoNewest-list page (18 per page).
limitNoMost search hits.
queryNoSearch words; omit for newest articles.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, open-world, and non-destructive behavior. The description adds valuable operational details—query searches titles only, caps at 100 hits with no paging, and newest list paginates at 18 per page—beyond what annotations provide.

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 sentences plus a short pointer sentence, front-loaded with purpose and mode selection; every phrase carries information with no filler.

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 list/search tool with three parameters and rich annotations, the description covers purpose, modes, limits, and the handoff to ik_article. It does not describe the fields returned in the article list, but the pointer to ik_article implies the list is sufficient for selection.

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. The description adds that query searches titles (not full content) and is limited to 100 hits without paging, which clarifies the search behavior beyond the schema's 'Search words' description.

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?

States a specific verb and resource ('Find articles on Iranketab's blog') and enumerates content types (book reviews, author profiles, reading lists), then names the sibling ik_article for reading one, so it cannot be mistaken for the single-article tool.

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?

Explains the two retrieval modes (query search vs newest first) and points to ik_article for reading a single article, but does not explicitly compare against ik_search or state when not to use this tool.

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