kalicart-global
Server Details
Federated commerce search across independent WooCommerce merchants. Keyless, read-only MCP server.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Average 4.5/5 across 5 of 5 tools scored.
Each tool has a clearly distinct purpose: get_product for detailed product info, global_search for searching products, list_categories for browsing categories, list_merchants for listing merchants, and lookup_merchant for checking individual merchant compatibility. No overlap.
All tool names follow a consistent verb_noun pattern in lowercase with underscores (get_product, global_search, list_categories, list_merchants, lookup_merchant). The pattern is uniform across the set.
With 5 tools, the server is well-scoped for a federated catalog indexing products across merchants. It covers searching, retrieving details, browsing categories and merchants, and verifying individual merchant support—each tool earns its place.
The tool surface covers all essential operations for the domain: search products, get product details, list categories, list merchants, and check merchant ARC compliance. No obvious gaps exist for a read-only federated index.
Available Tools
5 toolsget_productARead-onlyIdempotentInspect
Retrieve full product detail from the KaliCart Global federated index by p2209_id. Returns price, availability, attributes, variants, and a direct storefront URL for checkout handoff. Obtain p2209_id from global_search results.
| Name | Required | Description | Default |
|---|---|---|---|
| p2209_id | Yes | KaliCart product ID (e.g. prod_duinshop-it_432395) |
Tool Definition Quality
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, openWorldHint, and idempotentHint. The description adds value by listing returned fields (price, availability, attributes, variants, storefront URL) without contradicting annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences with no redundancy. First sentence covers purpose and returns; second sentence gives source for the ID. Every word earns its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a single-parameter tool with no output schema and rich annotations, the description fully covers purpose, parameter source, and return content. No gaps identified.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% with a description for p2209_id. The description provides an example format (prod_duinshop-it_432395) and clarifies it is a KaliCart product ID, adding meaning beyond the schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Clearly specifies verb (Retrieve), resource (full product detail from KaliCart Global federated index), and required parameter (p2209_id). Distinguishes from sibling global_search by describing returned data including price, availability, attributes, variants, and storefront URL.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicitly directs to obtain p2209_id from global_search results, providing clear context for when to use this tool (after search). No explicit when-not, but the flow is implied.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
global_searchARead-onlyIdempotentInspect
Search the KaliCart Global federated index: real product offers across independent WooCommerce merchants that opted in via the ARC (Agent-Readable Catalog) protocol. Returns merchant-authoritative prices, UCP availability_status, storefront URLs and canonical category leaves. Provide q (free text) and/or leaf (canonical category). Spec: https://bridge.kalicart.com/spec/
| Name | Required | Description | Default |
|---|---|---|---|
| q | No | Free-text product query matched against native merchant catalog text; no server-side translation. Translate when needed, or use leaf and canonical filters for language-neutral retrieval. | |
| leaf | No | Canonical category leaf (e.g. beverages.alcohol.sparkling_prosecco) | |
| brand | No | Brand facet filter (normalized, e.g. "nike") | |
| color | No | Color family (e.g. "blue") | |
| limit | No | Max offers to return (1-25, default 10). No pagination; raise to get more in one call | |
| gender | No | Gender facet (normalized): male, female, unisex, kids | |
| in_stock | No | Only offers with availability_status=in_stock | |
| max_price | No | Maximum price filter (numeric; per-offer merchant currency, no FX conversion) | |
| min_price | No | Minimum price filter (numeric; per-offer merchant currency, no FX conversion) |
Tool Definition Quality
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnly, openWorld, and idempotent hints. The description adds value by specifying that results are 'merchant-authoritative', the nature of availability status, and the lack of translation for free text. No contradictions.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Three concise sentences: what it does, what it returns, and usage advice. No unnecessary words. The spec link is a plus. Efficiently front-loaded.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Covers main purpose, returns, and key parameter guidance. However, it doesn't explicitly state behavior with no parameters (since none are required) or detail the output format beyond listed fields. With 9 parameters and no output schema, slightly more completeness could help, but still adequate.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, but the description adds meaningful context: no server-side translation for 'q', canonical nature of 'leaf', limit bounds and no pagination, per-offer currency for price filters. This goes beyond the schema descriptions.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states it searches the KaliCart Global federated index for real product offers. The verb 'Search' and resource specification are explicit. It distinguishes from siblings like get_product, list_categories, etc., by describing the global cross-merchant scope.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description advises to provide 'q' and/or 'leaf', includes a note about no server-side translation for 'q', and links to a spec. While it doesn't explicitly enumerate when to use alternatives, the sibling names and context make the intended use clear.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
list_categoriesARead-onlyIdempotentInspect
List canonical product category leaves used by KaliCart Global with product counts. Use to discover available categories before filtering global_search with the leaf parameter.
| Name | Required | Description | Default |
|---|---|---|---|
| parent | No | Filter to children of this node (e.g. "apparel") |
Tool Definition Quality
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, openWorldHint, and idempotentHint. The description adds that the output includes product counts, which is useful behavioral context beyond annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two sentences, front-loading the purpose and then the usage, with no wasted words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple tool with one optional parameter and no output schema, the description provides enough information to invoke correctly, though it could explicitly mention default behavior when no parent is specified.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% with clear parameter description. The tool description does not add additional meaning to the parameter beyond what the schema provides, so baseline score applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool lists canonical product category leaves with product counts, distinguishing it from sibling tools like global_search and list_merchants.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicitly states to use this tool before global_search to discover available categories for the leaf parameter, providing clear context.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
list_merchantsARead-onlyIdempotentInspect
List WooCommerce merchants participating in the KaliCart Global federated catalog. Returns merchant domain, storefront URL, and product count. Use before global_search to understand catalog coverage.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Max merchants to return (default 20, max 50), ordered by product count desc. No pagination |
Tool Definition Quality
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Describes return fields (domain, storefront URL, product count) and ordering (by product count desc, no pagination). Annotations already indicate read-only, idempotent, open-world; description adds useful behavioral details.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences: one for purpose, one for usage. Efficient, front-loaded, no wasted words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Covers purpose, usage, and return fields. Lacks error conditions or empty result handling, but for a simple list tool with annotations this is sufficient.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema covers 100% of the single limit parameter with full description, default, max, min. Description adds context about ordering and lack of pagination, enhancing understanding.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Clearly states the tool lists WooCommerce merchants from the KaliCart Global federated catalog. Differentiates from siblings like lookup_merchant and global_search by specifying the resource and action.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicitly recommends using before global_search to understand catalog coverage. Could mention when not to use, but provides helpful context.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
lookup_merchantARead-onlyInspect
Check whether a merchant domain runs an ARC-compliant catalog (KaliCart Bridge). Returns bridge_version, merchant discovery URL and federated-indexing consent flags. A miss schedules a background probe. Use when you already know a merchant domain (verify ARC support, get its discovery URL); to discover products across merchants, use global_search.
| Name | Required | Description | Default |
|---|---|---|---|
| domain | Yes | Merchant domain, e.g. shop.example.com |
Tool Definition Quality
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already indicate readOnly and openWorld. Description adds the key behavioral detail that a miss schedules a background probe, and lists return fields, adding value beyond annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two concise sentences, front-loaded with purpose and returns, followed by usage guidance. No wasted words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the simple single-parameter tool with annotations, the description covers purpose, return fields, side effect, usage guidelines, and alternatives. No gaps.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema covers the parameter fully with description and example. Description reinforces but doesn't add new semantic depth, so baseline 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool checks for ARC-compliant catalogs and returns specific fields. It distinguishes from sibling global_search by noting when to use each.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicitly says when to use (known merchant domain) and when not to (for product discovery, use global_search), providing a clear alternative.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!