Skip to main content
Glama
sepehr071

khanoumi-mcp

by sepehr071
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Search the beauty blog

kh_blog_search
Read-onlyIdempotent

Search the Khanoumi magazine for buying guides, care routines, and ingredient explainers. Use when users ask what suits them or how to use a product.

Instructions

Search the Khanoumi magazine (مجله خانومی): buying guides, care routines, ingredient explainers, with links.

Use when the user asks what suits them or how to use something; then find products with kh_search.

Input Schema

NameRequiredDescriptionDefault
pageNoPage number, from 1 (20 posts per page).
queryYesTopic, Persian works best, e.g. 'شامپو ریزش مو' or 'روتین پوست چرب'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.2.0
    • removedInput schema / properties / page / title
      Removed value: -"Page"
    • removedInput schema / properties / query / title
      Removed value: -"Query"
    • removedInput schema / title
      Removed value: -"kh_blog_searchArguments"
    • changedOutput schema / (root)
      Previous value: -{
-  "additionalProperties": true,
-  "title": "kh_blog_searchDictOutput",
-  "type": "object"
-}New value: +null
  2. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds one useful behavioral detail — results include links — but says nothing about pagination limits (the 20-per-page, 50-page cap), ranking, or result volume, so it adds only modest value beyond the structured fields.

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 compact sentences, zero filler: the first defines scope and content, the second gives the usage trigger and the hand-off tool. The most decision-relevant information (what it searches) is front-loaded.

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-parameter read-only search with no output schema, the description covers scope, trigger, and follow-up routing, and the 'with links' hint partially compensates for the missing return-value documentation. Pagination behavior is left to the schema, which is acceptable but leaves a small gap.

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%: the query parameter already documents the Persian-input preference with examples, and page documents the 20-posts-per-page sizing. The description adds no parameter-level guidance beyond that, so the baseline 3 is correct.

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 (search) and resource (the Khanoumi magazine / مجله خانومی), and enumerates the content types returned (buying guides, care routines, ingredient explainers). This clearly separates it from the product-oriented siblings like kh_search and kh_product, though the differentiation is only fully spelled out in the second sentence.

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 ('when the user asks what suits them or how to use something') and names the follow-up tool ('then find products with kh_search'), which routes the agent well. It stops short of stating when not to use this tool, so it falls just short of 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