Skip to main content
Glama

search_merchants

Search KlickyMart merchant records (same filters as GET /q)

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

Input Schema

NameRequiredDescriptionDefault
qNosubstring of domain or store name
btcNoexact BTC grade 0-4
catNoFine store-type codes
payNoany of these method codes; aliases (btc-onchain, lightning, shop-pay...) are accepted; a single group name (bitcoin, lightning, ecash) works too
subNoProduct family the store sells
tosNo
guestNo1 (or true) = drop stores known to REQUIRE an account; a store whose guest status is unknown is kept (guest: null) and ranked after confirmed-guest stores. confirmed = strict: only stores confirmed to allow guest checkout. 0 = only stores known to require an account. Items carry guest (true|false|null) and co
limitNo
scopeNo
ag_minNo
an_catNo
co_minNo
statusNo
btc_anyNo
btc_minNo
pay_allNo
categoryNoshopping (the vertical) or a coarse product category
ease_minNo
ship_preNo1 = shows shipping and tax before the payment step (observed by the probe)
ships_usNo
min_trustNoMinimum trust_tier; applied before paging so total is exact. Items carry trust_tier, trust_proofs, trust_label, trust_why, src
pay_groupNo
reachableNostatus crawled and agent access >= 1
rail_statusNo
agent_nativeNo1 = agent-native stores only
btc_indirectNo1 = stores where bitcoin works only indirectly (third-party processor such as BitPay/Confirmo/Coinbase Commerce/OpenNode, or a gift card bought with BTC); not native acceptance
free_ship_maxNofree-shipping threshold at or below this many USD (publicly stated)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / guest / description
      Added value: +"1 (or true) = drop stores known to REQUIRE an account; a store whose guest status is unknown is kept (guest: null) and ranked after confirmed-guest stores. confirmed = strict: only stores confirmed to allow guest checkout. 0 = only stores known to require an account. Items carry guest (true|false|null) and co"
    • changedInput schema / properties / guest / enum
      Previous value: -[
      -  0,
      -  1
      -]New value: +[
      +  0,
      +  1,
      +  "confirmed"
      +]
    • changedInput schema / properties / guest / type
      Previous value: -"integer"New value: +[
      +  "integer",
      +  "string"
      +]
  2. First observed

TDQS

C2/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It does not state that the operation is read-only, whether results are paginated, how ranking works, whether limit defaults or caps exist, or what the response shape looks like. For a 27-filter search endpoint, this leaves major behavioral questions unanswered.

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

Conciseness2/5

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

The description is only one sentence and contains no filler, but it is drastically under-specified for the complexity of the tool. The GET /q reference is obscure and not self-contained, so brevity here reflects omission rather than efficient communication.

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

Completeness1/5

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

Given 27 optional parameters, 48% schema coverage, no annotations, and no output schema, the description is nowhere near complete enough to guide correct invocation. It does not explain paging, defaults, result ordering, trust filtering, or the meaning of the many enum-constrained filters.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 48%, and the description adds no parameter meaning beyond an opaque reference to GET /q. Many parameters such as limit, scope, ag_min, an_cat, btc_any, pay_all, ease_min, and rail_status are undocumented or only sparsely described in the schema, so the description fails to compensate for the coverage gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a clear verb and resource: searching KlickyMart merchant records. However, it does not distinguish this tool from siblings such as find_agent_native, find_offers, or get_record, and the reference to GET /q assumes external API knowledge the agent may not have.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use guidance, no exclusions, and no naming of alternative tools for narrower merchant queries. The agent is left to infer that this is the broad search endpoint, without being told when a sibling like get_record or find_agent_native would be more appropriate.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.