kalicart-global

List participating merchants

list_merchants

Read-onlyIdempotent

Use this to inspect which WooCommerce merchants currently participate in the searchable KaliCart Global catalog and how much catalog coverage each contributes. It returns stable merchant identifiers, domains, storefront URLs, product counts, and sync time. Do not use it to find products; use global_search instead.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No	Max merchants to return (default 20, max 50), ordered by product count descending. No pagination

Output Schema

TableJSON Schema

Name	Required	Description	Default
`total`	Yes
`merchants`	Yes
`truncated`	Yes
`returned_count`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 20, 2026

changedOutput schema / properties / merchants / items / required

Previous value: -[
-  "merchant_id",
-  "merchant_domain",
-  "storefront_url",
-  "platform",
-  "product_count",
-  "last_sync"
-]New value: +[
+  "merchant_id",
+  "merchant_domain",
+  "platform",
+  "product_count",
+  "last_sync"
+]

Changed2 schema fields changedSep 13, 2026

changedInput schema / properties / limit / description

Previous value: -"Max merchants to return (default 20, max 50), ordered by product count desc. No pagination"New value: +"Max merchants to return (default 20, max 50), ordered by product count descending. No pagination"

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "merchants": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "last_sync": {
+            "anyOf": [
+              {
+                "anyOf": [
+                  {
+                    "type": "string"
+                  },
+                  {
+                    "format": "date-time",
+                    "type": "string"
+                  }
+                ]
+              },
+              {
+                "type": "null"
+              }
+            ]
+          },
+          "merchant_domain": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "merchant_id": {
+            "type": "string"
+          },
+          "platform": {
+            "type": "string"
+          },
+          "product_count": {
+            "minimum": 0,
+            "type": "integer"
+          },
+          "storefront_url": {
+            "format": "uri",
+            "type": "string"
+          }
+        },
+        "required": [
+          "merchant_id",
+          "merchant_domain",
+          "storefront_url",
+          "platform",
+          "product_count",
+          "last_sync"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "returned_count": {
+      "minimum": 0,
+      "type": "integer"
+    },
+    "total": {
+      "minimum": 0,
+      "type": "integer"
+    },
+    "truncated": {
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "merchants",
+    "total",
+    "returned_count",
+    "truncated"
+  ],
+  "type": "object"
+}

Changed1 schema field changedJun 25, 2026

addedInput schema / properties / limit / description

Added value: +"Max merchants to return (default 20, max 50), ordered by product count desc. No pagination"

AddedJun 24, 2026

TDQS

A4.5/5.0

Behavior4/5

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

The annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds useful context beyond the annotations: the returned data highlights 'stable merchant identifiers, domains, storefront URLs, product counts, and sync time,' and characterizes the data as 'currently participate' to indicate current-scope semantics.

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 sentences with no filler; the main usage and scope are front-loaded, the return contents are listed compactly, and the redirect to global_search is placed at the end. Every sentence earns its place.

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?

For a one-optional-parameter read-only list with a full output schema available, the description is complete: it states the collection being listed, the per-item information returned, and the alternative for product search. Nothing needed to call it correctly is missing.

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?

The single parameter, limit, is fully described in the schema (default, max, ordering, no pagination), so schema coverage is 100%. The description does not add parameter-level detail, but it doesn't need to because the schema already carries that burden.

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?

The description names a concrete action ('inspect'), a specific resource (participating WooCommerce merchants in the KaliCart Global catalog), and the key outcome (catalog coverage contributed). It also distinguishes itself from global_search by saying it should not be used to find products.

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?

It opens with 'Use this to inspect...' and explicitly says 'Do not use it to find products; use global_search instead.' This gives an explicit when-to-use, when-not-to-use, and a named alternative, which is exactly the routing guidance an agent needs.

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

All kalicart-global tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.