Skip to main content
Glama

Shipping, returns and store rules

kh_store_info
Read-onlyIdempotent

Retrieve Khanoumi store policies from its official FAQ—packaging costs, shipping fees and times, returns, payments, refunds, authenticity, and pink-box rules—by topic or query.

Instructions

Get Khanoumi's order rules from the official FAQ: packaging cost, shipping fees and times, returns, payment and refunds, authenticity guarantee, pink-box rules.

Fees for the true order cost are in the delivery answers. With topic=all and no query, answers are cut to 300 characters; pick a topic or query, or set full_text=true.

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": "kh_store_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNoOnly Q&A containing this, e.g. 'هزینه ارسال'.
topicNoFAQ section; all = about 80 answers, clipped.delivery
full_textNoDo not clip answers when topic is all.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv0.4.0
    • removedInput schema / properties / query / anyOf
      Removed value: -[
      -  {
      -    "maxLength": 60,
      -    "minLength": 2,
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • changedInput schema / properties / query / description
      Previous value: -"Only questions or answers containing this, e.g. 'هزینه ارسال'."New value: +"Only Q&A containing this, e.g. 'هزینه ارسال'."
    • addedInput schema / properties / query / maxLength
      Added value: +60
    • addedInput schema / properties / query / minLength
      Added value: +2
    • addedInput schema / properties / query / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • changedInput schema / properties / topic / description
      Previous value: -"FAQ section: delivery (fees, times), returns, payment, guarantee (authenticity, expiry), ...; all = about 80 answers, clipped."New value: +"FAQ section; all = about 80 answers, clipped."
  2. Changed6 schema fields changedv0.2.0
    • addedInput schema / properties / full_text
      Added value: +{
      +  "default": false,
      +  "description": "Do not clip answers when topic is all.",
      +  "type": "boolean"
      +}
    • removedInput schema / properties / query / title
      Removed value: -"Query"
    • changedInput schema / properties / topic / description
      Previous value: -"FAQ section: delivery (fees, times), returns, payment, guarantee (authenticity, expiry), order, pink_box, tracking, order_edit, comments, gold, or all (about 80 answers, long: prefer a topic or a query)."New value: +"FAQ section: delivery (fees, times), returns, payment, guarantee (authenticity, expiry), ...; all = about 80 answers, clipped."
    • removedInput schema / properties / topic / title
      Removed value: -"Topic"
    • removedInput schema / title
      Removed value: -"kh_store_infoArguments"
    • changedOutput schema / (root)
      Previous value: -{
      -  "additionalProperties": true,
      -  "title": "kh_store_infoDictOutput",
      -  "type": "object"
      -}New value: +null
  3. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld), so the description adds genuine behavioral value beyond them: answers are silently truncated to 300 characters when topic=all with no query, and full_text=true removes the clipping. It doesn't state approximate result volume or how answers are structured, but the truncation caveat is the key non-obvious trait.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short paragraphs, front-loaded with what is retrievable and followed by the operational caveat. The topic enumeration is long but earns its place as a coverage statement; no filler sentences.

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?

With no output schema, the description does the work of implying the return shape (Q&A entries, clipped answers) and warns about the default truncation. For a three-optional-parameter read-only lookup, this is close to complete; only result volume and exact answer structure are left implicit.

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 coverage is 100%, so all three parameters are already documented, including the topic enum and the 60-character query cap. The description does add cross-parameter meaning — the topic/query/full_text interaction that governs clipping — but this largely restates the full_text schema text ('Do not clip answers when topic is all').

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?

The description opens with a specific verb+resource ('Get Khanoumi's order rules from the official FAQ') and then enumerates the covered topics — packaging cost, shipping, returns, payment/refunds, authenticity guarantee, pink-box. That topic list makes it obviously distinct from the product-oriented siblings (kh_search, kh_product, kh_brands), though no sibling is named explicitly.

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?

It gives concrete operating guidance: 'pick a topic or query, or set full_text=true' to avoid clipped answers, and it directs the agent to the delivery topic when the real order cost is the question. It stops short of saying when to use this versus kh_search or kh_blog_search for overlapping informational needs.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.