Skip to main content
Glama
sepehr071

masterkala-mcp

by sepehr071
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Blog posts and buying guides

mk_blog_posts
Read-only

List MasterKala blog posts—buying guides, comparisons, and how-tos—newest first with links so users can pick product types or learn how to use gadgets.

Instructions

List MasterKala blog posts (buying guides, comparisons, how-tos), newest first, with links.

Use when the user asks which product type to choose or how to use a gadget: point them to the matching guide. Readers' questions answered by the store: mk_blog_comments.

Input Schema

NameRequiredDescriptionDefault
pageNoPage number, from 0, newest first.
limitNoPosts per page.
categoryNoBlog section, e.g. 'buying_guide' (راهنمای خرید) or 'comparison_review' (مقایسه و بررسی).buying_guide

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.3.0
    • removedInput schema / properties / category / title
      Removed value: -"Category"
    • removedInput schema / properties / limit / title
      Removed value: -"Limit"
    • removedInput schema / properties / page / title
      Removed value: -"Page"
    • removedInput schema / title
      Removed value: -"mk_blog_postsArguments"
    • changedOutput schema / (root)
      Previous value: -{
-  "additionalProperties": true,
-  "title": "mk_blog_postsDictOutput",
-  "type": "object"
-}New value: +null
  2. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds useful behavior the annotations do not: newest-first ordering and that results carry links, which matters because there is no output schema. It does not disclose the notable default (category defaults to 'buying_guide', so results are filtered unless overridden) or any pagination/rate-limit 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?

Two tight sentences: the core listing behavior and ordering are front-loaded, followed by the usage/routing sentence. No filler or repetition of the name.

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, three-parameter list tool with no output schema, the description covers purpose, ordering and result shape ('with links') adequately. The only meaningful omission is the default category filter, which changes what an agent actually receives when it omits that parameter.

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 page, limit and category are already documented in the schema, establishing the baseline of 3. The description's parenthetical content types loosely mirror several enum values but adds no syntax or defaulting detail, and it omits the consequential default of category='buying_guide'.

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 ('List MasterKala blog posts'), the content types covered (buying guides, comparisons, how-tos), the ordering ('newest first') and the return shape ('with links'). It also distinguishes itself from the sibling mk_blog_comments, which handles a different content type.

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 an explicit trigger ('Use when the user asks which product type to choose or how to use a gadget') and routes reader questions to the sibling mk_blog_comments. It stops short of excluding other plausibly competing siblings such as mk_reviews or mk_search for the same intent, so the routing is clear but not exhaustive.

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