Skip to main content
Glama
sepehr071

masterkala-mcp

by sepehr071
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Search products

mk_search
Read-only

Search MasterKala products by keyword to compare price, discount, and stock for each match, with in-stock items first and matching categories, brands, and tags.

Instructions

Search MasterKala products by keyword: price, discount and stock of each match.

Use first for "price of X" / "do you have X". In-stock items come first. Also returns matching categories (ids for mk_browse) and brand/tag pages. Cheapest: mk_find_cheapest. One product: mk_product.

Input Schema

NameRequiredDescriptionDefault
pageNoPage number, from 0.
limitNoProducts per page.
queryYesProduct name or keyword, Persian or English, e.g. 'هندزفری بلوتوث' or 'xiaomi'.
in_stock_onlyNoDrop items that cannot be bought online now. In-stock items come first, so an empty page means no more in-stock matches (total still counts all matches).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv0.3.0
    • removedInput schema / properties / in_stock_only / title
      Removed value: -"In Stock Only"
    • removedInput schema / properties / limit / title
      Removed value: -"Limit"
    • removedInput schema / properties / page / title
      Removed value: -"Page"
    • removedInput schema / properties / query / title
      Removed value: -"Query"
    • removedInput schema / title
      Removed value: -"mk_searchArguments"
    • changedOutput schema / (root)
      Previous value: -{
-  "additionalProperties": true,
-  "title": "mk_searchDictOutput",
-  "type": "object"
-}New value: +null
  2. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

With readOnlyHint=true already covering the safety profile, the description adds genuine behavioral context beyond annotations: in-stock results are ordered first, and the response also contains matching categories (with ids for mk_browse) and brand/tag pages. It does not mention pagination limits or result-size constraints, so it stops short of full disclosure.

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 purpose then routing, with zero filler. Every clause carries information an agent needs for selection.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, yet the description enumerates the return payload (price, discount, stock, categories, brand/tag pages) and the ordering rule, while parameters are fully covered by the schema. An agent has everything needed to call and interpret this tool.

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 query, page, limit and in_stock_only are all documented in the schema itself, including the empty-page semantics. The description only gestures at keyword search and stock ordering, adding no syntax or format detail beyond the structured fields; baseline 3 applies.

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 ('Search MasterKala products by keyword') plus the payload returned (price, discount, stock per match), which is exactly what an agent needs to distinguish this from siblings like mk_browse or mk_product.

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?

Gives an explicit trigger ('Use first for "price of X" / "do you have X"') and names both routing alternatives with their conditions: mk_find_cheapest for cheapest and mk_product for a single product. Nothing is left to inference.

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