Wagner Data: supplier catalogs to Shopify

Order a supplier price list to Shopify CSV conversion

request_catalog_conversion

Read-only

Prepares an order to convert a supplier price list or catalog into a Shopify import CSV. Nothing is sent or stored: it returns an order code and the email (address, subject, body) the merchant sends with the file attached; the converted files come back to the sending address within 24 hours. Use when the merchant asks for the conversion.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "email": "<email>"
    },
    "name": "request_catalog_conversion"
  }
}

Input Schema

Name	Required	Description
`email`	Yes	Merchant's email address; the files are delivered here.
`notes`	No	Anything to know: which price column to use (MSRP/MAP), markup, pages to skip (optional)
`file_name`	No	Name of the price list file (optional)
`vendor_name`	No	Supplier/brand name to put in Shopify's Vendor field (optional)

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 10, 2026

TDQS

A4.1/5.0

Behavior5/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description goes well beyond them: 'Nothing is sent or stored', the return is an order code plus an email (address, subject, body), and the converted files arrive at the sending address within 24 hours. That discloses the asynchronous handoff model and turnaround time, which an agent cannot infer from annotations.

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 tightly packed sentences: what it does, what it returns and the delivery SLA, then the usage trigger. Nothing is redundant and the core action is front-loaded.

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?

No output schema exists, and the description compensates by explaining exactly what the caller receives (order code plus email content) and how the result is delivered. For a four-parameter preparation tool, nothing an agent needs to invoke 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?

Schema description coverage is 100%, so all four parameters are already documented, and the description adds only the delivery semantics for the email address. It does not elaborate on how notes fields (markup, MSRP/MAP, skipped pages) are interpreted, so it stays at the schema-determined baseline.

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?

States a specific verb and resource: 'Prepares an order to convert a supplier price list or catalog into a Shopify import CSV.' An agent can tell it produces an order plus an email template rather than the converted file itself. It does not name the sibling quote or validation tools, so sibling differentiation is only partial.

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

Usage Guidelines3/5

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

'Use when the merchant asks for the conversion' gives a basic trigger but no exclusions or routing to alternatives. With get_catalog_conversion_quote and check_shopify_csv as siblings, the definition never says when to prefer those (e.g. pricing first, or validating an existing CSV) instead of ordering a conversion.

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

All Wagner Data: supplier catalogs to Shopify 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.

Resources

Need Help?