list_merchantsList public AirShelf merchants that have an assigned slug and at least one active product. Internal/demo and empty catalogs are excluded. Returns each merchant's name, slug, and product count; the slug is the merchant argument for request_quote.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
| Name | Required | Description | Default |
|---|---|---|---|
| total | No | ||
| merchants | Yes |
Changes observed during successful MCP inspections.
Output schema / properties / merchants / items / properties / checkout_capabilityAdded value: +{
+ "description": "shopify indicates a connected Shopify store; redirect sends the buyer to the product page.",
+ "enum": [
+ "shopify",
+ "redirect"
+ ],
+ "type": "string"
+}Output schema / properties / merchants / items / properties / manifest_urlAdded value: +{
+ "description": "Merchant agent manifest URL with supported endpoints and capabilities.",
+ "type": "string"
+}Output schema / properties / merchants / items / properties / products_urlAdded value: +{
+ "description": "Merchant product-listing endpoint URL.",
+ "type": "string"
+}Output schema / properties / merchants / items / properties / search_urlAdded value: +{
+ "description": "Merchant-scoped product-search endpoint URL.",
+ "type": "string"
+}Output schema / properties / merchants / items / properties / product_count / exclusiveMinimumAdded value: +0Output schema / properties / merchants / items / properties / slug / anyOfRemoved value: -[
- {
- "type": "string"
- },
- {
- "type": "null"
- }
-]Output schema / properties / merchants / items / properties / slug / typeAdded value: +"string"Output schema / properties / merchants / items / requiredPrevious value: -[
- "name"
-]New value: +[
+ "name",
+ "slug",
+ "product_count"
+]Output schema / (root)Previous value: -nullNew value: +{
+ "$schema": "http://json-schema.org/draft-07/schema#",
+ "additionalProperties": false,
+ "properties": {
+ "merchants": {
+ "items": {
+ "additionalProperties": {},
+ "properties": {
+ "domain": {
+ "type": "string"
+ },
+ "name": {
+ "type": "string"
+ },
+ "product_count": {
+ "type": "number"
+ },
+ "slug": {
+ "anyOf": [
+ {
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+ ]
+ }
+ },
+ "required": [
+ "name"
+ ],
+ "type": "object"
+ },
+ "type": "array"
+ },
+ "total": {
+ "type": "number"
+ }
+ },
+ "required": [
+ "merchants"
+ ],
+ "type": "object"
+}Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already provide readOnlyHint=true and destructiveHint=false, so the read-only nature is known. The description adds meaningful behavioral detail: filtering rules (internal/demo/empty catalogs excluded), the exact returned fields (name, slug, product count), and the cross-tool relationship of the slug. This goes beyond the annotations without contradicting them.
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 tightly written sentences. The first states what is listed and the filters; the second states the return fields and connects the output to a sibling tool. Every sentence carries information, and the core purpose is 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?
For a zero-parameter list tool with annotations covering safety and an output schema available, the description is complete. It specifies the exact population, the expected fields, and the practical use of the output. No additional context is needed to call it correctly.
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?
The tool has zero parameters)Skip, and schema coverage is 100% vacuously; the baseline for 0 params is 4. The description adds no parameter-specific detail because none exists, but it does mention the relevance of the returned slug to request_quote, which is a useful adjacent semantic hint.
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 starts with a specific verb-resource pair ('List public AirShelf merchants') and further narrows the scope with precise inclusion criteria (assigned slug, at least one active product). It distinguishes the tool by explicitly excluding internal/demo and empty catalogs, and clarifies the output's role (slug as merchant argument for request_quote), making it easy to differentiate from sibling tools.
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 gives clear context: this is the tool to use when you need publicly available merchants with active products)Skip, and it even ties the output to request_quote. However, it does not explicitly compare to alternatives like search_catalog or find_products, nor state when not to use it, leaving a small gap in routing.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.